I have a fairly large web application that was built with SQL Server 2000 and .NET 1.1. We're planning on moving to .NET 2.0 eventually, but there's a lot of work to be done before that happens. In the short term, we're looking to purchase a new database server and would like to upgrade to SQL Server 2005 at the same time. Is it as simple as recreating our databases on this new system and changing the connection string, or are there other gotchas? As far as what we're doing with SQL Server 2000, it's really nothing more than tables, views, and stored procedures. Thanks in advance for any advice.
OK so I'm just the Network Admin here, but our DBA's are off doing other stuff. So I thought I may inquire here about how the easiest way to migrate from SQL Server 2000 to 2005? The first server I'd like to migrate is just databases with a few users, no DTS packages or anything like that... The only problem is that there are several hundred db's, so moving them one at a time is not an option. Has anyone here had successful experience with doing this? Thanks in advance for your help! -Andrew
I am in a process of migration our current SQL Server 2000 (Standard Edition with SP3 running on 32 bit windows 2000 server) to SQL Server 2005 (Standard with SP1 running on X64 windows 2003 server)?
For migration does current SQL Server 2000 requires Service Pack 4 Installed?
The Environment: I have an old Windows 2000 BackOffice server (Retail but with no media) that hosts a small database (<50mb) that is hosted on the local SQL Server 2000 installation. The network has 8 PCs that connect to the database via ODBC connections. I just purchased a new server running Windows Server 2003 Standard Edition (OEM).
What I€™m Trying to Accomplish: I want to decommission the old 2000 BackOffice server and move the database to the new 2003 Standard server. I€™m trying to do this on the cheap, so I really want to avoid spending thousands on a new SQL server license.
Things I€™m Considering: 1) Migrating the database from SQL 2000 Standard to SQL 2005 Express 2) Moving the database from SQL 2000 Standard to MS Access 3) Purchasing SQL Server 2005 licenses and upgrading 4) Purchasing SQL 2000 Server licenses
The options are pretty much listed in my order of preference. I€™d like to move from SQL 2000 Server to SQL 2005 Express, but I haven€™t really found a lot of material on the subject since people customarily go the other way.
Any advice or alternative recommendations would be much appreciated!
Scenario Recently moved a SQL2000 database to SQL2005. Collation on SQL 2000 database server was SQL_Latin1_General_CP1_CI_AS Colaltion on SQL 2005 database server is Latin1_General_CI_AS
After restoring the SQL 2000 database on SQL 2005 we observed that the database collation was SQL_Latin1_General_CP1_CI_AS. We have altered the database collation to Latin1_General_CI_AS. We understand this will work for all new objects created on the database but existing objects (prior to the collation change) will continue to have the 'SQL_Latin1_General_CP1_CI_AS' collation.
What is the best method to change the collation of the older columns to 'Latin1_General_CI_AS' - 1) Run ALTER TABLE ALTER COLUMN <colname> <datatype> COLLATE Latin1_General_CI_AS <nullability> on each varchar/char column
or
2) For each table BCP out data DROP TABLE RECREATE TABLE (taking the new collation Latin1_General_CI_AS) BCP in data
hi, i need some help here,i made a simple data driven website in my development PC, at first, i used MS Access for my data base then i migrate it to sql server express 2005, and it works fine when i try to run it in my development PC with my IIS. but of course i will be deploying it to a real server, in our office were i will deploy my data driven site, we have a PC server Win Server 2003 with SQL Server 2000 Enterprise (im not pretty sure by the name but i know its not a free version, its something like a 2000 sql version with a word enterprise at the end).so my question is, i am developing an ASPdotNET site originally used SQL server 2005 express,how can i migrate my site to the Win Server 2003 and my database from SQL Server 2005 express to SQL server 2000 enterprisewill it work?? if not, what are the possible solution that i can do in cases like mine?i used Visual Web Developer 2008 Express Ed. in making my sites, and its DOES NOT allow databases in SQL Server 2000!!!!!it says "can't recognize the database"i hope you can help me with this.Thanks-SALAMAT PO....=)
We want to migrate our SQL Server 2000 Databases to SQL Server 2005 including all objects, sprocs, views, jobs, securty, DTS Packages, etc. Pretty much everything.. If anyone has done this in the past for enterprise level databases, I would greatly appreciate it if they could send me some documentation, references, pointers.
Our costumer is going to install new hardware. Actually he is using 2 servers which both have windows 2000 server (+ AD) and sql server 2000 installed. On the new servers he will use windows 2003 and sql server 2005 The hard part will be migrating sql server 2000 to sql server 2005. I have read (not 100%, though) the SQL2005UpgradeTechRef document and downloaded SQLUASetup.exe to be ready (microsoft sql server upgrade analyzer software)
But actually i want to know what is best upgrade path and what are your experience. Is there already a got (or better or perfect) document availabe for the sql server 2000 to sql server 2005 sql server side by side upgrade. Please help! thanks
My database is running right now at SQL Server 2000 Enterprise Edition. We would like to upgrade it to SQL server 2005 Standard Edition.
Since this database was upgraded from MS Access 2000 to SQL server 2000. This database is accessed by a proprietary application. I don't know some of the details about this application.
There is one more issue with this database, replication was implemented earlier and now it is disabled.
I am thinking that to take a full backup from SQL server 2000 and restore it in SQL server 2005. What do you think?
Please let me know if you have any other idea.
I have another question for you. Right now replication is disabled and I restore SQL server 2000 database to SQL server 2005. Would there be any problem when we try to implement replication again?
I have to transfer existing DTS packages from sqlserver 2000 to sqlserver 2005, Please let me know the steps by which i can migrate all the runing DTS into SSIS into sqlserver 2005
I have to migrate our existing SQL Server 2000 (standard edition) running on Windows 2000 server (32 bit) to a new windows 2003 server (64 bit) (SQL 2005 standard edition). I am thinking of doing this migratin after hours (or may be on weekend so a
I have planned the following steps (in order).
1. Install SQL Server 2005 on new server.(windows authenticatin and a SQL server will be running on a separate domain account)
2. Download SQL server upgrade advisor on current SQL Server 2000 (windows 2000) and run a report.
3. Back up (Full) SQL Server 2000
4. Script logins and schedule tasks on SQL 2000
5. Restore database on SQL 2005
6. Create jobs by runing Jobs scripit on SQL 2005
7. Create users and passwords by running the exported script file. Please refer to: How to transfer logins and passwords between instances of SQL Server http://support.microsoft.com/kb/246133/en-us
I am aware that I might face issues of db compatibility level, statistics out of date so I need to update statistics and may be redindex all my tables
PLEASE LET ME Know if I am missing something obvious? Not sure about our existing DTS packages? Any information. Right now I am just thiking of running all my existing 2000 DTS in 2005 as legacy
Note: Rob, Tara, Michael Valentine Jones, Mladen or Nigel , if you cam provide some input from your wealth of experience on this matter. I would sincerely appreciate it.
HiWe are going to upgrade from SQL 2002 to 2005. We have approx. 100mrows of data on the main table and hand of stored procs and views.What we had in mind was that we would dts the data out, script thestored procs and view out and import the it back into SQL 2005.Is there smarter way of doing this?The key thing is that the data must be cleanThanks
Looking a preparing a SQL 2000 to SQL 2005 Migration Plan to include the following points. It will be a side-by-side migration where the current environment will run in parallel with the new.
1. Assessment of current SQL 2000 environment. (Hardware, Databases, SQL components such as DTS) 2. Seqence for Steps to perform duing the migration 3. Required resources 4. TimelinesAnyone have such as plan?
I am trying to migrate Databases from MS SQL 2000 (server A) to MS sql 2005 (server B).
The problem i have when i use database copy wizard is that it gives an error and the login will not be migrated .
I tried backup and restore of the databases as well as detach and attach.All cases the logins will have a problem.
For example say for database intranet all the tables stored procedures etc gets migrated but under security >>users (say intrauser) i double click user and the the login name wont appear .and when i try to close the window it says login name must be specified(SQLmanagerUI)
Hi all, i was just thrown into SQL stuff at my job. For now I need to complete a migration, but soon i'm being sent to training to make sure that I can do this easier later. Heres my question
I backed up the database, then restored it to the new server. That worked fine. I couldn't log in...so i did some searching and found out about the sp_change_users_login command, I got my login fixed and I can log in. Now, I have about 1000 other users to change and I don't want to do those manually. Noone is using this database, so if needed, I could back it up and restore it differnetly if needed or If someone can give me a .sql file to run to fix all usernames and tell me how to run a .sql (i'm that new to it) that would be REALLY appreciated. Anyway, thanks in advance, looking forward to SQL administration.
and it seems really straight forward. does this tutorial cover everything i need to do for data migration? do i need to watch out for anything? if anyone knows of a better tutorial please let me know. thanks for the help.
Hi all. I'll say from the get go that I'm no SQL guru. I'm primarily a web dev who has been given the data jobs kind of by default so I'm definitely no DBA.
Anyway, having established my noobness, I have encountered an issue. The employer recently decided to upgrade our databases from 2000 to 2005 and I have been tasked to migrate the data from old to new. I have discovered the Import/Export Wizard and got it to move all the data in a dev database we use...but there was one problem. It seems that the tables in 2000 that had columns designated as identity columns do not have the identity attribute when they arrive in 2005.
I haven't figured a way to alter them to give them that attribute once they're in 2005 so I'm wondering if there's something I can do/change in the import process that would retain the identity property of the columns if I were to re-import them.
This is my first migration attempt so dumping it and starting over is no great loss...but any help would be most appreciated.
I am trying to migrate few of my SQL jobs to SQL2K5. Can I simply script and execute them on the new environment. I hope the script is forward compatible.
------------------------ I think, therefore I am - Rene Descartes
We are using an ASP.Net Application with MS SQL 2000 as the backend and NHibernate as the Interface. Now we are planning to migrate to MS SQL 2005 with NHibernate only as the the interface. I wish to knwo what are the possible issues,risks and impacts if we go for this migration on the Application, NHibernate and the Enterprise Manager.
We migrated our database from SQL 2000 to SQL 2005. But we faced some problems, according to the requirements of our project we dont want to apply some constraints on some fields of some tables. But when we run the database script of our old database on SQL 2005, it applied many constraints which causing some serious problems in our project. There are about 100+ tables in our database and some one told me that we have to false every constraint manually. Now, my question is that is there any solution of our this problem.
Hi. Wondered if I might get a bit of advice on a minor collation problem I've experienced after migrating a database form SQL Server 2000 to 2005?
Users reported an error appearing in pages in a web-based application and I traced the problem to a stored procedure that was using a temporary table. I retained the original collation - SQL_Latin1_General_CP1_CI_AS - after migration and the error showing up was 'Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation.' This makes sense as I guess temporary tables are assuming tempdb's collation. Resolution in this case was fairly simple, which was to apply an explicit collation to one of the columns in the temporary table (it only had three columns, only one requiring the collation). However the longer-term question is should I: (a) resolve similar issues in the same way as and when they arise; (b) change the collation of the migrated database to that of the default for system and new databases under 2005 - i.e. Latin1_General_CI_AS; or (b) change the collation of tempdb and the other system databases to match that of the migrated databases (sounds risky)?
I would probably go for (a) or perhaps (b) but could use some expert advise on the matter.
I am trying to migrate DTS 2000 packages to SQL 2005 SSis using Package Wizard. When I am invoking and after the passing server information of source and destination, while reading the packages it is giving error
TITLE: Microsoft SQL Server
------------------------------
This wizard will close because it encountered the following error:
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.UI.WizardFrameworkErrorSR&EvtID=UncaughtException&LinkId=20476
------------------------------
ADDITIONAL INFORMATION:
Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index (mscorlib)
Could someone can help in this regards. As this is a important task for me and I am stuck on this which has to be resolved by end of today.
I had an SQL 2000 database with Turkish collation. (Note: Default database collation was Latin)
Today i transfered data from that to SQL 2005 with Latin collation.
There is no problem with old data. I transfered them correctly. But when i insert/update at new database, Turkish characters change to Latin. (Like i->i, g->g)
When i put an N before the value, it works.
For example INSERT INTO T1 (A) VALUES (N'A')
Must i put N to all of them? I think not. What can be the solution?
I've downloaded the migration tool to convert an Access 2000 DB to a SQL DB. The VB code utilizes DAO (3.6) for hourly automatic compaction and the creation of an encrypted security database. ADO is used for the data maintenance functions. I expect the current connection methodology of ODBC using Jet 4.0 will need to be modified (many articles here address this). All the SQL code is inline and also must be modified. The Coldfusion code utilizes Micrsoft Access with Unicode via an ODBC connection with only SQL Select statements. At another job, I migrated an Informix 7 database to MS SQL 7 and for the most part the SQL code remained the same except for the wildcard spec from * to %.
I'm looking for insights and/or shortcuts on this effort, primarily in the SQL command mods area. I'm perusing the threads here as we speak, but hoped someone knew of a specific thread I could go to....laziness is alive and well for us chronologically gifted people, i.e. over 55.
Recently our database has been migrated from SQL 2000 to SQL 2005 on a new server(machine) with windows 2003(previously windows 2000). If the database is retained on the same machine but with a named instance of 2005, the application(websphere 5.1) is behaving normal whereas if i configure the aplication to the new server it is running slow for some of the queries but not all.
This change will have to be implemented in production very soon. Any advise will be of great benefit
We are migration few database from SQL 2000 Enterprise Server to the SQL 2005 Enterprise Server (64 bit-Itanium Server)
Problem :
- The performance difference observer was not much (Just 15-18%)
- The CPU Utilization goes to 100% immediately, when the software login screen appears and it sustains in between 90% to 100%
- Multi-User Access (3 or more concurrent users), the sql performance is tremendously slow.
Steps followed for Migration:
- We have used the backup and restore method to migrate the data from SQL 2000 Enterprise Server to the SQL 2005 Enterprise Server (64 bit-Itanium Server).
- We ran the DBCC DBREINDEX for each affected tables
- We executed the sp_updatestats procedure for all the tables
- Upgraded the DB compatibility version to 90
- Installed the SQL 2005 Enterprise Server (64 bit-Itanium Server) Service pack 2.
One thing that we observed, was the memory usage, on SQL 2000 the sqlservr.exe uses around 1.5 GB where as on the SQL 2005 its just 120 MB.
A normal select query on 2000 Server took 11-12 sec, having 10 lac records, and the same query on 2005 took 1 min (3-5 sec CPU process taken by sqlservr and rest by the Sever Management Studio.
The only differance noted was that on 2000 the entire data was displayed at one go where as in 2005 the data was displayed at the 1st sec, and was filling the rest in the buffer, and to finally display entire data it took 1 min.
Also
when we run this query
select * from sys.dm_os_sys_info
one column os_priority_class shows a value = 32 ? what does this means.
In the MSSQLSERVER SERVICES, properties, there is a parameter displaying value
Advanced > Running Under 64 bit OS = No ? what does this means.
Could anyone pls suggest as to how to increase the sqlservr.exe memory area, and also how the enhance the performance.
I did the migration by detaching the database from SQL 2000 running on W2K Pro and attaching it to SQL 2005 running on XP Pro. Some queries with simple aggregate functions such as AVG() have been slowed by at least an order of magnitude. I understand that SQL server can intelligently adapt to improve the performance. I am not sure how much it can improve at this point of time.
I am trying to import data from SQL 2000 to SQL 2005
The Data schemas are the same in both (tables, relationships, key and triggers).
Using the wizard I am trying to import data from SQL 2000 to SQL 2005. The issue I face is to manage the Idenity columns. I do not want the identity values from the SQL 2000 DB which may be at say 5000, instead I want to use the identity values from the SQL 2005 database which will problably start at 1
Is there a way to do this, should I use a custom query instead of a direct table dump. If using a custom query do I need to just specify a Select query or does it have to be a specific "INSERT INTO Table ..." type query
If I do import the data directly with Identity "ON" how can I advance the identity column value to current +1 on the SQL 2005 table.
