Back to Basics — What is DDL, DML, DCL & TCL?


I was talking with a database administrator about different categories that SQL Commands fall into — and I thought it would be great to document here. So here you go:

DML Data Manipulation Language: SQL Statements that affect records in a table. SELECT, INSERT, UPDATE, DELETE
DDL Data Definition Language: SQL Statements that create/alter a table structure CREATE, ALTER, DROP
DCL Data Control Language: SQL Statements that control the level of access that users have on database objects GRANT, REVOKE
TCL Transaction Control Language: SQL Statements that help you maintain the integrity of data by allowing control over transactions COMMIT, ROLLBACK


Is Truncate SQL command a DDL or DML? Please use comment section!

Author: Paras Doshi

How to fix the Non-unicode to unicode data type conversion problems in SQL Server Integration Services?



Are you trying to import an Excel file into SQL Server using SQL Server Integration services…And ran into error that has words like “Non unicode” and “unicode”? Then this blog is for you.

Why does this error occur?

Well it turns out that things like SQL Server and Excel have encoding standards that they follow which provides them a way to process, exchange & store data. BUT turns out that SQL Server and Excel use different standards.


So, the solution is simple right? Import the data from Excel into non-Unicode format because that’s what you need for SQL Server.

So how do you that? Between your Source and Destination tasks, include a task called “Data conversion” and do the following for all columns that have text:

Excel SQL Server Unicode Nonunicode

And in the destination task, you’ll have to make sure that the mapping section using the new output aliases that you defined in the “data conversion” step.


In this post, we learned about how to solve a common error that pops up when you try to import excel file to sql server using SSIS. Hope that helps.

Author: Paras Doshi

Summary – SQL server to SQL Azure migration << Paras Doshi

In this blog post, I aim to summarize database migration options that I have been blogging about for past few weeks. Choosing right tool is a key decision when you decide to migrate SQL server to SQL Azure – And I hope this blog post can help you decide which is the best tool to be picked for your scenario:
Here is the summary:
Scenario/Tool Generate script wizard SSIS BCP DAC v2.0
Migrate SQL schema YES YES   YES
Migrate Data YES YES YES YES
Migrate large Data   YES YES YES


Blog Posts featuring tools that help migrate SQL server database to SQL Azure:


Migrating SQL server Data to SQL Azure using BCP << Paras Doshi


How to use SQL server Integration services (SSIS) to migrate data from SQL server to SQL Azure << Paras Doshi

Generate script wizard:

How to use Generate script wizard to migrate SQL server Database to SQL Azure << Paras Doshi

Dac’s v2.0 (SQL Azure Import Export CTP):

[ SQL Azure Labs ] Exploring SQL Azure Import/Export Feature (CTP)


Related posts:

Migrating TSQL file and SQL server 2005 / 2008 Database to SQL Azure using SQL Azure Migration wizard << Paras Doshi

“Migrating Data into Microsoft’s Data Platform – SQL Azure” << SolidQ Journal Article


CrossPosted From: Summary – SQL server to SQL Azure migration << Paras Doshi


Can you please consider posting your valuable feedback/comments/suggestion in comments section? Thanks!

Extending SQL Azure with Azure worker roles << Guest Post on Pinal sir’s blog


My guest post on “Extending SQL Azure with Azure worker role” got published on Pinal sir’s blog. In the article, I discuss three lightweight solutions that augment the contemporary capability of SQL Azure. They are:

1. Automating SQL Azure database backup process

2. Lightweight SQL server agent for SQL Azure

3. Synchronization of databases using SYNC Framework.

To read the article, please visit:

Thank you Pinal sir for this wonderful opportunity.

sys.dm_db_partition_stats : A SQL Azure Dynamic management view (DMV) to calculate database size


I have written a blog post on beyondrelational site about a SQL Azure DMV – sys.dm_db_partition_stats that can be used to extract information about database size and size of each individual database object. To read the article please go to:

TSQL code to know SQL Azure DB size

A step by step guide to Install Adventure works LT ( sample database ) on SQL Azure


I have written a step by step guide on how to install Adventure works LT DB, a sample database available on codeplex, at my beyondrelational site. here is the link to the article: