I did a backup of a SQL2000 database (named Winstis) using the 2005 management studio. I then created a blank database on my 2005 instance (named Winstis). I then tried to do a database restore to the new 2005 database. I got an error:
System.Data.SqlClient.SqlError: The backup set holds a backup of a database other than the existing 'Winstis' database. (Microsoft.SqlServer.Smo)
I even tried the option to Overwrite Existing database and I got a different error:
System.Data.SqlClient.SqlError: The operating system returned the error '32(The process cannot access the file because it is being used by another process.)' while attempting 'RestoreContainer::ValidateTargetForCreation' on 'D:Program FilesMicrosoft SQL ServerMSSQLData est.ldf'. (Microsoft.SqlServer.Smo)
Also the 2005 instance database is on C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDataWinstis_Data.mdf
and the 2000 instance is on
D:Program FilesMicrosoft SQL ServerMSSQLDataWinstis_Data.mdf
How can I accomplish getting the database from 2000 to 2005 with all tables, store procedures, and functions?
Hi all,I'm having a problem restoring backup from 2000 to 2005. The actualrestore process went ok. However, the database user of the restoreddatabase is missing a Login Name. I've made sure that the Login Nameis created in 2005. Also tried deleting the user, but couldn't theuser is db owner. Is there any way that I can assign a Login Name forthis database user or maybe drop this user and assign another one?Regards,Gerd
I have a database that is in the SQL Server 2000 compatability mode on my SQL 2005 server. I am trying to restore a backup of this database on my SQL Server 2000 database on another server and keep getting strange messages. First trying Red-Gate and then plain SQL Server with no luck.
It seems as I remember that the 7.0 and 2000 compatibility issue between backups did not arise when the compatibility mode was set to 7.0.
Is this "planned" behavior or an "undocumented feature"??? Anyone else have success doing this?
I have three instances running on my sql 2008 r2 enterprise.I have taken full backup of one database from default instance.I login both the instances thru sa account.Now when I try to restore that backup on another instance it gives me the following error....
TITLE: Microsoft SQL Server Management Studio Restore failed for Server 'WRCP2F1CWS315TEJA'. (Microsoft.SqlServer.SmoExtended) System.Data.SqlClient.SqlError: The operating system returned the error '32(The process cannot access the file because it is being used by another process.)' while attempting 'RestoreContainer::ValidateTargetForCreation' on 'C:Program FilesMicrosoft SQL ServerMSSQL10.MSSQLSERVERMSSQLDATAfcms.mdf'. (Microsoft.SqlServer.Smo)
what can be done to restore bakup in another instance ...
moving to a new sql server box because of a problem with the SAN its connected to. started my named instance in single user mode and restored master. sqlserve.exe -c -m -s ovops now the instance won't start. tried starting it with the -t3608 switch.. won't start!! Its because my drive configuration is different on the new server than it was on the old server, I cannot start the instance because it is expecting model, msdb, temdb and all of the user databases on drives that don't exist?? what can I do?????
Hi,I am working in a sql server 2000 environment but my customer uses sql server 7. Is it possible to use backup and restore to transfer the database or should I set up a sql server 7 for development?The database only contains tables and views...ThanksKoen
I am new to SQL server and I need your advise on the following .
1. We have two SQL 7.0 Databases at a distant location and we want to move those databases to our location.
2. we plan to take the SQL backup of the databases in tape ( 4Gb and 2 Gb in size) , bring them here, restore them to SQL 2000 server. - Is this possible , DO SQL 7.0 backups are restored on SQL 2000 without any problems ?.
Also, we plan to take log backups of the DBs at the source after the initial full backups and apply them at the target SQL 2K databases till we cut over to the Target Databases.
Ehat would be the best method of doing this? All your suggestions , pointers to real life scenarios like this, solutions are welcome.
Please let me know if you need any more informations , before suggesting any solution.
Hello,Recently I've tried to restore backup made on SQL Server 6.5.Unfortunately, the only version of SQL Server I currently possess is SQLServer 2000. I have access only to that backup, because I've made it afew years ago, and the main db file doesn't exist any more ;( I would begrateful if you could help me a little ;)RegardsR.Kruk
When I try to restore my SQL Server 2000 backup file to a newly installed copy of SQL Server 2005 Express using Studio Express, I get the following error:
The backup set holds a backup of a database other than the existing 'UpperBridge' database. (Microsoft.sqlservfer.Express.smo)
The backup is made from an SQL Server 2000 database called 'UpperBridge'
I am trying to restore to a database called 'UpperBridge' which I created under 'New databases' in Studio Express.
I want to read certain data from the backup file of MS SQL 2000 without restoring the database backup file. Based on the data selected I will manage the further functionality such as restoration of the backup file. Is it possible to read some data from MS SQL 2000 backup file without restoring? If yes then please let me know how?
We would like to install Sql 2005 Enterprise Edition (including database engine, reporting service, integration service and analysis service) as a sepearte instance on a server which already has Sql 2000 with reporting services and analysis services. We do not want to disturb the existing sql 2000 setup.
If we do that then what will happen to my earlier sql 2000 reporting service? Will it be upgraded to sql 2005 reporting service? I heard that reporting services are instance unaware application. Where will be the default reporting service database available?
i'm trying to set up one of the asp.net website starter kits and part of the process is to backup the sql express db and then import it into the sql 2005 at the web hosting account. it's not working and i'm wondering if there's any difference between the backups they make. the sql express makes a file with a .bak extension and the sql 2005 at the host makes a file with a .sqlbak extension. i was assuming that was just a naming thing and not a structural thing but the host's tech support has said: "This sort of thing happens when the database being imported is not properly formatted. You can try downloading and using sql express from microsoft to see if you can do it manually, but most likely you will need to save your database again properly set for import to an mssql server rather than however you did." all i had done was rename the .bak file from express to .sqlbak as that was the choice for backup files. i will note that it also failed importing the .mdf, which works fine locally with the site but i did make some changes to it from the original that came with the starter kit. should a backup file made with sql express (using sql management studio express, by right clicking on the file and choosing tasks > backup) normally be importable by sql 2005? or, i suppose, does it make sense that a db that works fine locally with sql express (within a visual web developer express project anyway) would actually be "formatted" in a way that would cause it to fail to import into sql 2005? thanks much for any assistance.
I am currently having a problem with restoring a backup made on SQL 2000 XP machine onto a Windows server 2003 machine with SQL Express 2005. I am getting the following error
"System.Data.SqlClient.SqlError: The operating system returned the error '5(Access is denied.)' while attempting 'RestoreContainer::ValidateTargetForCreation' on 'C:Program FilesAvidian TechnologiesProphetavidian.mdf'. (Microsoft.SqlServer.Express.Smo)"
I'm not sure what is going on becuase I have no issues installing the backup on my XP Pro machine that has SQL Express 2005 Dev edition. So what I did was restore the backup on to SQL Express 2005 on my dev machine and backup again. Unfortunately when I took the newly created backup and tried again to restore the database on to my window server 2003 machine it failed again. Exact same message was displayed.
The box I am trying to connect to is running two instances of SQL Server. There is a SQL Server 2005 instance which is the default. There is a SQL Server 2000 instance which is named 'SQLSERVER'. I can connect to the SQL Server 2000 instance no problem:<add key="ConnectionString" value="server=MYPCSQLSERVER;database=mydatabase;user id=****;password=****" /> However, I am having trouble connecting to the Default SQL Server 2005 instance. I have tried: <add key="ConnectionString" value="server=MYPC;database=mydatabase;user id=****;password=****" /> but it doesn't work. I have tried explicitly setting SQL Server 2005 to use port 1434 (as SQL Server 2000 is running on port 1433), and then used: <add key="ConnectionString" value="server=MYPC,1434;database=mydatabase;user id=****;password=****" /> but this doesn't work either.
Am I mssing something here? Any help much appreciated Thanks...
I'm having an issue with stored procedures after restoring a db from 2000 -> 2005.
If any stored procedures isnt owned by dbo (eg tomsqluser.updateItems rather than dbo.updateItems) then it just wont work and Studio Management Server doesnt give the permission to change it to dbo.
hi there, I've got a problem while restoring a DB from sql server 2005 to sql server 2000 I always got an error message 3169. Please I want if it's possible to make it, it urgent.
Hi Guys, I have two servers at my site out of which one is our production server (on SQL 2000) and the other being a reporting server (SQL 2005). Now the question i have are the following..
Q1) Can i restore an hourly differential backup of my SQL 2000 to SQL 2005? Q2) If yes, are there any specific way i need to go about it other than the conventional Restore with NoRecovery option? Q3) If the answer is no to Q1, then is there any 3rd party software that does this(restoring differentials from 2000 to 2005)?
I had tried this once some time back and at that time it failed to keep the database in a state(norecovery) where in it would accept timely differential db restoration.
We are experiencing major performance issues after restoring SQL Server 2000 db into newly setup hardware environment. The application is faster on another environemnt running on Windows 2000 server with SQL Server 2000.
We have replicated exact same hardware setup, but only fifference is we are running latest version windows server (2003) and latest version of SQL Server (2005). So far we have troubleshooted the bottleneck to be one of the trigger that is inserting data into a table in one of the stored procedures. The same SP takes 9 mins to execute whereas on our env it takes around one hour. If I disable the trigger it executes in 2 minutes.
After restoring, we have executed
exec sp_updatestats
DBCC UPDATEUSAGE
DBCC DBREINDEX all tables
Set Compatibility level to SQL SERVER 2005 (90).
Now we are installing latest Service Pack for both OS and SQL Server.
Is it possible to restore a SQL 2000 backup with Binary Order collation to a new SQL 2005 installation with Dictionary order, case-insensitive. Is this something I can do during the restore process or would I need to change it after?
I tried to restore a database which I backuped from MS SQL 2000 to SQL Express 2005 but it always failed with the following error message. What could be the problem?
Restore failed for Server 'SERVSQLEXPRESS'. (Microsoft.SqlServer.Express.Smo)
Additional information
System.Data.SqlClient.SqlError: The backup set holds a backup of a database other than the existing 'gtp' database.
We have a set of databases some are fully read-only others have read-only file groups, is there any way to restore backups of these taken on an MSDE 2000 to an SQL Express 2005 instance?
When doing the inplace upgrade we change these to read-write before the upgrade and set them back after the upgrade.
These databases are used in the field by customers althought the controlled upgrade requires a backup before (and blocks if it fails) and tries a backup after if the post upgrade backup fails (due to disk space) we might need to recover from this odd situation.
The only solution I have is install MSDE some place restore to this then do the controlled upgrade again, any other ideas?
I don't know if this is the right forum to post this question, but here it goes.
We have restored into sql 2005 the database backups made in sql 2000. We connect with trusted connection and application roles, and when trying to execute a transaction to another database (with the guest user), we get a permission error.
Does anyone know if, apart from restoring the databases, we should do something else to get the guest user working the same way as with sql 2000 in the restored databases?
I am attempting to move some SQL 2000 databases to SQL 2005. My main production database does not seem to want to move. When I use the SQL 2005 GUI the .bak backup file is marked 'Incomplete'. When I attempt to restore the backup file I get a 'RESTORE detected an error on page (0:0) in database' message. I saw a thread in the SQL Express forum suggesting trying to restore from the T-SQL level to get the GUI out of the picture and I get the same 'error on page (0:0)' message. However when I take the same file and use SQL 2000 Enterprise Manager it restores with no problems.
Hello, I installed SQL 2005 Standard on the same server (2K3) with SQL 2000. My named instance I installed is coming up with "Version 8.00.2039" in the Server Management Studio and will not let me restore a database back-up I made on a 2005 development workstation (I'm assuming it's because it's trying to use the 2000 engine instead of the 2005). Is there a way I can force this instance to use the 2005 engine rather than the 2000?
I have about 4 SQL servers that have SQL2005 as the default instance and SQL2000 as a second instance. My problem is that I can not connect to the SQL2000 instances using the instance name. I can get to it using IP address and port number or if I set up an alias with IP and port number, but not by name (ie ServerNameSQL2000 which is how the instance was named). If the process is reversed (install SQL 2000 first and then SQL 2005) I can get to both instances using instance name.
I read something about if SQL2005 Browser service is running when SQL2000 service starts, the SQL2000 service won't listen for calls, but it was rather vague and I am not real sure if that is true. I am in the process of trying to test this to see if it is true, but due to the nature of the servers, I have to follow a process and it will take me a couple of days before I can test.
So I was hoping to find someone to deny or confirm this. Or who has had a similar issue and can shed some light on this for me. Thank you for you time. I appreciate it.
Hi, I am struggling connection to a named instance of SQL 2000 (SP4) from another machine but without any success. I get an error message saying that the server does not exist or access is denied.
The security configuration in this named instance is the same as the default instance (also 2000) and the remote machine can connect to it successfully.
I also configured the aliases in Client Network Utility in the client machine and set the server (machine) name and the port number used by the instance - but no help.
I use osql and Query Analyzer to connect to it, but I cannot connect by any of them.
Connecting locally, in the machine where the instance is installed, is successful.
The same behaviour appears when I try to connect to another instance on the machine which is 2005. Something with the named instance is problematic.
I need to move a large number of reports from a 2000 reporting services install to 2005. I've used the RS Scripter utility with some success. The issue I'm having is migrating history.
Can history be migrated without upgrading the reportserver and temp db to 2005? We'd like to preserve our 2000 environment while we move...although I suppose we could create another RS instance and copy the database, do the upgrade - but how would we merge our existing 2005 install with the upgraded 2000.
