September 8, 2009 at 12:47 pm
We are looking into transferring over from SQL Server 2000 to SQL Server 2005 and are curious of some features available on SQL Server 2005.
Are there any known issues with converting a SQL 2000 database to SQL 2005 and using the Row Versioning-Based Transaction Isolation feature?
Does anyone have any recommendations on how to test this?
September 8, 2009 at 1:24 pm
in sql 2005 (and specially when during using snapshot isolation level) very important is tempdb performance (separe disks, raid 1/0/10 and so on...)
September 9, 2009 at 2:46 pm
J, we upgraded a few databases from SQL 2K to 2K5 about two years ago, and now again to 2K8. The second migration was absolutely painless, but the first one was a real pain in the a**e. We had lots of old-style outer joins (databases started off as 4.2 in 1994 or so) embedded in a few million lines of C++ code and a bunch of stored procedures (the latter were easy to find). Finding those and fixing them took us almost six months. You may not have that legacy hanging around, but keep it in mind if you want to set the compatibility level to 9 or 10 after the migration.
Marcin, can one actually set the isolation level to snapshot if database compatibility is retained at 8.0? Apart from the fact of course that it has to be appropriate for the kind of issue one wants to solve?
September 9, 2009 at 4:25 pm
Thanks for the responses so far guys!
Marcin,
The server we'll be using is already setup with RAID 1/0. Do you suggest moving temdb over to a separate SCSI drive? or do you think the performace on the disk setup is good enough?
September 15, 2009 at 3:44 am
about the tempdb ... that's a "it depends". it mostly depends on how much your tempdb is used.
if your upgrading your sql box and the behaviour stays the same i would say dont change the (hardware)setup assuming people are satisfied the way it works ... unless you have a reason (issues) to change the hardware while your upgrading anyway.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply