Hi,
I'm trying to upgrade from SQL Server 2000 to 2005. The problem I am having is that when I try to attach the existing db files I get a message that says "database cannot be upgraded because it is read only or has read only files...."
Thing is... there is no write protection on the files.
Can anyone advise me on how to overcome this problem so that I can attach the db, please?
Thank you
Robert
I am currently using sql server 2000 and I have just installed sql server 2005 in a separate box that will be used as the production server so I will be upgrading to the new database server soon.
I was reading the upgrade options for this situation and one option is to detach the 2000 database, copy the mdf and log files to the new server and attach it to mssql 2005. Another option is to recreate the tables, views, etc. and export/import the data to the new server.
I would like to ask what the best option is for this situation because I am not sure what the advantages and disadvantages of just detaching/attaching and recreating the database in sql server 2005. If I just detach/attach the database, will there be any disadvantage in the performance because the database files were created in 2000 and is functioning because of backward compatibility in 2005? Would it be better to recreate the database in 2005 and import the data from 2000 so that the database would be running in a way that is designed for 2005?
I am not really sure of the differences of these upgrade options so any ideas would be greatly appreciated.
Thanks in Advance
-Voltaire
Hello, I have sql server 2000 personal edition on my PC and I have just got a 2005 DVD. I tried to install it but it is not working. I don't know how to manage my databases. As if there is no graphical managemnt tool. The 2005 is also Personal edition.
I reinstalled the sql 2000, and now I'm trying t upgrade to sql 2005, but still don't know how to do that.
Please someone help me!!!!!!!!!!
Probably this question has been asked hundreds of times and yet netsearch has not generated satisfactory enough answer, at least, to me.And OK, let's assume your organization has more than 200 employees,just one measure to indicate that it's not small and data processingneeds are quite extensive (for both OLTP and OLAP).We've heard so much about concurrency support, stability andperformance. Are there any real persuasive paper out there to talkabout it? Now, let me also put it in another perspective, say, you'rea Microsoft sql server sales guy or gal for that matter for newaccounts. What you got?Thanks.
View 5 Replies View RelatedI've inherited 6 sql server 2000 boxes. I've upgrade 3 with no trouble. now I have one that gives the message :
"your upgrade is blocked because of cross-language compatibility rules.
For more information about cross-language support, see the version..."
all servers are 2003, sp2. All SQL is Enterprise edition, default language is "english". even the collation order is
the same. why the cross language message? Any help would be good else I'll be forced to rebuild the DB and load application again. ugly!!
dave
Hi all,
My question might be a little bit unusual, but is it possible to upgrade SQL 2005 Express (the free version of SQL) to SQL 2000 Server without any loss of functionality?
Where do I have to pay attention to when doing this?
Thanks in advance!
MMQ
Hi All,
Currently we use SQL 2K SP4 and snapshot replication with a Central Publisher with Remote Distributor toplogy.
I am looking to upgrade or migrate our SQL servers to SQL 2005 and was wondering what is the best way to do this for our replicated architecture?
Is the best way to run the SQL 2005 Upgrade on all 3 servers (publisher, distributor, subscriber) and should it automatically upgrade the servers including the replication components? Is there anything i should consider/watch out for when doing the upgrade and it involves replication (namely snapshot replication)?
Thanks in advance.
I would like to upgrade a production active/passive SQL Server 2000 cluster to SQL Server 2005.
I've read all of the documentation I could find, and doing an in-place upgrade seems to be the way to go. (Despite the fact it scares the hell out of me.
But throughout all the documentation, I've yet to see some simple and fairly important questions answered.
How does the process of upgrading SQL Server work when you're dealing with a cluster?
Do you upgrade one machine then the other? If so, do you upgrade the active node first, or the passive node?
What happens if you're forced to failover from one instance to the other before you've had a chance to upgrade both to 2005? In other words, you failover from 2005 to 2000. Would that even work?
What happens if your upgrades fails for some reason? Is it easy to rollback the installation? If not, will reinstalling SQL Server 2000 cause any issues? Will it remember the previous configuration and simply fix the broken install?
Any help/insight would be greatly appreciated.
if it is possible to run a distributed query against 2000 from 2005, what would the OPENDATASOURCE parameters look like? I'd like to be able to pivot without copying my older 2000 db to 2005 or using linked servers..
For reference, here's an example of a distrib query that reads excel...
ie SELECT * INTO XLImport3 FROM OPENDATASOURCE('Microsoft.Jet.OLEDB.4.0',
'Data Source=C: estxltest.xls;Extended Properties=Excel 8.0')...[Customers$]
I have upgraded our test server and on non cluster production machine. My next server is a cluster and I don't have a test cluster server. Do I upgrade the active node and that is all or am I going to need to fail it over and upgrade the other node.
Also the prerequesite for the upgrade advisor is .net 2.0 I am going to up that on each server one at a time but I am only going to add the upgrade advisor to one node is that ok.
I read the SP1 documentation and it clearly states only patch the active node and do not patch the inactive nodes.
I used the SQL Server 2005 Upgrade Advisor to upgrade from SQL Server 2000 Enterprise to 2005 Standard. The only complaint I got concerned DTS packages, but I had none anyway. When I open SQL Server Management Studio, I can run queries, but they're against tables in the old 2000 databases. The SQL engine and Server agent are version version 8.0. Not surprising that new TSQL statements like 'BACKUP SERVICE MASTER KEY TO FILE' won't work.
Do I have to uninstall my previous version before upgrading?
Thanks.
I'm trying to upgrade the Default Instance of MSDE 2000 Release A which is installed with Mixed Mode and strong password to SQL Server 2005 Express in a Windows 2000 Server with SP4. On the Upgrade Logon Information screen, if I select SQL Server Authentication Mode, it will give me this message:
SQL Server Setup Cannot Upgrade the specified instance by using SQL Server Credential. You must use Windows Authentication credential for the upgrade.
Thanks for any help.
Hi All,
I have just migrated couple of test databases
from SQL Server 2000 to 2005 (side by side).
I also migrated the server level logins using SSIS transfer logins task, available on SSIS 'Transfer logins', I selected all the databases that I have migrated so that I have all database users account in server logins (to avoid orphaned users); but I don't have all the database users in server logins, also the sys.sysusers doesn't have the database users, that I have moved to SQL 2005. Can anybody help?
Also do I need to back up the SQL Server 2000 database and restore it on SQL 2005? What impact this operation can have?
Thanks for your time..
Bidyut
According to this http://msdn2.microsoft.com/en-us/library/ms143393(d=robot).aspx, it seems that it cannot. But is this a complete chart?
Thanks for any help,
Peter
In our application we use the ADODB.Recordset.
In SQL server 2000
If there was a view that joined 2 tables and I accessed the view the 2 ID fields in the view would still have the AutoIncrement attribute still set to true so that I knew those were Identity fields.
In SQL server 2005
I dont' know why but if you reference a View that has Identiy AutoInc fields in ADO it doesn't keep those properties.
Also for whatever reason we Set the ID field to 0 to let ourselves know its a new Record. SQL 2000 let it happen and assumed it to be null where as By Setting the ID to 0 in SQL 2005 causes it to blow up on me.
Is there some sort of setting in SQL that can make SQL 2005 work like SQL 2000 in these two instances...
Hi.
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?
I'm new to this so please advice? Thanks!
Hello Gurus:
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?
Thanks in advance.
Regards,
Arunesh
I'll start off by saying these questions were submitted to Microsoft and no
one can give us an answer without them doing a source code review. Their
response was "these are internal BCP scripts that are used by SQL"....yes, I
know that....that doesn't help to explain why the system created them. At
this point, I don't want my compary to pay support hours for Microsoft
personnel to learn what their software does.
--------------------
We've had merge publication in place for several years.
Last year, we added some tables/articles to publications.
After the upgrade from SQL Server 2000 SP4 Standard to SQL Server 2005 SP2
Standard, when the snapshot was run, the system created some new files that
had never existed before. Also, and more importantly, these files were only
created for the articles added after the initial snapshot was created.
Articles existing in the intial snapshot did not have these type of files
created.
Examples of these files for a SA_MOVE table that was added to an existing
publication:
MSmerge_contents_SA_MOVE.bcp
MSmerge_contents_SA_MOVE_forall.bcp
MSmerge_rowtrack_SA_MOVE90.bcp
sysmergesubsetfilters_SA_MOVE.bcp
sysmergesubsetfilters_SA_MOVE90.bcp
Also some new bcps created were:
MSmerge_contents90_forall.bcp
MSmerge_genhistory90.bcp
MSmerge_rowtrack90.bcp
sysmergesubsetfilters90.bcp
The system wanted to apply these files before it would start synchronizing
data so they had to be delivered to the subscriber. It appears it was the
sysmergesubsetfilters_ files that it wanted to apply. These are all 0 in
size and we do not have filter on(at least not as far as I know...see the
addmergearticle code below).
New databases created this year that had all of the articles defined in the
publication before the initial snapshot was taken did not get these
additional files created, nor did the system want to try to send files to the
subscriber before syncrhonization could begin.
This is an example of how an article had been cretead under SQL Server 2000
when adding a new database, before an initial snapshot is run:
exec sp_addmergearticle @publication = N'Last', @article = N'SA_MOVE',
@source_owner = N'dbo', @source_object = N'SA_MOVE', @type = N'table',
@description = null, @column_tracking = N'true', @pre_creation_cmd = N'drop',
@creation_script = null, @schema_option = 0x000000003000EFF1,
@article_resolver = null, @subset_filterclause = null, @vertical_partition =
N'false', @destination_owner = N'dbo', @verify_resolver_signature = 0,
@allow_interactive_resolver = N'false', @fast_multicol_updateproc = N'true',
@check_permissions = 0
This is an example of how an article was added under SQL Server 2000 to an
existing publication that already had the initial snapshot run:
exec sp_addmergearticle @publication = N'Last', @article = N'SA_MOVE',
@source_owner = N'dbo', @source_object = N'SA_MOVE', @type = N'table',
@description = null, @column_tracking = N'true', @pre_creation_cmd = N'drop',
@creation_script = null, @schema_option = 0x000000000000EFF1,
@article_resolver = null, @subset_filterclause = null, @vertical_partition =
N'false', @destination_owner = N'dbo', @auto_identity_range = N'false',
@verify_resolver_signature = 0, @allow_interactive_resolver = N'false',
@fast_multicol_updateproc = N'true', @check_permissions = 0,
@force_invalidate_snapshot = 1
A few questions:
Does anyone have an idea why the system created these files are part of the
2005 upgrade?
What is the real purpose of the files with names such as _forall.bcp ?
Thanks for any help/info on this,
Doug
We are in the process of upgrading to a new SQL 2012 server but we have many packages that load data from dbf files created with FoxPro into one of our databases. We have not converted the packages and run them with DTS but we get the following error:
Error: 2013-08-26 11:05:27.36
Code: 0xC0209303
Source: BenchmarkLoad Connection manager "OLEDB NPIONE.Investment.middleTierSQL"
Description: The requested OLE DB provider SQLNCLI.1 is not registered. If the 64-bit driver is not installed, run the package in 32-bit mode. Error code: 0x00000000.
[Code] .....
I searched for OLEDB and ODBC drivers for SQL 2012 64 bit but cannot find any that is newer than the 2005 that we have. What can I do short of changing the source files to overcome this issue?
How to identify whether the files are in read write or read only?
View 1 Replies View RelatedI have two database files, one .mdf and one .ndf. The creator of these files has marked them readonly. I want to "attach" these files to a new database, but cannot do so because they are read-only. I get this message:
Server: Msg 3415, Level 16, State 2, Line 1
Database 'TestSprintLD2' is read-only or has read-only files and must be made writable before it can be upgraded.
What command(s) are needed to make these files read_write?
thanks
Hello,
I have a project where I have to upgrade SQL 2000 to 2005. When we are upgrading we are going to move to new server so server name will change. Most of our applications have a hard coded connection string. Applications are developed with Classic ASP, .NET 1.1 and 2.0 as well.
Now the question is what is the best way to do this? Changing all the connection string will be a very painful task as we have many applications.
Can anyone suggest a way where we can achieve this without changing all the connection strings?
Thanks in advance.
Tareq
what are some of the issues that we might face while upgrading from SQl 2000 to SQl 2005? Actually I have to create upgrade plan for path from MS 2000 to MS 2005.
Any suggestions will be appreciated.
Thanks
Hi,
I was wondering if anyone could point me in the right direction for upgrading from SQL 2000 to SQL 2005?
I was under the impression that it was as easy as following an upgrade path after popping in the CD, but I realized it's not.
I'm a Systems Administrator who has installed both version in stand alone systems, but never tried an upgrade.
Thanks for your help.
Hello,
I would like to upgrade sql server 2000 to sql 2005. So Can I install the sql server 2005 on the same server where sql 2000 is already running and then use the database upgrade wizard. Or should I install the sql server 2005 on a different server.
Thanks
I have a sql 2000/2005 side-by-side install on a single server. I right-click a sql 2000 database, select All Tasks, and the Copy Database to upgrade a sql 2000 database. In the "Copy Database Wizard" I see the message:
"To use the detach and attach method SQL Server Agent must run under an Integration Servicers Proxy account that can access the file system of both the source and destination servers."
1. What does that mean?
2. I decided to click "Finish" in the wizard, and the database copy seemed to work fine. Whaterver 1) means does, by default, the SQL Server Agent already run under this "Integration Services Proxy" account. (Rememberr the upgrade process did work).
TIA,
barkingdong
Hey Guys,
Looking for some type of solution on this issue. I'm going from SQL2000 to SQL2005 and I run the upgrade advisory tool and all and I'm going through the procedures of getting our SQL server updated to SQL2005, when I attempt to run that analyzer to take a look at how well the migration will go. I get a timed out error message on the fallowing.
ORDERBYORDINALS
FTCATPROPITEMCOUNT
OLDSYSTEMTABLES
DROPSYSOBJ
HOSTIDRETURN
FTPROPS
QRYGOVCOSTLIMIT
FTCATALOGNAMERESTRICTION
SPCONFIGURE
INVALIDCHAR
OPENXMLWITH
XPAGENTPROXY
UPDATETEXT
SPHELPTRIGGERNEWCOL
DISKINIT
SYSPERFINFO
DEPRECATEDSP
OLDDBCC
ORDERBYALIAS
Exact error message and its always the same for each entry.
"Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding"
Any help in this are would be greatly appreciated, all other issues have been resolved I'm just stuck on this and I don't want to upgrade until the advisory tool gives me the ok to.....
Thanks in advance.
All,
I am looking for upgrading SQL 2000 databases to SQL 2005.Has anybody got a detailed plan /Documents for doing so?.
Thanks and Regards
Avijit Macker
I am in the beginning of upgrading a SQL 2000 DB on a Small business server to a 64 bit 2005 DB on a new box. Is my best method of upgrading to use the "copy" DB function in 2005? If so, what do I need to do to install the management tools on the 2000 box - since this is a 32 bit edition, and I have the 64 bit media?
View 1 Replies View Related
I got a requirement to upgrade only One SQL 2000 to SQL 2005 server. i did check that there are only databases in this server along with Linked server. I am looking for a best practice document for SQL upgrade and any thoughts or experience any one has faced during upgrade.
Other question is what about if there is a DTS on the server. right now on this particular server there is no DTS but in coming weeks i may need to upgrade other server which is having DTS as well. I have worked alot on SSIS packages but want to see if DTS will be converted to SSIS packages or i will have to manually do it.
Thanks
Hi,
We have 2 .net 1.1 applications using Microsoft SQL Server 2000 Enterprise Edition. To connect to database we are using nHibernate 0.6 for one application and Microsoft Enterprise Library Data Blocks Ver 1.0 in another.
We are planning to upgrade SQL servers of both applications to SQL 2005 Enterprise edition and retain .net 1.1 framework. Are nHibernate 0.6 and Microsoft Enterprise Library 1.0 data blocks compatible with the SQL 2005? Are any upgrades required for these as well?
We ran SQL upgrade advisor report on these applications, there weren't any changes to table/ stored procs suggested. Could that mean that the existing table design and stored procs are compatible with SQL 2005?
Thanks in Advance,
Abhijith Bharadwaj
Hi all,
I just ran sql upgrade advisor and got the following message:
"You can use SQL Server 2005 tools to edit your existing DTS packages. However, upgrading or
uninstalling the last instance of SQL Server 2000 on a computer removes the components required
to support this feature. You can retain or restore these components by installing the special
Web download, €œSQL Server 2000 DTS Designer Components,€? from the Microsoft Download Center
before or after you upgrade or uninstall SQL Server 2000."
I do have several DTS packages in my sql server 2000 database. does that mean if I upgrade my current 2000 database to 2005, those dts will be gone. But I can download sql server 2000 dts deginer components on our new sql 2005 database server before I upgrade. Then when I restore my sql 2000 database on our new 2005 server, eveything would be OK? I am not sure if my understanding is correct.
My advisor is on my local computer and I am running analysis against a remote database(on our intranet),€œSQL Server 2000 DTS Designer Components,€? should be intalled on my local computer or remote database server? what steps I should take in order to retain my dts package or transform it into something else?
can you shed light on me?
Thanks.
Betty
I am going through upgrading our current installation of SQL 2000 to 2005. When I install 2005 it doesn't seem to upgrade the server, but only installs the server tools. Do I need to completely remove 2000 in order to upgrade? Thanks!
View 4 Replies View Related