Attaching, Restoreing, Backup DB in MSDE , How?

Hi all;

I created a DB in MS SQL Server 2000.. (has Tables, SPs, Views..etc.) and I want to attached to a customer that has ONLY MSDE?

How?

Also, how can my customer make Backup & Restore from his MSDE? (BTW: can I do that in code (VB.NET/ASP.NET)??

Thanks in advanced!UP :(

Plz, help me!!

Attaching without ldf file

I tried to attach mdf file without ldf file. However:
"Error 1813: Could not open new database 'GJIRB'. CREATE DATABASE is aborted
.
Device activation error. The physical file name 'C:\ ...\db_name.LDF' may be
incorrect."
Then:
"Attaching database has failed."
If one has not have ldf file is it possible to use mdf file?Hi
sp_attach_single_file_db may help! Make sure that the LDF does not exist
already and the location that is being used is correct.
John
"Alur" wrote:

> I tried to attach mdf file without ldf file. However:
> "Error 1813: Could not open new database 'GJIRB'. CREATE DATABASE is abort
ed.
> Device activation error. The physical file name 'C:\ ...\db_name.LDF' may
be
> incorrect."
> Then:
> "Attaching database has failed."
> If one has not have ldf file is it possible to use mdf file?|||After sp_attach_single_file_db
the message:
"Server: Msg 911, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not locate entry in
sysdatabses for database 'db_name'.
No entry fount with that name. Make sure that the name is entered correctly.
"
appeared.
"John Bell" wrote:
> Hi
> sp_attach_single_file_db may help! Make sure that the LDF does not exist
> already and the location that is being used is correct.
> John
>
> "Alur" wrote:
>|||You can use exec sp_attach_db and only specify the database name and teh MDB
file path - and leave the remaining parameters blank (i.e., do not specify a
path to the non existant .LDF file).
Your database will get attached and a NEW log file (.ldf) will be created.
-HTH
"Alur" <Alur@.discussions.microsoft.com> wrote in message
news:115A77E2-4DDF-4A4E-8582-7B11A77CF90D@.microsoft.com...
>I tried to attach mdf file without ldf file. However:
> "Error 1813: Could not open new database 'GJIRB'. CREATE DATABASE is
> aborted.
> Device activation error. The physical file name 'C:\ ...\db_name.LDF' may
> be
> incorrect."
> Then:
> "Attaching database has failed."
> If one has not have ldf file is it possible to use mdf file?|||Excuse me
After
sp_attach_single_file_db
@.dbname = 'db_name',
@.physname = 'c:\db_name_Data.MDF'
the message
"Server: Msg 1813, Level 16, State 2, Line 1
Could not open new database 'db_name'. CREATE DATABASE is aborted.
Device activation error. The physical file name 'C:\Program Files\Microsoft
SQL Server\MSSQL\Data\db_name_Log.LDF' may be incorrect."
appeared.
"John Bell" wrote:
> Hi
> sp_attach_single_file_db may help! Make sure that the LDF does not exist
> already and the location that is being used is correct.
> John
>
> "Alur" wrote:
>|||Thank you.
"Jeffrey Todd" wrote:

> You can use exec sp_attach_db and only specify the database name and teh M
DB
> file path - and leave the remaining parameters blank (i.e., do not specify
a
> path to the non existant .LDF file).
> Your database will get attached and a NEW log file (.ldf) will be created.
> -HTH
>
> "Alur" <Alur@.discussions.microsoft.com> wrote in message
> news:115A77E2-4DDF-4A4E-8582-7B11A77CF90D@.microsoft.com...
>
>|||I ran into this very same issue this w although I was trying to
attach the db via vbscript from an msi. Also got the same error when
trying to attach the db from Query Analyser.
Turned out that the mdf had been set to read only because someone had
not checked the shippable copy out of SourceSafe before building the
msi.
As soon as I set the file back to read\write... the problem dissappeared
instantly.
Seems that SQLDMO tries to update the mdf with the new file name and
instead of reporting an access error just continues and uses the ldf
location that is already in the mdf.
Maybe this will provide usefull for others.
Best wishes
Lee Cottrell
Chief Technical Officer
Paymentshield Limited
*** Sent via Developersdex http://www.examnotes.net ***|||Thank you.
"Lee Cottrell" wrote:

> I ran into this very same issue this w although I was trying to
> attach the db via vbscript from an msi. Also got the same error when
> trying to attach the db from Query Analyser.
> Turned out that the mdf had been set to read only because someone had
> not checked the shippable copy out of SourceSafe before building the
> msi.
> As soon as I set the file back to read\write... the problem dissappeared
> instantly.
> Seems that SQLDMO tries to update the mdf with the new file name and
> instead of reporting an access error just continues and uses the ldf
> location that is already in the mdf.
> Maybe this will provide usefull for others.
> Best wishes
> Lee Cottrell
> Chief Technical Officer
> Paymentshield Limited
> *** Sent via Developersdex http://www.examnotes.net ***
>|||And could you tell me is it possible to solve this in SQL Server versions,
which newer than 2000 ?
"Alur" wrote:
> Thank you.
> "Lee Cottrell" wrote:
>|||Hi
I don't think attaching a mdf file that has not been detached properly is
going to work in any version as your database will be in an inconsistent
state. But you may want to post to try posting to the beta news group
http://communities.microsoft.com/ne...lcid=us

to see if anyone has tried this.
John
"Alur" <Alur@.discussions.microsoft.com> wrote in message
news:B22347AC-D039-4842-9595-AF4CBF9D1E57@.microsoft.com...
> And could you tell me is it possible to solve this in SQL Server versions,
> which newer than 2000 ?
> "Alur" wrote:
>

attaching to msdb db

Hello there
On the business i;m working on, I've installed MSDE on my client computer.
So far i've worked with SQL sever 2000
now i transfered to sql server 2005.
and i tried to attach one of my files. It gave me Error because my DB i;m
trying to attach is bigger then 2GB (which is not possible according to
microsoft Licence)
now what can i do,
if i instead of detach and attach i do backup and restore it allow me to do
that?Roy
SQL Server 2005 Express Edition has 4GB limited .Or do you try to attach
SQL Server 2005 to MSDE database?
"Roy Goldhammer" <roy@.hotmail.com> wrote in message
news:umkvw3UGHHA.4116@.TK2MSFTNGP05.phx.gbl...
> Hello there
> On the business i;m working on, I've installed MSDE on my client computer.
> So far i've worked with SQL sever 2000
> now i transfered to sql server 2005.
> and i tried to attach one of my files. It gave me Error because my DB i;m
> trying to attach is bigger then 2GB (which is not possible according to
> microsoft Licence)
> now what can i do,
> if i instead of detach and attach i do backup and restore it allow me to
> do that?
>

attaching to msdb db

Hello there
On the business i;m working on, I've installed MSDE on my client computer.
So far i've worked with SQL sever 2000
now i transfered to sql server 2005.
and i tried to attach one of my files. It gave me Error because my DB i;m
trying to attach is bigger then 2GB (which is not possible according to
microsoft Licence)
now what can i do,
if i instead of detach and attach i do backup and restore it allow me to do
that?
Roy
SQL Server 2005 Express Edition has 4GB limited .Or do you try to attach
SQL Server 2005 to MSDE database?
"Roy Goldhammer" <roy@.hotmail.com> wrote in message
news:umkvw3UGHHA.4116@.TK2MSFTNGP05.phx.gbl...
> Hello there
> On the business i;m working on, I've installed MSDE on my client computer.
> So far i've worked with SQL sever 2000
> now i transfered to sql server 2005.
> and i tried to attach one of my files. It gave me Error because my DB i;m
> trying to attach is bigger then 2GB (which is not possible according to
> microsoft Licence)
> now what can i do,
> if i instead of detach and attach i do backup and restore it allow me to
> do that?
>
|||Maybe one of the following will help you:
1. If the db has a lot of free space, see if shrinking will reduce the size.
2. Move some tables into a new database, then shrink and attach both.
3. Delete and/or move some of your older data into a new database, then
shrink and attach both.

attaching to msdb db

Hello there
On the business i;m working on, I've installed MSDE on my client computer.
So far i've worked with SQL sever 2000
now i transfered to sql server 2005.
and i tried to attach one of my files. It gave me Error because my DB i;m
trying to attach is bigger then 2GB (which is not possible according to
microsoft Licence)
now what can i do,
if i instead of detach and attach i do backup and restore it allow me to do
that?Roy
SQL Server 2005 Express Edition has 4GB limited .Or do you try to attach
SQL Server 2005 to MSDE database?
"Roy Goldhammer" <roy@.hotmail.com> wrote in message
news:umkvw3UGHHA.4116@.TK2MSFTNGP05.phx.gbl...
> Hello there
> On the business i;m working on, I've installed MSDE on my client computer.
> So far i've worked with SQL sever 2000
> now i transfered to sql server 2005.
> and i tried to attach one of my files. It gave me Error because my DB i;m
> trying to attach is bigger then 2GB (which is not possible according to
> microsoft Licence)
> now what can i do,
> if i instead of detach and attach i do backup and restore it allow me to
> do that?
>|||Maybe one of the following will help you:
1. If the db has a lot of free space, see if shrinking will reduce the size.
2. Move some tables into a new database, then shrink and attach both.
3. Delete and/or move some of your older data into a new database, then
shrink and attach both.

Attaching the log file and the mdf files of the database.

When I try to attach both the log file and mdf files

I got the following error message.

TITLE: Microsoft SQL Server Management Studio

Attach database failed for Server 'FCIT-GFOX082'. (Microsoft.SqlServer.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Attach+database+Server&LinkId=20476

ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

The header for file 'C:\Documents and Settings\Administrator\My Documents\Microsoft Press\AS2005SBS\Setup\Query\log_attach_databases.txt' is not a valid database file header. The FILE SIZE property is incorrect. (Microsoft SQL Server, Error: 5172)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.0194&EvtSrc=MSSQLServer&EvtID=5172&LinkId=20476

BUTTONS:

OK

Could someone help me on how to go about this.

Regards,

Ronald

Maybe you need to take a step back and tell us what you were trying to accomplish. SSAS does not use mdf and log files. And the file in the error message you posted is a .txt file.

SSAS either uses a .abf format for back up and restore, or an xmla script to create an empty database.

|||

I am trying to attach the SSAS Step by Step database that comes with the book Microsoft SQL SERVER 2005 Analysis SErvices Step by Step.

When I try it out, I get error messages.

Regards,

Ronaldl

attaching system database

Hi,
I would like to ask if system database from other server can be
attached to other server. So basically, the process is, the existing
system database(including user databases) will be replaced by other
set of database(system and user databases) the new set of the
databases are just located in a separate drive in a cluster
environment. Will this procedure can apply?
http://support.microsoft.com/kb/224071
I am not sure if this will work. Just need to verify.
Thanks.
This will work. In some cases, you can simply copy the MDF/LDF files on the
same location where the system database files exist while the SQL Server
service is stopped. Once it starts, it should see those files. I used this
approach when I needed to set the collation settings for my tempdb. Instead
of rebuilding the master database, I just copied the model database files
from one server which has the same collation settings I need for my tempdb
and it worked
"Bry" <fqies_bry@.yahoo.com> wrote in message
news:1186108853.215054.30080@.j4g2000prf.googlegrou ps.com...
> Hi,
> I would like to ask if system database from other server can be
> attached to other server. So basically, the process is, the existing
> system database(including user databases) will be replaced by other
> set of database(system and user databases) the new set of the
> databases are just located in a separate drive in a cluster
> environment. Will this procedure can apply?
> http://support.microsoft.com/kb/224071
> I am not sure if this will work. Just need to verify.
> Thanks.
>
|||What if I have to use the other drive where they put the database
files? like I will modify the SQL(as KB said) to modify the drive of
the system database. will there be implications/problems?
|||I was about to say this...this is very important as your backups will not
work
"Jonathan Psaila-Depasquale" <nospam@.nospamplease.com> wrote in message
news:OLlqTka1HHA.3916@.TK2MSFTNGP02.phx.gbl...[vbcol=seagreen]
> Hi,
> Make sure that your destination SQL Server instance is patched up to the
> same build as the instance from which you are taking the system databases.
> Jonathan
>
> Bry wrote:

attaching system database

Hi,
I would like to ask if system database from other server can be
attached to other server. So basically, the process is, the existing
system database(including user databases) will be replaced by other
set of database(system and user databases) the new set of the
databases are just located in a separate drive in a cluster
environment. Will this procedure can apply?
http://support.microsoft.com/kb/224071
I am not sure if this will work. Just need to verify.
Thanks.This will work. In some cases, you can simply copy the MDF/LDF files on the
same location where the system database files exist while the SQL Server
service is stopped. Once it starts, it should see those files. I used this
approach when I needed to set the collation settings for my tempdb. Instead
of rebuilding the master database, I just copied the model database files
from one server which has the same collation settings I need for my tempdb
and it worked
"Bry" <fqies_bry@.yahoo.com> wrote in message
news:1186108853.215054.30080@.j4g2000prf.googlegroups.com...
> Hi,
> I would like to ask if system database from other server can be
> attached to other server. So basically, the process is, the existing
> system database(including user databases) will be replaced by other
> set of database(system and user databases) the new set of the
> databases are just located in a separate drive in a cluster
> environment. Will this procedure can apply?
> http://support.microsoft.com/kb/224071
> I am not sure if this will work. Just need to verify.
> Thanks.
>|||What if I have to use the other drive where they put the database
files? like I will modify the SQL(as KB said) to modify the drive of
the system database. will there be implications/problems?|||Hi,
Make sure that your destination SQL Server instance is patched up to the
same build as the instance from which you are taking the system databases.
Jonathan
Bry wrote:
> Hi,
> I would like to ask if system database from other server can be
> attached to other server. So basically, the process is, the existing
> system database(including user databases) will be replaced by other
> set of database(system and user databases) the new set of the
> databases are just located in a separate drive in a cluster
> environment. Will this procedure can apply?
> http://support.microsoft.com/kb/224071
> I am not sure if this will work. Just need to verify.
> Thanks.
>|||I was about to say this...this is very important as your backups will not
work
"Jonathan Psaila-Depasquale" <nospam@.nospamplease.com> wrote in message
news:OLlqTka1HHA.3916@.TK2MSFTNGP02.phx.gbl...[vbcol=seagreen]
> Hi,
> Make sure that your destination SQL Server instance is patched up to the
> same build as the instance from which you are taking the system databases.
> Jonathan
>
> Bry wrote:

attaching system database

Hi,
I would like to ask if system database from other server can be
attached to other server. So basically, the process is, the existing
system database(including user databases) will be replaced by other
set of database(system and user databases) the new set of the
databases are just located in a separate drive in a cluster
environment. Will this procedure can apply?
http://support.microsoft.com/kb/224071
I am not sure if this will work. Just need to verify.
Thanks.This will work. In some cases, you can simply copy the MDF/LDF files on the
same location where the system database files exist while the SQL Server
service is stopped. Once it starts, it should see those files. I used this
approach when I needed to set the collation settings for my tempdb. Instead
of rebuilding the master database, I just copied the model database files
from one server which has the same collation settings I need for my tempdb
and it worked
"Bry" <fqies_bry@.yahoo.com> wrote in message
news:1186108853.215054.30080@.j4g2000prf.googlegroups.com...
> Hi,
> I would like to ask if system database from other server can be
> attached to other server. So basically, the process is, the existing
> system database(including user databases) will be replaced by other
> set of database(system and user databases) the new set of the
> databases are just located in a separate drive in a cluster
> environment. Will this procedure can apply?
> http://support.microsoft.com/kb/224071
> I am not sure if this will work. Just need to verify.
> Thanks.
>|||What if I have to use the other drive where they put the database
files? like I will modify the SQL(as KB said) to modify the drive of
the system database. will there be implications/problems?|||Hi,
Make sure that your destination SQL Server instance is patched up to the
same build as the instance from which you are taking the system databases.
Jonathan
Bry wrote:
> Hi,
> I would like to ask if system database from other server can be
> attached to other server. So basically, the process is, the existing
> system database(including user databases) will be replaced by other
> set of database(system and user databases) the new set of the
> databases are just located in a separate drive in a cluster
> environment. Will this procedure can apply?
> http://support.microsoft.com/kb/224071
> I am not sure if this will work. Just need to verify.
> Thanks.
>|||I was about to say this...this is very important as your backups will not
work
"Jonathan Psaila-Depasquale" <nospam@.nospamplease.com> wrote in message
news:OLlqTka1HHA.3916@.TK2MSFTNGP02.phx.gbl...
> Hi,
> Make sure that your destination SQL Server instance is patched up to the
> same build as the instance from which you are taking the system databases.
> Jonathan
>
> Bry wrote:
>> Hi,
>> I would like to ask if system database from other server can be
>> attached to other server. So basically, the process is, the existing
>> system database(including user databases) will be replaced by other
>> set of database(system and user databases) the new set of the
>> databases are just located in a separate drive in a cluster
>> environment. Will this procedure can apply?
>> http://support.microsoft.com/kb/224071
>> I am not sure if this will work. Just need to verify.
>> Thanks.

attaching subscription database woes

I'm trying to get to a point where I can implement structural changes to a
merge replication system. My plan is to ship copies of a subscription
database to enduser outside the corp firewall and write some code to load
the new subscription database. I've done the following:
1. create a subscription db on the same server as the publisher
2. use the 'copy a subscription database' menu choice to create a copy of
it.
3. move the copy to target server.
4. in the replication folder on the target server select: 'attach
subscription database', select the msf file, specify a name for the db.
5. run sp_addMergeSubscription on the publication server as follows:
exec sp_addmergesubscription
@.publication = 'rep_test_hub',
@.subscriber = 'k-server',
@.subscriber_db = 'rep_test_sub2',
@.subscription_type = 'pull',
@.sync_type = 'none'
6. on the publisher - drill down to the publisher list, refresh it and note
the addition of 'rep_test_sub2'. At this point the status is 'deactivated'
7. synch with the publisher on subscriber
The above works fine when both pub and sub are on the same box. When I try
this on another pc in a peer-peer network I get the following error:
Event Type: Information
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 203
Date: 1/20/2006
Time: 1:20:32 PM
User: N/A
Computer: k-HOME
Description:
SubSystem Message - Job
'K-SERVER-rep_test_hub-rep_test_hub-K-HOME-rep_test_sub6- 0'
(0x826C45BA92AD5F4E9B37842A22DB6F0B), step 1 - The process could not connect
to Distributor 'K-SERVER'. Login failed for user 'NT AUTHORITY\ANONYMOUS
LOGON'.
Why is the synch attempt using an 'anonymous logon'?
I've checked my SQL-Agent properties and it is setup for 'SQL-Server
Authentication' in the connection tab on both systems. Both server have
identical 'sa' passwords. The startup account is 'system account' on the
sub PC and a domain admin account on the hub PC. The sub PC is not part of
the domain.
Any suggestions?
Thanks.
Run SQL Server agent under a local admin account on the subscriber.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"astro" <astro@.bcmn.com> wrote in message
news:U2bAf.38900$7S.35782@.tornado.rdc-kc.rr.com...
> I'm trying to get to a point where I can implement structural changes to a
> merge replication system. My plan is to ship copies of a subscription
> database to enduser outside the corp firewall and write some code to load
> the new subscription database. I've done the following:
> 1. create a subscription db on the same server as the publisher
> 2. use the 'copy a subscription database' menu choice to create a copy of
> it.
> 3. move the copy to target server.
> 4. in the replication folder on the target server select: 'attach
> subscription database', select the msf file, specify a name for the db.
> 5. run sp_addMergeSubscription on the publication server as follows:
> exec sp_addmergesubscription
> @.publication = 'rep_test_hub',
> @.subscriber = 'k-server',
> @.subscriber_db = 'rep_test_sub2',
> @.subscription_type = 'pull',
> @.sync_type = 'none'
> 6. on the publisher - drill down to the publisher list, refresh it and
> note the addition of 'rep_test_sub2'. At this point the status is
> 'deactivated'
> 7. synch with the publisher on subscriber
> The above works fine when both pub and sub are on the same box. When I
> try this on another pc in a peer-peer network I get the following error:
> Event Type: Information
> Event Source: SQLSERVERAGENT
> Event Category: Job Engine
> Event ID: 203
> Date: 1/20/2006
> Time: 1:20:32 PM
> User: N/A
> Computer: k-HOME
> Description:
> SubSystem Message - Job
> 'K-SERVER-rep_test_hub-rep_test_hub-K-HOME-rep_test_sub6- 0'
> (0x826C45BA92AD5F4E9B37842A22DB6F0B), step 1 - The process could not
> connect to Distributor 'K-SERVER'. Login failed for user 'NT
> AUTHORITY\ANONYMOUS LOGON'.
> Why is the synch attempt using an 'anonymous logon'?
> I've checked my SQL-Agent properties and it is setup for 'SQL-Server
> Authentication' in the connection tab on both systems. Both server have
> identical 'sa' passwords. The startup account is 'system account' on the
> sub PC and a domain admin account on the hub PC. The sub PC is not part
> of the domain.
>
> Any suggestions?
> Thanks.
>
>

attaching SQL Server 2000 database to SQL Server 2005 Express

If someone can help. I just installed SQL Server 2005 Express. I am trying to attach a SQL Server 2000 database so I can work on it. I am getting the following error.

Msg 5118, Level 16, State 1, Line 1

The file "L:\SQL Data\Data\Dougins_Data.mdf" is compressed but does not reside in a read-only database or filegroup. The file must be decompressed.

Msg 1813, Level 16, State 2, Line 1

Could not open new database 'Dougins'. CREATE DATABASE is aborted.

I cannot find instructions in help to decompress the file. Does anyone have any suggestions?

I dont think so there is file compression is related to database. Check with your windows folks since file compression are done at the OS level. Ask them to decompress the files and you should be good to go.

Attaching SQL Server 2000 database on SQL Serve 2005

Hello!
We are planning to migrate our multi terabyte SQL Server 2000 database
by detaching data/log files on 2000 box and reattaching them on 2005. Has
anyone experienced any issues with this process in general and databases of
such size in particular? As far as I know, SQL Server will perform database
conversion when attaching database on SQL 2005.
Any thoughts are greatly appreciated,
IgorThis is a simple test,with a database names 'test' which on sqlserver 2000.
first:
Stop the database's servers(2000) on machine.
second:
Execute the command on 2005 server:
exec sp_attach_db @.dbname = N'test',
@.filename1 = N'd:\sqlserver database\MSSQL\data\test_Data.MDF',
@.filename2 = N'd:\sqlserver database\MSSQL\data\test_Log.LDF'
ok.So easy.And the server will return a message:'Converting database 'test'
from version 539 to the current version 607.'
"imarchenko" wrote:

> Hello!
> We are planning to migrate our multi terabyte SQL Server 2000 database
> by detaching data/log files on 2000 box and reattaching them on 2005. Has
> anyone experienced any issues with this process in general and databases o
f
> such size in particular? As far as I know, SQL Server will perform databas
e
> conversion when attaching database on SQL 2005.
>
> Any thoughts are greatly appreciated,
> Igor
>
>|||you should copy the datafile to a specifically catalog 。And use new files
to
attach.Otherwise 2000 server's 'test' database will disappear
"luyan" wrote:
[vbcol=seagreen]
> This is a simple test,with a database names 'test' which on sqlserver 2000
.
> first:
> Stop the database's servers(2000) on machine.
> second:
> Execute the command on 2005 server:
> exec sp_attach_db @.dbname = N'test',
> @.filename1 = N'd:\sqlserver database\MSSQL\data\test_Data.MDF',
> @.filename2 = N'd:\sqlserver database\MSSQL\data\test_Log.LDF'
> ok.So easy.And the server will return a message:'Converting database 'test
'
> from version 539 to the current version 607.'
> "imarchenko" wrote:
>|||luyan,
Thanks for you reply. I do know how to detach/attach database. My
question is whether anyone has experienced any problems while attaching
terabyte databases.
Thanks,
Igor
"luyan" <luyan@.discussions.microsoft.com> wrote in message
news:051EBA51-A12E-4E42-A07B-94B5D588DA72@.microsoft.com...[vbcol=seagreen]
> you should copy the datafile to a specifically catalog ?And use new files
> to
> attach.Otherwise 2000 server's 'test' database will disappear
> "luyan" wrote:
>|||It may take a long time. I did restore a 500 MB SQL 2000 DB to SQL 2005 and
it took about 10 minutes on SAN system. In your situation you have to
consider this issue.
Bill
"imarchenko" wrote:

> Hello!
> We are planning to migrate our multi terabyte SQL Server 2000 database
> by detaching data/log files on 2000 box and reattaching them on 2005. Has
> anyone experienced any issues with this process in general and databases o
f
> such size in particular? As far as I know, SQL Server will perform databas
e
> conversion when attaching database on SQL 2005.
>
> Any thoughts are greatly appreciated,
> Igor
>
>|||Bill,
Thanks for you feedback.
Igor
"Bill Wang" <BillWang@.discussions.microsoft.com> wrote in message
news:D23E2D1B-DAA2-4FA2-A5CA-E253DC148BED@.microsoft.com...[vbcol=seagreen]
> It may take a long time. I did restore a 500 MB SQL 2000 DB to SQL 2005
> and
> it took about 10 minutes on SAN system. In your situation you have to
> consider this issue.
> Bill
> "imarchenko" wrote:
>

Attaching SQL Server 2000 database on SQL Serve 2005

Hello!
We are planning to migrate our multi terabyte SQL Server 2000 database
by detaching data/log files on 2000 box and reattaching them on 2005. Has
anyone experienced any issues with this process in general and databases of
such size in particular? As far as I know, SQL Server will perform database
conversion when attaching database on SQL 2005.
Any thoughts are greatly appreciated,
IgorThis is a simple test,with a database names 'test' which on sqlserver 2000.
first:
Stop the database's servers(2000) on machine.
second:
Execute the command on 2005 server:
exec sp_attach_db @.dbname = N'test',
@.filename1 = N'd:\sqlserver database\MSSQL\data\test_Data.MDF',
@.filename2 = N'd:\sqlserver database\MSSQL\data\test_Log.LDF'
ok.So easy.And the server will return a message:'Converting database 'test'
from version 539 to the current version 607.'
"imarchenko" wrote:
> Hello!
> We are planning to migrate our multi terabyte SQL Server 2000 database
> by detaching data/log files on 2000 box and reattaching them on 2005. Has
> anyone experienced any issues with this process in general and databases of
> such size in particular? As far as I know, SQL Server will perform database
> conversion when attaching database on SQL 2005.
>
> Any thoughts are greatly appreciated,
> Igor
>
>|||you should copy the datafile to a specifically catalog ã'And use new files to
attach.Otherwise 2000 server's 'test' database will disappear
"luyan" wrote:
> This is a simple test,with a database names 'test' which on sqlserver 2000.
> first:
> Stop the database's servers(2000) on machine.
> second:
> Execute the command on 2005 server:
> exec sp_attach_db @.dbname = N'test',
> @.filename1 = N'd:\sqlserver database\MSSQL\data\test_Data.MDF',
> @.filename2 = N'd:\sqlserver database\MSSQL\data\test_Log.LDF'
> ok.So easy.And the server will return a message:'Converting database 'test'
> from version 539 to the current version 607.'
> "imarchenko" wrote:
> > Hello!
> >
> > We are planning to migrate our multi terabyte SQL Server 2000 database
> > by detaching data/log files on 2000 box and reattaching them on 2005. Has
> > anyone experienced any issues with this process in general and databases of
> > such size in particular? As far as I know, SQL Server will perform database
> > conversion when attaching database on SQL 2005.
> >
> >
> > Any thoughts are greatly appreciated,
> > Igor
> >
> >
> >|||luyan,
Thanks for you reply. I do know how to detach/attach database. My
question is whether anyone has experienced any problems while attaching
terabyte databases.
Thanks,
Igor
"luyan" <luyan@.discussions.microsoft.com> wrote in message
news:051EBA51-A12E-4E42-A07B-94B5D588DA72@.microsoft.com...
> you should copy the datafile to a specifically catalog ?And use new files
> to
> attach.Otherwise 2000 server's 'test' database will disappear
> "luyan" wrote:
>> This is a simple test,with a database names 'test' which on sqlserver
>> 2000.
>> first:
>> Stop the database's servers(2000) on machine.
>> second:
>> Execute the command on 2005 server:
>> exec sp_attach_db @.dbname = N'test',
>> @.filename1 = N'd:\sqlserver database\MSSQL\data\test_Data.MDF',
>> @.filename2 = N'd:\sqlserver database\MSSQL\data\test_Log.LDF'
>> ok.So easy.And the server will return a message:'Converting database
>> 'test'
>> from version 539 to the current version 607.'
>> "imarchenko" wrote:
>> > Hello!
>> >
>> > We are planning to migrate our multi terabyte SQL Server 2000
>> > database
>> > by detaching data/log files on 2000 box and reattaching them on 2005.
>> > Has
>> > anyone experienced any issues with this process in general and
>> > databases of
>> > such size in particular? As far as I know, SQL Server will perform
>> > database
>> > conversion when attaching database on SQL 2005.
>> >
>> >
>> > Any thoughts are greatly appreciated,
>> > Igor
>> >
>> >
>> >|||It may take a long time. I did restore a 500 MB SQL 2000 DB to SQL 2005 and
it took about 10 minutes on SAN system. In your situation you have to
consider this issue.
Bill
"imarchenko" wrote:
> Hello!
> We are planning to migrate our multi terabyte SQL Server 2000 database
> by detaching data/log files on 2000 box and reattaching them on 2005. Has
> anyone experienced any issues with this process in general and databases of
> such size in particular? As far as I know, SQL Server will perform database
> conversion when attaching database on SQL 2005.
>
> Any thoughts are greatly appreciated,
> Igor
>
>|||Bill,
Thanks for you feedback.
Igor
"Bill Wang" <BillWang@.discussions.microsoft.com> wrote in message
news:D23E2D1B-DAA2-4FA2-A5CA-E253DC148BED@.microsoft.com...
> It may take a long time. I did restore a 500 MB SQL 2000 DB to SQL 2005
> and
> it took about 10 minutes on SAN system. In your situation you have to
> consider this issue.
> Bill
> "imarchenko" wrote:
>> Hello!
>> We are planning to migrate our multi terabyte SQL Server 2000
>> database
>> by detaching data/log files on 2000 box and reattaching them on 2005. Has
>> anyone experienced any issues with this process in general and databases
>> of
>> such size in particular? As far as I know, SQL Server will perform
>> database
>> conversion when attaching database on SQL 2005.
>>
>> Any thoughts are greatly appreciated,
>> Igor
>>

Attaching SQL Server 2000 database on SQL Serve 2005

Hello!
We are planning to migrate our multi terabyte SQL Server 2000 database
by detaching data/log files on 2000 box and reattaching them on 2005. Has
anyone experienced any issues with this process in general and databases of
such size in particular? As far as I know, SQL Server will perform database
conversion when attaching database on SQL 2005.
Any thoughts are greatly appreciated,
Igor
This is a simple test,with a database names 'test' which on sqlserver 2000.
first:
Stop the database's servers(2000) on machine.
second:
Execute the command on 2005 server:
exec sp_attach_db @.dbname = N'test',
@.filename1 = N'd:\sqlserver database\MSSQL\data\test_Data.MDF',
@.filename2 = N'd:\sqlserver database\MSSQL\data\test_Log.LDF'
ok.So easy.And the server will return a message:'Converting database 'test'
from version 539 to the current version 607.'
"imarchenko" wrote:

> Hello!
> We are planning to migrate our multi terabyte SQL Server 2000 database
> by detaching data/log files on 2000 box and reattaching them on 2005. Has
> anyone experienced any issues with this process in general and databases of
> such size in particular? As far as I know, SQL Server will perform database
> conversion when attaching database on SQL 2005.
>
> Any thoughts are greatly appreciated,
> Igor
>
>
|||you should copy the datafile to a specifically catalog 。And use new files to
attach.Otherwise 2000 server's 'test' database will disappear
"luyan" wrote:
[vbcol=seagreen]
> This is a simple test,with a database names 'test' which on sqlserver 2000.
> first:
> Stop the database's servers(2000) on machine.
> second:
> Execute the command on 2005 server:
> exec sp_attach_db @.dbname = N'test',
> @.filename1 = N'd:\sqlserver database\MSSQL\data\test_Data.MDF',
> @.filename2 = N'd:\sqlserver database\MSSQL\data\test_Log.LDF'
> ok.So easy.And the server will return a message:'Converting database 'test'
> from version 539 to the current version 607.'
> "imarchenko" wrote:
|||luyan,
Thanks for you reply. I do know how to detach/attach database. My
question is whether anyone has experienced any problems while attaching
terabyte databases.
Thanks,
Igor
"luyan" <luyan@.discussions.microsoft.com> wrote in message
news:051EBA51-A12E-4E42-A07B-94B5D588DA72@.microsoft.com...[vbcol=seagreen]
> you should copy the datafile to a specifically catalog ?And use new files
> to
> attach.Otherwise 2000 server's 'test' database will disappear
> "luyan" wrote:
|||It may take a long time. I did restore a 500 MB SQL 2000 DB to SQL 2005 and
it took about 10 minutes on SAN system. In your situation you have to
consider this issue.
Bill
"imarchenko" wrote:

> Hello!
> We are planning to migrate our multi terabyte SQL Server 2000 database
> by detaching data/log files on 2000 box and reattaching them on 2005. Has
> anyone experienced any issues with this process in general and databases of
> such size in particular? As far as I know, SQL Server will perform database
> conversion when attaching database on SQL 2005.
>
> Any thoughts are greatly appreciated,
> Igor
>
>
|||Bill,
Thanks for you feedback.
Igor
"Bill Wang" <BillWang@.discussions.microsoft.com> wrote in message
news:D23E2D1B-DAA2-4FA2-A5CA-E253DC148BED@.microsoft.com...[vbcol=seagreen]
> It may take a long time. I did restore a 500 MB SQL 2000 DB to SQL 2005
> and
> it took about 10 minutes on SAN system. In your situation you have to
> consider this issue.
> Bill
> "imarchenko" wrote:

Attaching SQL Database in 2005 from CD-ROM

Hi:
I am trying to attach a database on a CD-ROM using the following command
exec sp_attach_db dbname='dbname',
filename1='d:\dbname.mdf',
filename2='d:\dbname.ldf'
and I am getting the following error
Msg 3415, Level 16, State 1, Line 1
Database 'dbname' cannot be upgraded because it is read-only or has
read-only files. Make the database or files writeable, and rerun recovery.
Any Help would be appreciated.
TIA
-srini
Its working on SQL 2000 Server. I am wondering is there a work-around for
SQL 2005.
-srini
"srini" wrote:

> Hi:
> I am trying to attach a database on a CD-ROM using the following command
> exec sp_attach_db dbname='dbname',
> filename1='d:\dbname.mdf',
> filename2='d:\dbname.ldf'
> and I am getting the following error
> Msg 3415, Level 16, State 1, Line 1
> Database 'dbname' cannot be upgraded because it is read-only or has
> read-only files. Make the database or files writeable, and rerun recovery.
>
> Any Help would be appreciated.
> TIA
> -srini
|||SQL needs upgradte the db and the cdrom is read only,upgrade from hard disk
and then save to cdrom
"srini" <srini@.discussions.microsoft.com> escribi en el mensaje
news:A8B27EC6-2370-4596-8FF2-E505147BB62D@.microsoft.com...
> Hi:
> I am trying to attach a database on a CD-ROM using the following command
> exec sp_attach_db dbname='dbname',
> filename1='d:\dbname.mdf',
> filename2='d:\dbname.ldf'
> and I am getting the following error
> Msg 3415, Level 16, State 1, Line 1
> Database 'dbname' cannot be upgraded because it is read-only or has
> read-only files. Make the database or files writeable, and rerun recovery.
>
> Any Help would be appreciated.
> TIA
> -srini
|||Look at this page from BOL:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/fd717bec-b389-4b1e-936c-a4ccf75dba77.htm
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"srini" <srini@.discussions.microsoft.com> wrote in message
news:A8B27EC6-2370-4596-8FF2-E505147BB62D@.microsoft.com...
> Hi:
> I am trying to attach a database on a CD-ROM using the following command
> exec sp_attach_db dbname='dbname',
> filename1='d:\dbname.mdf',
> filename2='d:\dbname.ldf'
> and I am getting the following error
> Msg 3415, Level 16, State 1, Line 1
> Database 'dbname' cannot be upgraded because it is read-only or has
> read-only files. Make the database or files writeable, and rerun recovery.
>
> Any Help would be appreciated.
> TIA
> -srini
|||Thanks Geoff for a quick reply.
I read and tried the same it works. Thanks a lot.
Just in case if some one, needs step by step guidelines
Step1:
EXEC sp_create_removable 'exportdb',
'exportdbsys',
'C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\exportdbsys.mdf', 2,
'exportdblog',
'C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\exportdblog.ldf', 2,
'exportdbdata',
'C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\exportdbdata.ndf', 2
Step2:
Exported all objects that I wanted into this db through context menu optoin
"Export "
Step3:
sp_certify_removable exportdb
Step4:
Took the db offline.
Step5:
Copied the files on CD-ROM
Step6:
Deleted exportdb
Step7:
Attached the exportdb as exportdb1 as follows
sp_attach_db @.dbname = 'exportdb1',
@.filename1 = 'd:\exportdbsys.mdf',
@.filename2 = 'd:\exportdbdata.ndf',
@.filename3 = 'd:\exportdblog.ldf'
step8:
Verified the db works with simple select statement.
-srini
"Geoff N. Hiten" wrote:

> Look at this page from BOL:
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/fd717bec-b389-4b1e-936c-a4ccf75dba77.htm
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "srini" <srini@.discussions.microsoft.com> wrote in message
> news:A8B27EC6-2370-4596-8FF2-E505147BB62D@.microsoft.com...
>
|||Thanks Luis Tarzia.
My requirement is to use the database on CD-ROM as read-only database and I
want to be able to attach the db to any SQL 2005 and start using the same.
-srini
"Luis Tarzia" wrote:

> SQL needs upgradte the db and the cdrom is read only,upgrade from hard disk
> and then save to cdrom
> "srini" <srini@.discussions.microsoft.com> escribió en el mensaje
> news:A8B27EC6-2370-4596-8FF2-E505147BB62D@.microsoft.com...
>
>

Attaching SQL Database in 2005 from CD-ROM

Hi:
I am trying to attach a database on a CD-ROM using the following command
exec sp_attach_db dbname='dbname',
filename1='d:\dbname.mdf',
filename2='d:\dbname.ldf'
and I am getting the following error
Msg 3415, Level 16, State 1, Line 1
Database 'dbname' cannot be upgraded because it is read-only or has
read-only files. Make the database or files writeable, and rerun recovery.
Any Help would be appreciated.
TIA
-sriniIts working on SQL 2000 Server. I am wondering is there a work-around for
SQL 2005.
-srini
"srini" wrote:
> Hi:
> I am trying to attach a database on a CD-ROM using the following command
> exec sp_attach_db dbname='dbname',
> filename1='d:\dbname.mdf',
> filename2='d:\dbname.ldf'
> and I am getting the following error
> Msg 3415, Level 16, State 1, Line 1
> Database 'dbname' cannot be upgraded because it is read-only or has
> read-only files. Make the database or files writeable, and rerun recovery.
>
> Any Help would be appreciated.
> TIA
> -srini|||SQL needs upgradte the db and the cdrom is read only,upgrade from hard disk
and then save to cdrom
"srini" <srini@.discussions.microsoft.com> escribió en el mensaje
news:A8B27EC6-2370-4596-8FF2-E505147BB62D@.microsoft.com...
> Hi:
> I am trying to attach a database on a CD-ROM using the following command
> exec sp_attach_db dbname='dbname',
> filename1='d:\dbname.mdf',
> filename2='d:\dbname.ldf'
> and I am getting the following error
> Msg 3415, Level 16, State 1, Line 1
> Database 'dbname' cannot be upgraded because it is read-only or has
> read-only files. Make the database or files writeable, and rerun recovery.
>
> Any Help would be appreciated.
> TIA
> -srini|||Look at this page from BOL:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/fd717bec-b389-4b1e-936c-a4ccf75dba77.htm
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"srini" <srini@.discussions.microsoft.com> wrote in message
news:A8B27EC6-2370-4596-8FF2-E505147BB62D@.microsoft.com...
> Hi:
> I am trying to attach a database on a CD-ROM using the following command
> exec sp_attach_db dbname='dbname',
> filename1='d:\dbname.mdf',
> filename2='d:\dbname.ldf'
> and I am getting the following error
> Msg 3415, Level 16, State 1, Line 1
> Database 'dbname' cannot be upgraded because it is read-only or has
> read-only files. Make the database or files writeable, and rerun recovery.
>
> Any Help would be appreciated.
> TIA
> -srini|||Thanks Geoff for a quick reply.
I read and tried the same it works. Thanks a lot.
Just in case if some one, needs step by step guidelines
Step1:
EXEC sp_create_removable 'exportdb',
'exportdbsys',
'C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\exportdbsys.mdf', 2,
'exportdblog',
'C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\exportdblog.ldf', 2,
'exportdbdata',
'C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\exportdbdata.ndf', 2
Step2:
Exported all objects that I wanted into this db through context menu optoin
"Export "
Step3:
sp_certify_removable exportdb
Step4:
Took the db offline.
Step5:
Copied the files on CD-ROM
Step6:
Deleted exportdb
Step7:
Attached the exportdb as exportdb1 as follows
sp_attach_db @.dbname = 'exportdb1',
@.filename1 = 'd:\exportdbsys.mdf',
@.filename2 = 'd:\exportdbdata.ndf',
@.filename3 = 'd:\exportdblog.ldf'
step8:
Verified the db works with simple select statement.
-srini
"Geoff N. Hiten" wrote:
> Look at this page from BOL:
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/fd717bec-b389-4b1e-936c-a4ccf75dba77.htm
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "srini" <srini@.discussions.microsoft.com> wrote in message
> news:A8B27EC6-2370-4596-8FF2-E505147BB62D@.microsoft.com...
> > Hi:
> >
> > I am trying to attach a database on a CD-ROM using the following command
> >
> > exec sp_attach_db dbname='dbname',
> > filename1='d:\dbname.mdf',
> > filename2='d:\dbname.ldf'
> >
> > and I am getting the following error
> >
> > Msg 3415, Level 16, State 1, Line 1
> > Database 'dbname' cannot be upgraded because it is read-only or has
> > read-only files. Make the database or files writeable, and rerun recovery.
> >
> >
> > Any Help would be appreciated.
> >
> > TIA
> > -srini
>|||Thanks Luis Tarzia.
My requirement is to use the database on CD-ROM as read-only database and I
want to be able to attach the db to any SQL 2005 and start using the same.
-srini
"Luis Tarzia" wrote:
> SQL needs upgradte the db and the cdrom is read only,upgrade from hard disk
> and then save to cdrom
> "srini" <srini@.discussions.microsoft.com> escribió en el mensaje
> news:A8B27EC6-2370-4596-8FF2-E505147BB62D@.microsoft.com...
> > Hi:
> >
> > I am trying to attach a database on a CD-ROM using the following command
> >
> > exec sp_attach_db dbname='dbname',
> > filename1='d:\dbname.mdf',
> > filename2='d:\dbname.ldf'
> >
> > and I am getting the following error
> >
> > Msg 3415, Level 16, State 1, Line 1
> > Database 'dbname' cannot be upgraded because it is read-only or has
> > read-only files. Make the database or files writeable, and rerun recovery.
> >
> >
> > Any Help would be appreciated.
> >
> > TIA
> > -srini
>
>

Attaching SQL Database in 2005 from CD-ROM

Hi:
I am trying to attach a database on a CD-ROM using the following command
exec sp_attach_db dbname='dbname',
filename1='d:\dbname.mdf',
filename2='d:\dbname.ldf'
and I am getting the following error
Msg 3415, Level 16, State 1, Line 1
Database 'dbname' cannot be upgraded because it is read-only or has
read-only files. Make the database or files writeable, and rerun recovery.
Any Help would be appreciated.
TIA
-sriniIts working on SQL 2000 Server. I am wondering is there a work-around for
SQL 2005.
-srini
"srini" wrote:

> Hi:
> I am trying to attach a database on a CD-ROM using the following command
> exec sp_attach_db dbname='dbname',
> filename1='d:\dbname.mdf',
> filename2='d:\dbname.ldf'
> and I am getting the following error
> Msg 3415, Level 16, State 1, Line 1
> Database 'dbname' cannot be upgraded because it is read-only or has
> read-only files. Make the database or files writeable, and rerun recovery.
>
> Any Help would be appreciated.
> TIA
> -srini|||SQL needs upgradte the db and the cdrom is read only,upgrade from hard disk
and then save to cdrom
"srini" <srini@.discussions.microsoft.com> escribi en el mensaje
news:A8B27EC6-2370-4596-8FF2-E505147BB62D@.microsoft.com...
> Hi:
> I am trying to attach a database on a CD-ROM using the following command
> exec sp_attach_db dbname='dbname',
> filename1='d:\dbname.mdf',
> filename2='d:\dbname.ldf'
> and I am getting the following error
> Msg 3415, Level 16, State 1, Line 1
> Database 'dbname' cannot be upgraded because it is read-only or has
> read-only files. Make the database or files writeable, and rerun recovery.
>
> Any Help would be appreciated.
> TIA
> -srini|||Look at this page from BOL:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/fd717bec-b389-4b1e-936c-a4cc
f75dba77.htm
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"srini" <srini@.discussions.microsoft.com> wrote in message
news:A8B27EC6-2370-4596-8FF2-E505147BB62D@.microsoft.com...
> Hi:
> I am trying to attach a database on a CD-ROM using the following command
> exec sp_attach_db dbname='dbname',
> filename1='d:\dbname.mdf',
> filename2='d:\dbname.ldf'
> and I am getting the following error
> Msg 3415, Level 16, State 1, Line 1
> Database 'dbname' cannot be upgraded because it is read-only or has
> read-only files. Make the database or files writeable, and rerun recovery.
>
> Any Help would be appreciated.
> TIA
> -srini|||Thanks Geoff for a quick reply.
I read and tried the same it works. Thanks a lot.
Just in case if some one, needs step by step guidelines
Step1:
EXEC sp_create_removable 'exportdb',
'exportdbsys',
'C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\exportdbsys.mdf', 2,
'exportdblog',
'C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\exportdblog.ldf', 2,
'exportdbdata',
'C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\exportdbdata.ndf', 2
Step2:
Exported all objects that I wanted into this db through context menu optoin
"Export "
Step3:
sp_certify_removable exportdb
Step4:
Took the db offline.
Step5:
Copied the files on CD-ROM
Step6:
Deleted exportdb
Step7:
Attached the exportdb as exportdb1 as follows
sp_attach_db @.dbname = 'exportdb1',
@.filename1 = 'd:\exportdbsys.mdf',
@.filename2 = 'd:\exportdbdata.ndf',
@.filename3 = 'd:\exportdblog.ldf'
step8:
Verified the db works with simple select statement.
-srini
"Geoff N. Hiten" wrote:

> Look at this page from BOL:
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/fd717bec-b389-4b1e-936c-a4
ccf75dba77.htm
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "srini" <srini@.discussions.microsoft.com> wrote in message
> news:A8B27EC6-2370-4596-8FF2-E505147BB62D@.microsoft.com...
>|||Thanks Luis Tarzia.
My requirement is to use the database on CD-ROM as read-only database and I
want to be able to attach the db to any SQL 2005 and start using the same.
-srini
"Luis Tarzia" wrote:

> SQL needs upgradte the db and the cdrom is read only,upgrade from hard dis
k
> and then save to cdrom
> "srini" <srini@.discussions.microsoft.com> escribió en el mensaje
> news:A8B27EC6-2370-4596-8FF2-E505147BB62D@.microsoft.com...
>
>

Attaching SQL 2005 db to a SQL 2000 Server

Is this possible to attach a database from a SQL 2005 server to a Server runnning SQL 2000?
I have searched but came up empty.I highly doubt it.|||It can happen other way.|||Why do you need to do that?

You can install SQL2K5 Express and attach your SQL2K5 db there. Anything specific forces you to attach it to SQL2K?

attaching sql 2000 db with enterprse manager

When I upgrade from a sql 7 db to a sql 2000 db, everything goes well. I can also detach the 2000 db with sql 2000 enterprise manager. But when I want to attach the db again to an other sql 2000 server my loginnames disappear when i look at my users. This is because there are not yet any loginnames under the other sql 2000 server. What can I do to get my loginnames also under my usernames at the database to be attached. Else I cannot login in. Tell Me, please!

thanks beforehand.

\greetings ThePercivalYou can use the Transfer Logins DTS function that comes with SQL2K, but that will only transfer the logins and not their associated permissions.

You also have to BCP the syslogins table and then use sp_resolve_logins to restore the associated permissions. See SQL BOL on sp_resolve_logins

Regards,

Hugh Scott

Originally posted by thepercival
When I upgrade from a sql 7 db to a sql 2000 db, everything goes well. I can also detach the 2000 db with sql 2000 enterprise manager. But when I want to attach the db again to an other sql 2000 server my loginnames disappear when i look at my users. This is because there are not yet any loginnames under the other sql 2000 server. What can I do to get my loginnames also under my usernames at the database to be attached. Else I cannot login in. Tell Me, please!

thanks beforehand.

\greetings ThePercival

Attaching SQL 2000 DB in SQL 2005 and vice versa from CD-ROM

Hi all:
I am trying to attach db created in SQL 2000, detached and written on CD-ROM
in SQL 2005 and vice versa.
If I try to attach on the same SQL Server where it was created, it works fine.
I am using SQL 2000 generated db files as template to create databases
through API, both on SQL 2000 & on SQL 2005 machine.
1. When the database created on SQL 2005 attached in SQL 2000, I get the
following error.
Server: Msg 602, Level 21, State 50, Line 1
Could not find row in sysindexes for database ID 13, object ID 1, index ID
1. Run DBCC CHECKTABLE on sysindexes.
2. When the database created on SQL 2000 is attached in SQL 2005, I get the
following error.
Msg 3415, Level 16, State 1, Line 1
Database 'DB1' cannot be upgraded because it is read-only or has read-only
files. Make the database or files writeable, and rerun recovery.
Is there a workaround for this issue.
Any help would be appreciated.
TIA
-srini
You can't attach a 2005 db to 2000, regardless of read-only media or not.
As for attaching 2000 database to 2005, it is doable, but SQL Server has to be able to upgrade the
file structure. this means that for attach to work, the media cannot be read-only.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"srini" <srini@.discussions.microsoft.com> wrote in message
news:718B30EB-2CDE-4F7A-B995-2254B4B3217C@.microsoft.com...
> Hi all:
> I am trying to attach db created in SQL 2000, detached and written on CD-ROM
> in SQL 2005 and vice versa.
> If I try to attach on the same SQL Server where it was created, it works fine.
> I am using SQL 2000 generated db files as template to create databases
> through API, both on SQL 2000 & on SQL 2005 machine.
>
> 1. When the database created on SQL 2005 attached in SQL 2000, I get the
> following error.
> Server: Msg 602, Level 21, State 50, Line 1
> Could not find row in sysindexes for database ID 13, object ID 1, index ID
> 1. Run DBCC CHECKTABLE on sysindexes.
> 2. When the database created on SQL 2000 is attached in SQL 2005, I get the
> following error.
> Msg 3415, Level 16, State 1, Line 1
> Database 'DB1' cannot be upgraded because it is read-only or has read-only
> files. Make the database or files writeable, and rerun recovery.
> Is there a workaround for this issue.
> Any help would be appreciated.
> TIA
> -srini
|||Thank you Tibor.
"Tibor Karaszi" wrote:

> You can't attach a 2005 db to 2000, regardless of read-only media or not.
> As for attaching 2000 database to 2005, it is doable, but SQL Server has to be able to upgrade the
> file structure. this means that for attach to work, the media cannot be read-only.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "srini" <srini@.discussions.microsoft.com> wrote in message
> news:718B30EB-2CDE-4F7A-B995-2254B4B3217C@.microsoft.com...
>