Comments
Sort by recent activity
Hi
Essentially I am trying to create an upgrade script for my database which I can then reuse on multiple servers. So I have one database which is the old version and one which is the new version. I can compare these databases with SQL Compare and SQL Data Compare to generate scripts that will transform any database that is the old version into the new version.
However if one of the differences between the old and new database versions is a new lookup or definition table, both the table schema and the table data needed to be scripted out as part of the upgrade. I can't figure out how to do this. Can I use SQL Packager for this?
Hope that's clearer
Julia. / comments
Hi
Essentially I am trying to create an upgrade script for my database which I can then reuse on multiple servers. So I have one database which is the old version and one which is the new version. ...
Hi David
Yes, all the databases which I will be using my upgrade script on are exactly identical. Sorry I should've been more specific.
I can script the schema of the new definition table using SQL compare, but I can't work out how to script the data. SQL data compare doesn't seem to be happy to script the data for a table that only exists in the source database.
Can you give me more info on how I can do this using SQL Compare, SQL Data Compare or SQL Packager?
Julia. / comments
Hi David
Yes, all the databases which I will be using my upgrade script on are exactly identical. Sorry I should've been more specific.
I can script the schema of the new definition table using SQL...
Hi jheidt
Thanks for the reply. I could do that, but I was looking for a solution that was more automated. The more manual steps there are, the more chance there is of introducing an error into the process. / comments
Hi jheidt
Thanks for the reply. I could do that, but I was looking for a solution that was more automated. The more manual steps there are, the more chance there is of introducing an error into the...
For me, just an option to specify a single value when the column is being created would be sufficient. There are scheduled routines in the database that manage the value of the column I am adding, so the value of the column at creation doesn't really matter. It just needs to have a value so I can define the column as NOT NULL.
Julia. / comments
For me, just an option to specify a single value when the column is being created would be sufficient. There are scheduled routines in the database that manage the value of the column I am adding, ...