StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6930270
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-08-03T17:02:28.817
FavoriteCount
0
LastActivityDate
2011-08-03T17:02:28.817
LastEditDate
LastEditorUserId
0
OwnerUserId
877097
ParentId
6929018
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Although making each DDL script 'rerunnable' with IF NOT EXISTS etc is good practice, I can see how that approach will eventually get messy and cumbersome. It can also get especially thorny when you are running data conversion scripts. The approach I have always taken is to number each script sequentially and store them somewhere and keep track of the ID of last run script; that ID is your DBVersion. The DBVersion number is stored in a settings or version table in the DB. All that's left is to have some process for comparing the DBVersion value with the MAX(id) of your scripts table (or file, or dictionary or whatever) <pre><code>CREATE TABLE DBVer ( DBVer INT PRIMARY KEY CLUSTERED ) INSERT INTO DBVer(DBVer) SELECT 1 CREATE TABLE DBScripts ( ID INT IDENTITY(1,1) PRIMARY KEY CLUSTERED, Script NVARCHAR(MAX) ) CREATE PROC UpdateDB AS DECLARE @i INT, @max INT, @SQL NVARCHAR(MAX) SELECT @max = MAX(ID), @i = MAX(DBVER) FROM DBScripts CROSS JOIN DBVer --only ever one row in here but make sure! if @i>@max RETURN --no updates, let exit early WHILE @i <= @max --loop through and apply new scripts BEGIN SELECT @SQL = Script FROM DBScripts WHERE ID = @i EXEC sp_executesql @statement = @SQL SET @i = @i + 1 END UPDATE DBVer SET DBVer = @i --this can also be in the loop GO </code></pre> This is not a total solution but you get the general idea. Things to think about include where the update is getting called from if each of 100 clients call updateDB on startup it may be worth putting in some locking or some other means to manage a potential race condition. It may also be worth wrapping everything in a transaction. DDL can be rolled back but you can also fill up the log very quickly with big changes. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWrite an SQL update script so it always updates the db correctly, regardless of the db version our client has
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USCode Magician
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. This table or related slice is empty.
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.