|
|
|
SSC Veteran
 
Group: General Forum Members
Last Login: Yesterday @ 6:37 AM
Points: 228,
Visits: 501
|
|
|
|
|
|
Grasshopper
Group: General Forum Members
Last Login: Yesterday @ 12:30 AM
Points: 13,
Visits: 47
|
|
Great series. Replicated all the steps and have it working except for one thing: When I drop the WeatherData db and run the MasterDeploy script, I get the following:
------------------------------------------------
[V1] Deploying WeatherData v1
[V1] Calling CreateWeatherData.test.sql...
Failure: WeatherData does not exist.
[V1] CreateWeatherData.test.sql called.
Msg 911, Level 16, State 1, Line 3
Database 'WeatherData' does not exist. Make sure that the name is entered correctly.
> DBVersion table exists.
> Dropping AddNewVersion stored procedure
...however if I highlight just the CreateWeatherData lines and run those first on their own, the database gets created and then I can run the MasterDeploy in its entirety. Any idea why it's getting stuck?
|
|
|
|
|
SSC Journeyman
Group: General Forum Members
Last Login: Tuesday, January 26, 2010 10:56 AM
Points: 82,
Visits: 187
|
|
What is the point of storing this kind of information in the Database itself, but not using some kind of trigger?
People should be able to find out what they are looking at BEFORE they dive into the internals of the database, so the only point that I can see for storing version info in a table is if you can set things up to automatically record what changes are made.
Throw away your pocket calculators; visit www.calcResult.com
|
|
|
|
|
SSC Rookie
Group: General Forum Members
Last Login: 2 days ago @ 7:02 AM
Points: 40,
Visits: 162
|
|
Great series Andy - Thank you.
I do have a question. All of the work you did here is something that has to be done manually and maintained manually. Now I understand in situations where you can’t buy a development too this is the way to go. I am a big fan of automation and using tools that help reduce errors and maintain efficiency. With that said is it me or are others seeing a big drop off in the number of posts for tools like Visual Studio Team Edition For Database Professionals even though 2008 was recently introduced? Reason why I ask is because I am pushing to use this tool as a standard yet I don’t want to go down this path only to have to go back to the manual way in the near future or worse yet back myself into a corner. Do you have any feedback on this? Again thank you for taking the time to put together a great series.
|
|
|
|
