THE SQL Server Blog Spot on the Web

Welcome to SQLblog.com - The SQL Server blog spot on the web Sign in | |
in Search

Jamie Thomson

This is the blog of Jamie Thomson, a freelance data mangler in London

SSDT database projects were not always going to output T-SQL…

Interesting the stuff you pick up from reading forums…

“The BATCH seperators [in SSDT deployment scripts] are used to provide scoping when resolving object shapes. SSDT or VSDB scripts for that matter serve a different purpose, they provide the blueprint of the model you want, and do not represent how it will be used to construct the target site. We choose TSQL as our DSL, at first we wanted to use a different representation, but user research in 2005 told us loud and clear users wanted to use TSQL as their DSL. In order to make the compiler work, we had to impose some simplifications, one is a more frequent use of BATCH seperators to indentify object scopes.”

by Gert Drapers (former lead of the SSDT product team) at http://social.msdn.microsoft.com/Forums/en-US/ssdt/thread/47d4124b-82cd-48f9-8ba7-c2ae4c73cbcf/

Personally I’m glad that they chose to use T-SQL as it makes debugging easier but I’d be interested to know what else was on the table!

@Jamiet

Published Wednesday, February 13, 2013 10:15 AM by jamiet
Filed under: ,

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

 

Kent Chenery said:

Well a .dacpac is a zip file (rename it to crack it open) and you'll find some XML in there.  Maybe that's what they were thinking of using.

February 13, 2013 4:35 AM
 

jamiet said:

Well the XML is just the definition of the model - they take that model, compare it to the target, and build a script that makes the target schema look like that which is defined in the model. In other words, there is a lot of work goes on *after* the dacpac is produced to determine what actions are to be taken.

There still needs to be some sort of API for applying that to the DB - the post above states that that API is T-SQL.

February 13, 2013 4:44 AM
 

piers7 said:

M, presumably (defunct Oslo project)?

February 21, 2013 8:06 PM
 

jamiet said:

Hi Piers,

Yeah, someone else contacted me offline and made the same suggestion. Think you could be right.

JT

P.S. M might be rising from the grave. Watch this space.

February 22, 2013 3:54 AM
 

asava samuel said:

Here is a database compatible with Windows Runtime:

https://www.kellermansoftware.com/p-49-ninja-winrt-database.aspx

March 14, 2013 5:52 AM

Leave a Comment

(required) 
(required) 
Submit

This Blog

Syndication

Powered by Community Server (Commercial Edition), by Telligent Systems
  Privacy Statement