[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 279
  • Last Modified:

Consideration in consolidating 2x old SQL Server 2000 into 1x new powerful SQL Server 2008 ?

Hi All,

I'm in the process of consolidating the old Database server into SQL Server 2008 VM, what could be the things that I need to consider before I go ahead and attach detaching the DB instances into the new 2008 server ?

cmiiw:
After I've done the restore for each instances, I'll set the compatibility level to SQL 2000, and run DBCC UPDATEUSAGE (0);
0
jjoz
Asked:
jjoz
  • 3
  • 2
  • 2
  • +2
4 Solutions
 
p_nutsCommented:
Io as it will be running virtually. And I've had applications that wouldn't connect. So I'm always testing this and moving db by db.
0
 
Aaron ShiloCommented:
hi

i agree with p_nuts ive had problems to connecting with apps after moving to sql 2008 from 2000
you should do a POC first and see that you have no problem using your apps before migrating complitly
0
 
Alpesh PatelAssistant ConsultantCommented:
If you set the compatibility level to SQL 2000 then you have no advantage of SQL Server 2008. Please avoid this if possible.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
Kobe_LenjouCommented:
PatelAlpesh, this is not true. You do benefit from all the features and performance of SQL2008. Setting the compatibility level ONLY changes the way the engine handles certain situations that have drastically changed (for example default order: http://insqlserver.com/content/effect-database-compatibility-level-order-clause-scenario-1) and a lot of other stuff.
Your database WILL be upgraded to the SQL2008 format internally, no matter what compat level you have.

The penalty of this low compat level is very small.
0
 
jjozAuthor Commented:
oh, so if I have a very old legacy application that can only uses the old SQL Server 2000 T-SQL, then I won't be able to use it eventhough I set the compatibility level to 80 --> SQL Server 2000 compat level ?
0
 
Kobe_LenjouCommented:
On the contrary. The compat level 80 will make it work.

The compat level setting only changes the 'exterior behaviour' of the database.

You should however test this. If this app was written in a 'funky' way, it might just stop working.
0
 
Kobe_LenjouCommented:
By the way, if your app is playing by the rules it will just work, no matter what compat level you assign.
0
 
p_nutsCommented:
Exactly.. But how many apps play by the rules.

The only way of knowing is to test. Start with the defaults in 2008 and change the level after testing if needed .

Also talk to the vendor. What do they support ..
0
 
jjozAuthor Commented:
thanks !
0

Featured Post

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

  • 3
  • 2
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now