StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19376023
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-10-15T08:00:12.473
FavoriteCount
0
LastActivityDate
2013-10-15T08:00:12.473
LastEditDate
LastEditorUserId
0
OwnerUserId
1315875
ParentId
1761421
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
You can indeed check the installed version, if you register your database as a data-tier application during deployment. You can do this by including the following in your publish profile: <pre><code> <RegisterDataTierApplication>True</RegisterDataTierApplication> </code></pre> This option will register the schema and it's version number in the msdb database during deployment. Be sure to change the dacpac version number between releases! We use msbuild to create dacpacs, example code for setting the dacpac version: <pre><code>DacVersion=$(ProjectReleaseNumber).$(ProjectBuildNumber).$(ProjectRevisionNumber) </code></pre> Having done this, you can build version-aware predeployment scripts. <pre><code>-- Get installed version, e.g. 2.3.12309.0 DECLARE @InstalledVersion NVARCHAR(64) = ( SELECT type_version FROM msdb.dbo.sysdac_instances WHERE instance_name = DB_NAME() ); -- Get the major part of the version number, e.g. 2 DECLARE @InstalledVersionMajor TINYINT = CONVERT(TINYINT, SUBSTRING(@InstalledVersion, 0, PATINDEX('%.%', @InstalledVersion))); IF (@InstalledVersionMajor < 5) BEGIN; PRINT 'Do some nontrivial incremental change that only needs to be applied on version before 5'; END; </code></pre> Checking for the version number that you are currently deploying is a little more cumbersome but can also be done. Check out Jamie Thomson's excellent blog for this technique:<a href="http://sqlblog.com/blogs/jamie_thomson/archive/2012/12/10/editing-sqlcmdvariable-nodes-in-ssdt-publish-profile-files-using-msbuild.aspx" rel="nofollow">Editing sqlcmdvariable nodes in SSDT Publish Profile files using msbuild</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PONontrivial incremental change deployment with Visual Studio database projects
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USS Koppenol
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.