SQL Server 2000 Migration To SQL Server 2005 Collation Change - Method?
Jan 24, 2008
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. 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 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 need a SQL Server 2005 SP2 instance with a collation of SQL_Latin1_General_CP850_BIN2. After installing SP2, the collation is SQL_Latin1_General_CP850_BIN, and none of the patches I can find seem to want to work (they are all apparently written for SQL Server 2000).
Hi,If I have a database with collation Sequence X and I change thecollation sequence of database to Collation Sequence Y , do I have tomigrate the data of tables with collation Sequence X to collationSequence Y or SQl server takes care of migrating the data internally.Thanks in advance.-Kalyan
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 are going to upgrade one of our SQL Server 2000/Win200 instance to SQL Server 2005/Win2003. Currently, the SQL Server 2000 which contains about 30 database. This is my plan:
Install SQL Server 2005/Win2003 on a new instance Backup SQL Server 2000 database instance (how do I back all 30 database at the same time?)
Then do a Restore from the SQL Server 2005 instanceIs this a good method or using the "Copy Database Wizard" is better method?
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 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.
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!
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've restored a SQL Server 2000 database with a Latin1_General_BIN collation from a .dmp file to a SQL Server 2005 server with a default collation of SQL_Latin1_General_CP1_CI_AS. When I try to change the database collation I get hundreds of the following error:
The object 'CK_PM10200_GLPOSTD_00AF8CF' is dependent on database collation. So, in this case, is it even possible to change the collation if there are objects in the database that are dependent on it?
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.
Complete: SetPackageInstallStateAction at: 2007/9/23 7:33:43, returned true Running: DeterminePackageTransformsAction at: 2007/9/23 7:33:43 Complete: DeterminePackageTransformsAction at: 2007/9/23 7:33:43, returned true Running: ValidateSetupPropertiesAction at: 2007/9/23 7:33:43 Complete: ValidateSetupPropertiesAction at: 2007/9/23 7:33:43, returned true Running: OpenPipeAction at: 2007/9/23 7:33:43 Complete: OpenPipeAction at: 2007/9/23 7:33:43, returned false Error: Action "OpenPipeAction" failed during execution. Running: CreatePipeAction at: 2007/9/23 7:33:43 Complete: CreatePipeAction at: 2007/9/23 7:33:43, returned true Running: RunRemoteSetupAction at: 2007/9/23 7:33:43 <Func Name='CProcessCtrl::GetInstallPath'> <EndFunc Name='CProcessCtrl::GetInstallPath' Return='0' GetLastError='0'> Error: 0x80070050 TaskScheduler::NewWorkItem for SQL Server Remote Setup Error: 0x80070005 TaskSchedulerWorkItem failed to save the task [SQL Server Remote Setup ] Complete: RunRemoteSetupAction at: 2007/9/23 7:33:43, returned false Error: Action "RunRemoteSetupAction" failed during execution. Error information reported during run: Attempting to determine log files for remote install. Connection to remote computer's scheduler service. Creating new workitem. Deleting existing work item and trying again... Starting remote setup onSQL1N2 Error: 80070005 Access is denied. Running: PopulateMutatorDbAction at: 2007/9/23 7:33:43 Complete: PopulateMutatorDbAction at: 2007/9/23 7:33:43, returned true Running: GenerateRequestsAction at: 2007/9/23 7:33:43 SQL_Engine = 3 SQL_Data_Files = -1 SQL_Replication = -1 SQL_FullText = -1 SQL_SharedTools = -1 SQL_BC_DEP = -1 Analysis_Server = -1 AnalysisDataFiles = -1 AnalysisSharedTools = -1 RS_Server = -1 RS_Web_Interface = -1 RS_SharedTools = -1 Notification_Services = -1 NS_Engine = -1 NS_Client = -1 SQL_DTS = -1 Client_Components = -1 Connectivity = -1 SQL_Tools90 = -1 SQL_WarehouseDevWorkbench = -1 SDK = -1 SQLXML = -1 Tools_Legacy = -1 TOOLS_BC_DEP = -1 SQL_SSMSEE = -1 SQL_Documentation = -1 SQL_BooksOnline = -1 SQL_DatabaseSamples = -1 SQL_AdventureWorksSamples = -1 SQL_AdventureWorksDWSamples = -1 SQL_AdventureWorksASSamples = -1 SQL_Samples = -1 Complete: GenerateRequestsAction at: 2007/9/23 7:33:44, returned true Running: CreateProgressWindowAction at: 2007/9/23 7:33:44 Complete: CreateProgressWindowAction at: 2007/9/23 7:33:44, returned false Error: Action "CreateProgressWindowAction" failed during execution. Running: ScheduleActionAction at: 2007/9/23 7:33:44 Complete: ScheduleActionAction at: 2007/9/23 7:33:45, returned true Skipped: InstallASAction.11 Waiting for actions from remote setup(s) Breaking wait state and aborting package due to cancel code received: 1602 Remote setup(s) are ready Notify package action is determined: 1602 Error Code: 0x800700e9 (233) Windows Error Text: No process is on the other end of the pipe.
Source File Name: remotemessageliboverlappedpipelistener.cpp Compiler Timestamp: Sat Oct 7 09:43:54 2006 Function Name: sqls:verlappedPipeListener::writePipe Source Line Number: 294
Notification failed to send. ---- Context ----------------------------------------------- sqls::HostSetupPackageInstallerSynch::installAction
Removing machine from list of targets to sync. Skipped: Action "InstallASAction.11" was not run. Information reported during analysis: All installs have been cancelled, so package: "sqlsupport", referred by package: "as", will not be installed. Skipped: InstallASAction.18 Skipped: Action "InstallASAction.18" was not run. Information reported during analysis: All installs have been cancelled, so package: "owc11", referred by package: "as", will not be installed. Skipped: InstallASAction.22 Skipped: Action "InstallASAction.22" was not run. Information reported during analysis: All installs have been cancelled, so package: "bcRedist", referred by package: "as", will not be installed. Skipped: InstallASAction.9 Skipped: Action "InstallASAction.9" was not run. Information reported during analysis: All installs have been cancelled, so package: "msxml6", referred by package: "as", will not be installed. Skipped: InstallDTSAction Skipped: Action "InstallDTSAction" was not run. Information reported during analysis: All installs have been cancelled, so package: "dts", will not be installed. Skipped: InstallDTSAction.11 Skipped: Action "InstallDTSAction.11" was not run. Information reported during analysis: All installs have been cancelled, so package: "sqlsupport", referred by package: "dts", will not be installed. Skipped: InstallDTSAction.12 Skipped: Action "InstallDTSAction.12" was not run. Information reported during analysis: All installs have been cancelled, so package: "sqlncli", referred by package: "dts", will not be installed. Skipped: InstallDTSAction.18 Skipped: Action "InstallDTSAction.18" was not run. Information reported during analysis: All installs have been cancelled, so package: "owc11", referred by package: "dts", will not be installed. Skipped: InstallDTSAction.22 Skipped: Action "InstallDTSAction.22" was not run. Information reported during analysis: All installs have been cancelled, so package: "bcRedist", referred by package: "dts", will not be installed. Skipped: InstallDTSAction.9 Skipped: Action "InstallDTSAction.9" was not run. Information reported during analysis: All installs have been cancelled, so package: "msxml6", referred by package: "dts", will not be installed. Skipped: InstallNSAction Skipped: Action "InstallNSAction" was not run. Information reported during analysis: All installs have been cancelled, so package: "ns", will not be installed. Skipped: InstallNSAction.11 Skipped: Action "InstallNSAction.11" was not run. Information reported during analysis: All installs have been cancelled, so package: "sqlsupport", referred by package: "ns", will not be installed. Skipped: InstallNSAction.12 Skipped: Action "InstallNSAction.12" was not run. Information reported during analysis: All installs have been cancelled, so package: "sqlncli", referred by package: "ns", will not be installed. Skipped: InstallNSAction.18 Skipped: Action "InstallNSAction.18" was not run. Information reported during analysis: All installs have been cancelled, so package: "owc11", referred by package: "ns", will not be installed. Skipped: InstallNSAction.22 Skipped: Action "InstallNSAction.22" was not run. Information reported during analysis: All installs have been cancelled, so package: "bcRedist", referred by package: "ns", will not be installed. Skipped: InstallNSAction.9 Skipped: Action "InstallNSAction.9" was not run. Information reported during analysis: All installs have been cancelled, so package: "msxml6", referred by package: "ns", will not be installed. Skipped: InstallRSAction.11 Skipped: Action "InstallRSAction.11" was not run. Information reported during analysis: All installs have been cancelled, so package: "sqlsupport", referred by package: "rs", will not be installed. Skipped: InstallRSAction.18 Skipped: Action "InstallRSAction.18" was not run. Information reported during analysis: All installs have been cancelled, so package: "owc11", referred by package: "rs", will not be installed. Skipped: InstallRSAction.22 Skipped: Action "InstallRSAction.22" was not run. Information reported during analysis: All installs have been cancelled, so package: "bcRedist", referred by package: "rs", will not be installed. Skipped: InstallSqlAction Clustered feature detected: SQL_Engine Clustered feature detected: SQL_FullText Loaded DLL:C:Program FilesMicrosoft SQL Server90Setup Bootstrapsqlsval.dll Version:2005.90.3042.0 Windows Error Text: User cancelled installation.
Source File Name: sqlchainingsqlchainingactions.cpp Compiler Timestamp: Thu Nov 16 20:32:00 2006 Function Name: sqls::ReportChainingResults:erform Source Line Number: 3667
---- Context ----------------------------------------------- sqls::RunRemoteSetupAction::waitForRemoteSetupComplete king package: "patchRS2000" as failed due to cancel code received from cancel source: 1602 sqls Delay load of action "UploadDrWatsonLogAction" returned nothing. No action will occur as a result. Message pump returning: 1602
Hi. I don't know how to change the collation in SQL Server 2000, my collation is Modern_Spanish_CI_AS, if somedoby knows the procedure to change the collation I would be thankful. Thank you again and best regards. Christian
I need to select collation settings to support chinese characters. As i came to know that i need to select 950 character set. But problem is that i am not able to find the option for chinese characters i.e, 950 character set in the collation settings of the setup. It will be helpful if anyone could suggest me if there is any other option to set while set up or in an existing sql server instance to support chinese character data.
We are in the process of Migrating our SQL Server 7.0 databases to SQL Server 2000. We have purchased two new servers for this process. What is the best method for the Database Migration ? - Copy Database Wizard ? - DTS ?
Dear Friends,I am about to migrate a Visual FoX Pro 7.0 & 5.0 databases to MS SQLServer 2000. I would like toshare the experience with you, if you have undergone such a task. Isthere any utility for achievingthis.Any white paper or link for guidance on the same.I wannted to migrate the whole database to MS SQL Server 2000. Iwanted to migrate the tablestructures and procedures to MS SQL Server 2000.Please shed some light please.RegardsKumar
I€™m currently evaluating SQL Server 2005 to what advantages there would be to upgrading from SQL Server 2000. Our existing systems make much use of DTS so it critical for us to be able to run SQL Server 2000 DTS packages in SQL Server 2005. Having installed the Enterprise SQL Server 2005 CTP successfully on a new Windows 2003 server and following the advice to install Legacy Components I find the Migration Wizard (under Legacy> Data Transformation Services) fails with the following error after entering source and target dialogs: This wizard will close because it encountered the following error: Additional Information: Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index (mscorlib) Also when trying to open a structured storage DTS file I incur another error: Unable to load DTS 2000 Runtime. This component may have not been installed (Microsoft.SqlServer.DtsObjectExplorerUI) This error seems to imply that the DTS 2000 Runtime needs installing. Can this component be downloaded and installed separately?
When I migrated data from one SQL Server to another I got collection problems because collation of the target server was different from the source one.
The best solution I thought about was to change collation of the database in target server to be equal to the server collation so that when a temporary table is created, and the collation used would be the server collation, no error would occur. All sounds logic, but, after I ran ALTER DATABASE command and changed the collation of the database, I verified that all varchar fields of all database tables retained the old collation, not the new database collation I set.
Is there any way to change the collation of all fields at once when I change the database collation?
hi, i must convert my SqlServer2000 to SqlServer2005. I just do it on my Computer and i run a component "SQL Server upgrade wizard" it convert my SQLServer. But now i must do it on my Server Web and if i run that component it give me an error : "must run SQL 6.5" and i don't installed it. Can i download it with all right migration? thank you
I have a client that is moving their web ap (which has already been developed) from one host to their own servers. The problem is that they don't have MS SQL Server 2000, but they have MSDE. All the code is already writen to work with SQL SERVER 2000.
I have a couple of questions:
1. Can I safely assume that all this code will work with MSDE and all I have to change is the connection string? For example:
SqlConnection myConn = new SqlConnection(connstring);
In other words, can I still use the SqlClient classes to work with MSDE, or will I have to modify the code?
2. Will it be a problem creating the tables and migrating the data from SQL SERVER to MSDE? Can I use Enterprise Manager to do this?
3. I never had to remotely (or even locally) connect to a MSDE database alone, I always develop with a SQL Server db. Can I use a similar connection string for the MSDE database? Do I have to create a data provider on the local machine? Can you give me an example of a MSDE connection string?
