We have a SQL Server 2000 database in production running on SQL Server 2000 instance. But in our staging environment, we have this same database on a SQL Server 2008 instance but running under compatibility level 80 (SQL Server 2000).
We need to upgrade the production database to SQL Server 2008, so I'm trying to run the SQL Server Upgrade Advisor 2008 on my staging copy. But I'm getting this error:
SQL Server version: 10.00.2531 is not supported by this release of Upgrade Advisor, only SQL Server 2000 or SQL Server 2005 are supported.
My goal is to know what might happen if I change the compatibility level to 100 (SQL Server 2008). How can I get Upgrade Advisor to tell me under my circumstances?
As you've discovered, Upgrade Advisor doesn't work for that; I don't know of a tool that automatically compares compatibility modes. The best reference I know of is this:
https://msdn.microsoft.com/en-us/library/bb510680(v=sql.100).aspx
Which will show you breaking changes between level 80=>90 and level 90=>100.
I should also state that upgrading to SQL 2008 should NOT be your final stop; with SQL 2016 looming on the horizon, you should investigate moving up to at least SQL 2014.
When upgrading we normally create a new install and migrate databases over, but we are going to test out in-place upgrade from sql server 2008 to sql server 2008 r2 (standard) in our development environment. Question is can the upgrade steps for in-place be run without downtime or restricting access to the server? Users must be able to continue to work without issues. Thanks ahead of time.
Hey friends I have one problem related to SQL Server 2008 R2.
I set up Visual Studio 2010 on my system and then SQL Server 2008 R2. And now I am trying to restore the database in my system but it generates the Return Error 3241 error. And I could not restore the database.
One of my friend told me that since you have install the VS 2010 first you are running the SQL Server 2005 Express although SQL Server 2008 R2 has been installed, this is the problem you could not restore the database.
But now How can I solve my problem? I will be very thankful for the solution...
Since you have both SQL Server Express and SQL Server 2008 R2 installed, at least one of them is a named instance; most likely this will be SQL Server 2005 Express, installed as (local)\SQLEXPRESS.
The error indicates you're trying to restore a newer version backup to an older database (a 2008 R2 backup to a 2005 or 2008 server) - so are you trying to restore your 2008 R2 database onto the (local)\SQLExpress instance??
That will never work! SQL Server doesn't support restoring a backup from a newer version on an older server.
You need to restore it to your real 2008 R2 server instance! Possibly this is called your (local) server - possibly it has an instance name - not sure, you need to check this for yourself.
try this first :
Restore verifyonly from disk='Path\backupfile.bak'
I have a database working on SQL Server 2000. We are now migrating to a new server with SQL Server 2008 r2. Can anyone please point me to some resource or howto?
I'm not really finding my way around SQL 2000.
Thank you!
Basically, what you need to do is:
backup your database in SQL Server 2000 to a .bak file
move that *.bak file to your new server
restore that database onto your new server
You're done! There's really nothing more to it..... just backup (on your old system) and restore (on your new system).
So where exactly is your problem ??
Update: as #Péter correctly mentions: this leaves your database in the SQL Server 2000 compatibility mode. This means: even though you've "migrated" to SQL Server 2008 R2, you can still only use the 2000 features.
In order to see what compatibility mode your database is in, check the sys.databases catalog view:
SELECT * FROM sys.databases WHERE name = 'YourDatabaseName'
One column is called compatibility_level and contains an INT; 80 = SQL Server 2000, 90 = SQL Server 2005, 100 = SQL Server 2008 / 2008 R2 and 110 = SQL Server 2012
In order to change your database to a different compatibility level, use this command:
ALTER DATABASE YourDatabaseNameHere
SET COMPATIBILITY_LEVEL = 100;
This will put your database into the "native" SQL Server 2008 (and 2008 R2) mode and now your migration is complete, you can use all the new SQL Server 2008 R2 features.
I would start by running the Upgrade Advisor against the 2000 server (during low utilization or off hours) to see what recommendations it makes and fully address each: http://msdn.microsoft.com/en-us/library/ms144256.aspx
Here too is a white paper from MS on the topic: http://download.microsoft.com/download/2/0/B/20B90384-F3FE-4331-AA12-FD58E6AB66C2/SQL%20Server%202000%20to%202008%20Upgrade%20White%20Paper.docx
A lot could go wrong...too much to cover in a forum setting. But then again nothing could go wrong...the best plan, test, and then test some more.
The others answers are correct from a technical perspective but not from a support point of view.
I don't think Microsoft support a direct upgrade from SQL Server 2000 to SQL Server 2008 R2. That doesn't mean it is hard, just that it is not supported. (Which may or may not be significant for your scenario)
You can upgrade your SQL Server 2000 instance to SQL Server 2008 R1 and then perform a subsequent upgrade to SQL Server 2008 R2. (Or even SQL Server 2012 if you are so inclined)
I am currently doing the same thing.
Creating your SQL 2008 database from a 2000 restore bak is a good first step. Most of the work for me was dealing with the user permissions, and making sure that the users were in sync with the database login, and that we didn't have a database schema generated by the backup tied to that user that would cause problems if we tried to recreate that database user.
What we ended up doing was:
1) Create a script. We had a script that would dynamically write a script to do the following: drop login, drop db user, drop schema, recreate login, recreate user, grant user permissions.
2) Restore database.
4) Run the generated script
Edited Apr 2012 because original link changed to latest version, SQL Server 2012
For an "in-situ" upgrade (MSDN links):
... to SQL Server 2008 R2
You can upgrade instances of SQL Server 2000, SQL Server 2005 or SQL Server 2008 to SQL Server 2008 R2.
... to SQL Server 1012
You can upgrade from SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2 to SQL Server 2012.
yet another option is to try to connect database (files) of sql2k to sql2k8 directly.
The simpliest way is to back up your database in SQL 2000 to a .bak file and move it. Do a restore and everything should be fine. Run a sp_Users_Loging to identify the users in the orphan server.
I have Mysql dump file of around 200 GB, now I need to migrate into Sql server 2008. So What approach I should follow, should I go ahead with the line by line sql statement or is there any GUI tool available which suits to my requirement ?
Microsoft SQL Server Migration Assistant for MySQL v1.0
Microsoft SQL Server Migration
Assistant (SSMA) is a toolkit that
dramatically cuts the effort, cost,
and risk of migrating from MySQL to
SQL Server 2005, SQL Server 2008, SQL
Server 2008 R2 and SQL Azure.