April 19, 2011 at 9:11 pm
Hi,
we are trying upgrade our db application to newer version.
right now we have 1.1 version (sql server 2005) and new version is 1.2 (sql 2008)
there are few new tables and columns in new version.
So when we migrate new data model chages to existing version database, just wondering what needs to be take care and how to start , who will do this task a dba or developer?
Kind of new to this task, any ideas would be appreciated. thank you.
April 20, 2011 at 4:51 am
There isn't one single way of doing this, but in general, it would be the DBA responsible for the rollout. To really get into deployments in detail, I'd suggest getting a copy of the Red Gate Guide to SQL Server Team-Based Development[/url] (it's a free e-book). I wrote the chapters on deploying databases.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 21, 2011 at 9:43 am
Been doing something similar to this for the last Six Months. I have found that the Database Edition of Visual Studio (2005, 2008, or 2010) has been invaluable in helping create the Schema and Data update scripts to keep everything Synchronized on both version of SQL server.
Do you have access to any of these tools?
If not, get them, or get the similar Red Gate products for comparing DB objects and creating update scripts.
The biggest issue I have experianced is the Developers forget that the new SQL Data Types like DATE, TIME, or DATETIME2 are only good for 2008 databases. When we find these in the Stored Procedure calls we change them back to SMALLDATETIME or DATETIME (depending on percision) and all is good. I recomend using the code analysis tools to check your data layer often for the used of only SQL 2005 data-types.
Also when you synch the 2008 DB schema to the 2005 server DB you will need to manually check and edit any automated update script for code, functions, and settings not supported by SQL 2005.
These are the things I know you will run into. You may find more. The bigest things to be aware of is the SQLDataType setting in the applicaiton code (use SQL 2005 data types only) and All client systems that will connect to the SQL 2008 db will need to install the SQL 2008 client drivers. The 2008 SQL client can connect to 2005 and do everything, but there are weird times when the 2005 SQL client can not connect to 2008 and do everything.
:smooooth:
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply