Comments
Sort by recent activity
Thanks for the responses....so can you tell me how you would propose to get these changes out to my production database(s) and include the migration scripts with them?
Start me with the trunk, and I have a developer who needs to branch the code. What steps should we take, from development, to merging back to the trunk, to deploying to production, to get this to perform correctly and include the migration scripts?
Thanks,
Joe / comments
Thanks for the responses....so can you tell me how you would propose to get these changes out to my production database(s) and include the migration scripts with them?
Start me with the trunk, and ...
thanks for the reply, Brian. Unfortunately, I can't link my production DB to source control, because that would be bad. So doing "get latest" there would not be possible. I have to use SQLCompare.
I tagged 2 releases, release 1 and release 2, in SVN (which is essentially just making a copy of both the Schema folder and the Migration Scripts folder).
I then did a compare of these two, but because the migration script was added somewhere in the intermediate steps between the final releases, SQL Compare doesn't seem to be picking it up. / comments
thanks for the reply, Brian. Unfortunately, I can't link my production DB to source control, because that would be bad. So doing "get latest" there would not be possible. I have to use SQLCompar...
Hi chris,
This was a brand new repository, created by first committing the changes from the existing database...
The discrepancy is a single row that exists both in the DB as well as in the repository. Here is the full statement:
INSERT INTO [dbo].[FILE_TYPE] ([FILE_TYPEID], [FILETYPE], [DESCRIPTION], [ICONIMAGE], [VIEWABLE], [EXTENSION]) VALUES (N'x-zip-compressed', 'ZIP Document', NULL, 'Zip.gif', NULL, N'.zip')
This is repeated on both sides of the comparison, but one one side it says "Only in Database" and the other side it says "Only in Source Control" / comments
Hi chris,
This was a brand new repository, created by first committing the changes from the existing database...
The discrepancy is a single row that exists both in the DB as well as in the reposit...
Sorry it's taken so long to get back on this one....a slew of other projects considerations are splitting my time way too much [image]
The advanced scenarios weren't terribly advanced, things like changing the size of a column referenced by a foreign key, or adding a "not null" property to a column, both things that would normally cause SQLCompare to drop the column (and/or FKs) and recreate them, which could result in a loss of data. / comments
Sorry it's taken so long to get back on this one....a slew of other projects considerations are splitting my time way too much
The advanced scenarios weren't terribly advanced, things like changin...
I am using SQL Source Control 3.
My config file looks just like the one below, thanks. / comments
I am using SQL Source Control 3.
My config file looks just like the one below, thanks.
Thanks, forcing binary collation did the trick. / comments
Thanks, forcing binary collation did the trick.