![]() ![]() This is because we are querying against the local database instead of the connected database that actually contains real data. The Message pane shows (0 row(s) affected), and the Results pane returns no row. ![]() In the script pane, paste this code and click the Execute Query button to run the query. Right-click the TradeDev node and select New Query. This time, notice that the tables, views and functions have been deployed to the local database server. If you debug the same project later, SSDT will detect any changes since your last debugging session, and deploy only those to the local database.Įxpand the nodes under TradeDev in the Local database server again. In this case, SSDT will first attempt to build the project, and if there is no error, the project (and its entities) will be deployed to the local database. ![]() Press F5 to debug the TradeDev database project.īy default, SSDT will use the local database server instance for debugging database projects. Notice that they do not contain any of the tables and entities we created in earlier procedures. The Data Tools Operations window shows the status of expansion/import operations in progress on any database in the Local node. Notice the appearance of a database with the same name as the TradeDev project. This is the local database instance.Įxpand the Local and Databases nodes. Notice that in SQL Server Object Explorer, under the SQL Server node, a new node named Local appears. The following procedures utilize entities created in previous procedures in the Connected Database Development and Project-Oriented Offline Database Development sections. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |