backgroundwe know that Azure Sql Database can reduce operation cost, is a pass mode, has the resource elasticity setting, can freely adjust the resources automatically corresponding to the different business peaks (also can reduce the cost cost), but also facilitates the late project resource expansion, and some other advantages or features, This is not listed. The database development engineer, then, is the difference between operating Azure SQL database and how we use the SSMs (Microsoft Sql Server Management Studio) to operate on the local library. we'll simply compare them from the following sections1. Create object comparisons; (Simple list Create database operation on Azure, SSMS CREATE database default omitted)2. Connection library comparison;3. Operation comparison; 1. Creating Object Comparisons 2. Comparison of link libraries
As you can see from the diagram above, there are no objects at the instance level that are involved in Azure SQL database. in Azure SQL database The approximate summary is as follows:1. No AlwaysON, no database mirroring, no log shipping, no replication. There are geo-replication can directly add the database auxiliary copy (the library size refers to the data file size);2. There is no agent, if you need to perform scheduled scheduling can refer to the " through the local agent monitoring and control azure_sql_database" 3. No SSIS;4. Objects at the instance level are not supported (such as not supporting global temporary tables, no profiler, etc.); for monitoring You can refer to how to monitor running scripts or whether a stored procedure is running under Azure SQL database 3. Comparison of specific operations can I use objects such as temporary tables by discovering that there is no tempdb in the Azure SQL database system databases? first look at the current Azure SQL database version numberTest temporary table (not SQL Server temporal table) temporary tables can be used, and global temporary tables are not supported. Some commands are not supported in pass mode. Note that the default getdate () is UTC time, which differs from Beijing time by 8 hours. Other libraries cannot be explicitly called in this library, such as the use master by default, Azure SQL database does not support cross-Library operations, you need to create an extension table, build a table with the same name, and be read-only and schema-unique. If you want to store procedures for cross-library operations, you need to use Sp_execute_remote calls. the stored procedure point in the SSMs 2012 interface is right -click:the stored procedure point in the SSMS 2016 interface is right -click:UI interface operation, it is recommended to install the latest version of SSMs. or exec sp_helptext add the specific stored procedure name, execute, copy the execution result is the script of the stored procedure; ReferencesHow to create an extension tableSp_execute_remoteSummaryAzure SQL database compared to SSMS:1. No AlwaysON, no database mirroring, no log shipping, no replication. There are geo-replication can directly add the database auxiliary copy (the library size refers to the data file size);2. No agent; If you need to perform a scheduled schedule, you can refer to " monitoring Azure SQL database via local agent " 3. No SSIS;4. Object-level objects are not supported (such as not supporting global variables, no profiler, etc.); for monitoring, you can refer to how to monitor running scripts or whether a stored procedure is running under Azure SQL database5. Some commands are not supported, because Azure SQL database is pass mode;6. Note that the default getdate () is a UTC time difference of 8 hours from Beijing time;7. You cannot explicitly invoke other libraries in this library;8. By default, Azure SQL database does not support cross-Library operations, you need to create an extension table, build a table with the same name, only read-only and schema-unique;9.azure SQL database is a V12-based engine, and it is recommended to install SSMS version 2016 operation on the UI interface. 10. User name restrictions, cannot use Admin\administrator\sa\guest\root
How to connect Azure SQL database with SSMs the difference between connecting to a local library
