SQL azure vs SQL Server

 

SQL azure should be easy for developers and administrators to use, because SQL azure uses a similar relational data model, where data is stored on SQL azure and stored on SQL Server. Similar to a local SQL server instance, an SQL azure Server is a logical group of databases and an independent authorization unit.

On each SQL azure server, you can create multiple databases. Each database can have multiple tables, views, stored procedures, indexes, and other familiar database objects. This data model can reuse your existing relational database design and transact-SQL programming skills and experience, simplifying the migration of existing local database applications.ProgramTo SQL azure. For more information about Transact-SQL and Its Relationship with SQL Azure, visit
Transact-SQL support (SQL azure database ).

The SQL azure server and database are both virtual objects and do not correspond to physical servers and databases. By isolating you from the physical system, SQL azure enables you to devote time to database design and value-added services.

 

 

Features	SQL Server (local)	SQL azure	Work und
Data Storage	No size limit	· Web version · Bussiness version For details about the size and pricing, see pricing overview. Note: When you use the allocated size (1 GB or 10 Gb), only the select and delete statements are executed. The update and insert statements throw an error.	· An archive process can be created when the old data can be transplanted to another SQL azure or local database. · Because of the preceding size constraints, we recommend that you split the data across databases. Creating multiple databases makes full use of the computing power of multiple nodes. The biggest value of the azure model is its flexibility. You can create any number of databases as needed when your needs are at the highest point and delete the database when your needs are reduced. The biggest challenge is the ability to develop applications across databases. Once this function is implemented, it can be extended to any database.
Version Edition	· Express · Workgroup · Standard · Enterprise · Enterprise version
Connectivity	· SQL Server Management Studio · Sqlcmd · SQL Server 2008 R2 management Studio provides complete connectivity to SQL azure. Earlier versions have limited support. · Sqlcmd
Data Migration		· SQL server integration services, BCP, and sqlbulkcopyapi
Authentication Verification	· SQL Verification · Windows Verification · SQL Server Verification		Use SQL Server for verification
Schema	No restrictions	SQL azure does not support heap tables. All tables must have a clustered index to insert data.	Check all scripts to ensure that all tables have a clustered index.
Tsql supports tsql supportability		Some tsql commands are fully supported. Some are supported, while others are not. Supported tsql: http://msdn.microsoft.com/en-us/library/ee336270.aspx · Some supported tsql: Http://msdn.microsoft.com/en-us/library/ee336267.aspx · Unsupported tsql: Http://msdn.microsoft.com/en-us/library/ee336253.aspx
"Use" command "use" command	Supported	Not Supported	The use command is not supported. Because the databases created by each user may not be on the same physical server. Therefore, applications must retrieve data from multiple databases and combine the data at the application layer.
Transaction replication transactional Replication	Supported	Not Supported	You can use BCP or SSIS to obtain data flowing into the local SQL Server as needed. You can also use SQL data sync tool to synchronize local SQL Server with SQL azure.
Log Transmission Log Shipping	Supported	Not Supported
Database mirroring ing	Supported	Not Supported
SQL Agent	Supported	Unable to run SQL Agent/jobs on SQL azure	You can run SQL Agent on the local SQL Server and connect to SQL azure
Server Selection items server options	Supported	· Support some system views (http://msdn.microsoft.com/en-us/library/ee336238.aspx)	Most system-level metadata is disabled because the information on the server layer provided on the cloud is meaningless.
Connection restrictions connection limitations	None	To provide a fair user experience for all tenants on the node, the connection may be closed in the following situations: · Excessive resource usage · Long run query (more than 5 mi minutes) · A single transaction that runs for a long time in TRAN and end tran-(more than 5 minutes) · Idle connection-(over 30 minutes)
SSIS	You can run SSIS locally.	Unable to run SSIs in SQL azure	Run SSIS locally and connect to SQL azure using ADO. net provider.

 

References: http://blogs.msdn.com/ B /azchina/archive/2010/05/25/sql-azure-vs-sql-server.aspx