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...
>
Showing posts with label detached. Show all posts
Showing posts with label detached. Show all posts
Thursday, February 16, 2012
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 fin
e.
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
-sriniYou 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-R
OM
> in SQL 2005 and vice versa.
> If I try to attach on the same SQL Server where it was created, it works f
ine.
> 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 t
he
> 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 t
o be able to upgrade the
> file structure. this means that for attach to work, the media cannot be re
ad-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...
>
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 fin
e.
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
-sriniYou 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-R
OM
> in SQL 2005 and vice versa.
> If I try to attach on the same SQL Server where it was created, it works f
ine.
> 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 t
he
> 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 t
o be able to upgrade the
> file structure. this means that for attach to work, the media cannot be re
ad-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...
>
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
-sriniYou 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...
> > 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
>
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
-sriniYou 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...
> > 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
>
attaching DB using single MDF file
Hi there,
I'm trying to attach a DB using a single MDF file. The file was not properly detached as our server had crashed suddenly neither was the a proper backup done..When I try to attach it says
"the file you've specified is not a valid sql server database file" . But another database was restored using a MDF file without any problems ?
Please do get back if anyone may get what the problem likely is ? It'd be of great help. Let me know if my problem was clear or if I've to put it in a different fashion.
Cheers
GaneshOriginally posted by gans_sr
Hi there,
I'm trying to attach a DB using a single MDF file. The file was not properly detached as our server had crashed suddenly neither was the a proper backup done..When I try to attach it says
"the file you've specified is not a valid sql server database file" . But another database was restored using a MDF file without any problems ?
Please do get back if anyone may get what the problem likely is ? It'd be of great help. Let me know if my problem was clear or if I've to put it in a different fashion.
Cheers
Ganesh
what do u mean by
other database was restored using a MDF file without any problems ?
was it the same file which u r trying to restore again??
to me it seems that the database file is corrupted and u will have to look for the most recent backup for the database.|||Harshal,
Its not the same file and its a differnt one . I also reckon it could be corrupt, but do you think it can be repaired by any chance ?
About backup, somehting had happened to hte server it seems , may be some virus and it stopped job schedule on sql server also.
Thanks for any ideas
Ganesh|||Originally posted by gans_sr
Harshal,
Its not the same file and its a differnt one . I also reckon it could be corrupt, but do you think it can be repaired by any chance ?
About backup, somehting had happened to hte server it seems , may be some virus and it stopped job schedule on sql server also.
Thanks for any ideas
Ganesh
In that case u r in a real problem! I haven't heard of repairing a corrupt database file yet.The only solution that I see is to get the latest workable backup from the backup sets and restore them. I hope you have some backups before the job stopped running.
and also once every thing is running, do configure an alert for all the jobs so that their status is mailed to u every time they run.
regards,
Harshal.|||Thanks Harshal .Looks like thats the only option available now.
I'm trying to attach a DB using a single MDF file. The file was not properly detached as our server had crashed suddenly neither was the a proper backup done..When I try to attach it says
"the file you've specified is not a valid sql server database file" . But another database was restored using a MDF file without any problems ?
Please do get back if anyone may get what the problem likely is ? It'd be of great help. Let me know if my problem was clear or if I've to put it in a different fashion.
Cheers
GaneshOriginally posted by gans_sr
Hi there,
I'm trying to attach a DB using a single MDF file. The file was not properly detached as our server had crashed suddenly neither was the a proper backup done..When I try to attach it says
"the file you've specified is not a valid sql server database file" . But another database was restored using a MDF file without any problems ?
Please do get back if anyone may get what the problem likely is ? It'd be of great help. Let me know if my problem was clear or if I've to put it in a different fashion.
Cheers
Ganesh
what do u mean by
other database was restored using a MDF file without any problems ?
was it the same file which u r trying to restore again??
to me it seems that the database file is corrupted and u will have to look for the most recent backup for the database.|||Harshal,
Its not the same file and its a differnt one . I also reckon it could be corrupt, but do you think it can be repaired by any chance ?
About backup, somehting had happened to hte server it seems , may be some virus and it stopped job schedule on sql server also.
Thanks for any ideas
Ganesh|||Originally posted by gans_sr
Harshal,
Its not the same file and its a differnt one . I also reckon it could be corrupt, but do you think it can be repaired by any chance ?
About backup, somehting had happened to hte server it seems , may be some virus and it stopped job schedule on sql server also.
Thanks for any ideas
Ganesh
In that case u r in a real problem! I haven't heard of repairing a corrupt database file yet.The only solution that I see is to get the latest workable backup from the backup sets and restore them. I hope you have some backups before the job stopped running.
and also once every thing is running, do configure an alert for all the jobs so that their status is mailed to u every time they run.
regards,
Harshal.|||Thanks Harshal .Looks like thats the only option available now.
Monday, February 13, 2012
Attaching Database Failed
Can someone please help me with this problem.
I Did a database backup from serverA and restore to
serverB using w2k. I detached the database from serverB,
and when try to attach to the restored database, I got an
error" Error 9003:The LSN(120998:148:1) passed to log
scan in database "xyz" is invalid.
How do I fix this error. Thanks.Hi
That is a Severity 20 error. Errors messages with a severity level of 20 or
higher are considered fatal errors and terminate the client connection.
There is a KB article # 328354 (FIX: A RESTORE DATABASE WITH RECOVERY
Statement Can Fail with Error 9003 or Error 9004), but that was fixed in
SP3.
If you are running SP3, you either have a corrupt DB, or you have
encountered another problem. In the latter's case, call your local Microsoft
PSS.
I would bet that the DB is corrupt. Where did you try to attach the DB
again, server B?
Can you try to restore the backup from Server A again on Server B and then
run DBCC CHECKDB and DBCC CHECKALLOC to see if you have corruption and it
came across in the backup?
--
Mike Epprecht, Microsoft SQL Server MVP
Epprecht Consulting (PTY) LTD
Johannesburg, South Africa
Mobile: +27-82-552-0268
IM: mike@.NOSPAMepprecht.net
Specialist SQL Server Solutions and Consulting
"Someone" <anonymous@.discussions.microsoft.com> wrote in message
news:1ff201c3e05c$bf1da530$a501280a@.phx.gbl...
database and I got the same error again. I am doing a new
restore as I write this and I will try to attach again.
Thanks.
severity level of 20 or
client connection.
WITH RECOVERY
that was fixed in
you have
your local Microsoft
attach the DB
Server B and then
corruption and it
message
I tried to attach to the database again.
new
From http://www.google.com.tr/search?q=e...elopmentnow.com
I Did a database backup from serverA and restore to
serverB using w2k. I detached the database from serverB,
and when try to attach to the restored database, I got an
error" Error 9003:The LSN(120998:148:1) passed to log
scan in database "xyz" is invalid.
How do I fix this error. Thanks.Hi
That is a Severity 20 error. Errors messages with a severity level of 20 or
higher are considered fatal errors and terminate the client connection.
There is a KB article # 328354 (FIX: A RESTORE DATABASE WITH RECOVERY
Statement Can Fail with Error 9003 or Error 9004), but that was fixed in
SP3.
If you are running SP3, you either have a corrupt DB, or you have
encountered another problem. In the latter's case, call your local Microsoft
PSS.
I would bet that the DB is corrupt. Where did you try to attach the DB
again, server B?
Can you try to restore the backup from Server A again on Server B and then
run DBCC CHECKDB and DBCC CHECKALLOC to see if you have corruption and it
came across in the backup?
--
Mike Epprecht, Microsoft SQL Server MVP
Epprecht Consulting (PTY) LTD
Johannesburg, South Africa
Mobile: +27-82-552-0268
IM: mike@.NOSPAMepprecht.net
Specialist SQL Server Solutions and Consulting
"Someone" <anonymous@.discussions.microsoft.com> wrote in message
news:1ff201c3e05c$bf1da530$a501280a@.phx.gbl...
quote:|||Thank you for your reply. I applied sp3 and reattach the
> Can someone please help me with this problem.
> I Did a database backup from serverA and restore to
> serverB using w2k. I detached the database from serverB,
> and when try to attach to the restored database, I got an
> error" Error 9003:The LSN(120998:148:1) passed to log
> scan in database "xyz" is invalid.
> How do I fix this error. Thanks.
database and I got the same error again. I am doing a new
restore as I write this and I will try to attach again.
Thanks.
quote:
>--Original Message--
>Hi
>That is a Severity 20 error. Errors messages with a
severity level of 20 or
quote:
>higher are considered fatal errors and terminate the
client connection.
quote:
>There is a KB article # 328354 (FIX: A RESTORE DATABASE
WITH RECOVERY
quote:
>Statement Can Fail with Error 9003 or Error 9004), but
that was fixed in
quote:
>SP3.
>If you are running SP3, you either have a corrupt DB, or
you have
quote:
>encountered another problem. In the latter's case, call
your local Microsoft
quote:
>PSS.
>I would bet that the DB is corrupt. Where did you try to
attach the DB
quote:
>again, server B?
>Can you try to restore the backup from Server A again on
Server B and then
quote:
>run DBCC CHECKDB and DBCC CHECKALLOC to see if you have
corruption and it
quote:
>came across in the backup?
>
>--
>--
>Mike Epprecht, Microsoft SQL Server MVP
>Epprecht Consulting (PTY) LTD
>Johannesburg, South Africa
>Mobile: +27-82-552-0268
>IM: mike@.NOSPAMepprecht.net
>Specialist SQL Server Solutions and Consulting
>"Someone" <anonymous@.discussions.microsoft.com> wrote in
message
quote:|||I just finished the restore, and got the same error when
>news:1ff201c3e05c$bf1da530$a501280a@.phx.gbl...
serverB,[QUOTE]
an[QUOTE]
>
>.
>
I tried to attach to the database again.
quote:
>--Original Message--
>Thank you for your reply. I applied sp3 and reattach the
>database and I got the same error again. I am doing a
new
quote:|||wsd
>restore as I write this and I will try to attach again.
>Thanks.
>
>severity level of 20 or
>client connection.
DATABASE[QUOTE]
>WITH RECOVERY
>that was fixed in
or[QUOTE]
>you have
>your local Microsoft
to[QUOTE]
>attach the DB
on[QUOTE]
>Server B and then
>corruption and it
in[QUOTE]
>message
>serverB,
got[QUOTE]
>an
>.
>
From http://www.google.com.tr/search?q=e...elopmentnow.com
Attaching an SQL .MDF file to an MSDE Instance
I have installed an instance of MSDE. I have a full version of SQLServer2000 and have created all of the procs, etc. and have detached the .mdf file from the full version of SQLServer2000. How do I attach the tables, procs, etc in the MDF file to the MSDE instance?Hi,
Login to SQL Server using OSQL and use sp_attch_db store procedure to attach
the database.
Thanks
Hari
MCDBA
"Tom Buchanan" <thomasfbuchanan@.hotmail.com> wrote in message
news:46FB74F5-46C5-4379-A640-C0F71124D135@.microsoft.com...
> I have installed an instance of MSDE. I have a full version of
SQLServer2000 and have created all of the procs, etc. and have detached the
.mdf file from the full version of SQLServer2000. How do I attach the
tables, procs, etc in the MDF file to the MSDE instance?
Login to SQL Server using OSQL and use sp_attch_db store procedure to attach
the database.
Thanks
Hari
MCDBA
"Tom Buchanan" <thomasfbuchanan@.hotmail.com> wrote in message
news:46FB74F5-46C5-4379-A640-C0F71124D135@.microsoft.com...
> I have installed an instance of MSDE. I have a full version of
SQLServer2000 and have created all of the procs, etc. and have detached the
.mdf file from the full version of SQLServer2000. How do I attach the
tables, procs, etc in the MDF file to the MSDE instance?
Sunday, February 12, 2012
Attaching a Database which was not deatached.
Hello Can anyone please tell me how i can attach a database which was not
detached from the server previously?
right now when i try to use sp_attach_db i get error code 9004 , same thing
happens in SQL Enterprise manager...
I made backup of the 2 datafile/logfile on cd-rom but when i try to attach
them after the server hardware failed, i get that weird 9004 error code.Did you make a SQL Server backup of the database by issuing a BACKUP
DATABASE command?
What version and service pack are you using?
You might find the following useful:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;277843
http://support.microsoft.com/default.aspx?scid=kb;EN-US;274797
--
Bryan Bitzer MCP
Senior Database Administrator
Marshall & Swift / Boeckh
www.msbinfo.com
"Artmic" <Artmic@.discussions.microsoft.com> wrote in message
news:2DB5489D-137F-4A40-8122-810E9F80036C@.microsoft.com...
> Hello Can anyone please tell me how i can attach a database which was not
> detached from the server previously?
> right now when i try to use sp_attach_db i get error code 9004 , same
thing
> happens in SQL Enterprise manager...
>
> I made backup of the 2 datafile/logfile on cd-rom but when i try to attach
> them after the server hardware failed, i get that weird 9004 error code.
>|||9004 usually means you have a corrupt logfile (means that your logfile is
useless)
you can try
sp_attach_single_file_db (use datafile only)
see how this goes.
"Bryan Bitzer" wrote:
> Did you make a SQL Server backup of the database by issuing a BACKUP
> DATABASE command?
> What version and service pack are you using?
> You might find the following useful:
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;277843
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;274797
> --
> Bryan Bitzer MCP
> Senior Database Administrator
> Marshall & Swift / Boeckh
> www.msbinfo.com
> "Artmic" <Artmic@.discussions.microsoft.com> wrote in message
> news:2DB5489D-137F-4A40-8122-810E9F80036C@.microsoft.com...
> > Hello Can anyone please tell me how i can attach a database which was not
> > detached from the server previously?
> >
> > right now when i try to use sp_attach_db i get error code 9004 , same
> thing
> > happens in SQL Enterprise manager...
> >
> >
> > I made backup of the 2 datafile/logfile on cd-rom but when i try to attach
> > them after the server hardware failed, i get that weird 9004 error code.
> >
>
>
detached from the server previously?
right now when i try to use sp_attach_db i get error code 9004 , same thing
happens in SQL Enterprise manager...
I made backup of the 2 datafile/logfile on cd-rom but when i try to attach
them after the server hardware failed, i get that weird 9004 error code.Did you make a SQL Server backup of the database by issuing a BACKUP
DATABASE command?
What version and service pack are you using?
You might find the following useful:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;277843
http://support.microsoft.com/default.aspx?scid=kb;EN-US;274797
--
Bryan Bitzer MCP
Senior Database Administrator
Marshall & Swift / Boeckh
www.msbinfo.com
"Artmic" <Artmic@.discussions.microsoft.com> wrote in message
news:2DB5489D-137F-4A40-8122-810E9F80036C@.microsoft.com...
> Hello Can anyone please tell me how i can attach a database which was not
> detached from the server previously?
> right now when i try to use sp_attach_db i get error code 9004 , same
thing
> happens in SQL Enterprise manager...
>
> I made backup of the 2 datafile/logfile on cd-rom but when i try to attach
> them after the server hardware failed, i get that weird 9004 error code.
>|||9004 usually means you have a corrupt logfile (means that your logfile is
useless)
you can try
sp_attach_single_file_db (use datafile only)
see how this goes.
"Bryan Bitzer" wrote:
> Did you make a SQL Server backup of the database by issuing a BACKUP
> DATABASE command?
> What version and service pack are you using?
> You might find the following useful:
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;277843
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;274797
> --
> Bryan Bitzer MCP
> Senior Database Administrator
> Marshall & Swift / Boeckh
> www.msbinfo.com
> "Artmic" <Artmic@.discussions.microsoft.com> wrote in message
> news:2DB5489D-137F-4A40-8122-810E9F80036C@.microsoft.com...
> > Hello Can anyone please tell me how i can attach a database which was not
> > detached from the server previously?
> >
> > right now when i try to use sp_attach_db i get error code 9004 , same
> thing
> > happens in SQL Enterprise manager...
> >
> >
> > I made backup of the 2 datafile/logfile on cd-rom but when i try to attach
> > them after the server hardware failed, i get that weird 9004 error code.
> >
>
>
Thursday, February 9, 2012
Attach onto different Server - Database Read Only
Hiya,
I have just detached and reattached a database from one server to another
but its read only, can anyone tell me why ?
Thanks
Hello,
Have you checked the read only flag in the database settings ?
Also check the access rights of the files themselves to see if there is
update permission on the server.
Peter
"A politician needs the ability to foretell what is going to happen
tomorrow, next week, next month, and next year. And to have the ability
afterwards to explain why it didn't happen."
Winston Churchill
"Patricia" wrote:
> Hiya,
> I have just detached and reattached a database from one server to another
> but its read only, can anyone tell me why ?
> Thanks
|||Perhaps you need to re-assign user names to SQL Server logins.
Have a look at the description of the following functions in Books Online:
sp_change_users_login
sp_changedbowner
Regards,
Axel
"Patricia" <Patricia@.discussions.microsoft.com> schrieb im Newsbeitrag
news:145F306A-FB47-4E7A-9263-FB905631E01F@.microsoft.com...
> Hiya,
> I have just detached and reattached a database from one server to another
> but its read only, can anyone tell me why ?
> Thanks
I have just detached and reattached a database from one server to another
but its read only, can anyone tell me why ?
Thanks
Hello,
Have you checked the read only flag in the database settings ?
Also check the access rights of the files themselves to see if there is
update permission on the server.
Peter
"A politician needs the ability to foretell what is going to happen
tomorrow, next week, next month, and next year. And to have the ability
afterwards to explain why it didn't happen."
Winston Churchill
"Patricia" wrote:
> Hiya,
> I have just detached and reattached a database from one server to another
> but its read only, can anyone tell me why ?
> Thanks
|||Perhaps you need to re-assign user names to SQL Server logins.
Have a look at the description of the following functions in Books Online:
sp_change_users_login
sp_changedbowner
Regards,
Axel
"Patricia" <Patricia@.discussions.microsoft.com> schrieb im Newsbeitrag
news:145F306A-FB47-4E7A-9263-FB905631E01F@.microsoft.com...
> Hiya,
> I have just detached and reattached a database from one server to another
> but its read only, can anyone tell me why ?
> Thanks
Attach onto different Server - Database Read Only
Hiya,
I have just detached and reattached a database from one server to another
but its read only, can anyone tell me why ?
ThanksHello,
Have you checked the read only flag in the database settings ?
Also check the access rights of the files themselves to see if there is
update permission on the server.
Peter
"A politician needs the ability to foretell what is going to happen
tomorrow, next week, next month, and next year. And to have the ability
afterwards to explain why it didn't happen."
Winston Churchill
"Patricia" wrote:
> Hiya,
> I have just detached and reattached a database from one server to another
> but its read only, can anyone tell me why ?
> Thanks|||Perhaps you need to re-assign user names to SQL Server logins.
Have a look at the description of the following functions in Books Online:
sp_change_users_login
sp_changedbowner
Regards,
Axel
"Patricia" <Patricia@.discussions.microsoft.com> schrieb im Newsbeitrag
news:145F306A-FB47-4E7A-9263-FB905631E01F@.microsoft.com...
> Hiya,
> I have just detached and reattached a database from one server to another
> but its read only, can anyone tell me why ?
> Thanks
I have just detached and reattached a database from one server to another
but its read only, can anyone tell me why ?
ThanksHello,
Have you checked the read only flag in the database settings ?
Also check the access rights of the files themselves to see if there is
update permission on the server.
Peter
"A politician needs the ability to foretell what is going to happen
tomorrow, next week, next month, and next year. And to have the ability
afterwards to explain why it didn't happen."
Winston Churchill
"Patricia" wrote:
> Hiya,
> I have just detached and reattached a database from one server to another
> but its read only, can anyone tell me why ?
> Thanks|||Perhaps you need to re-assign user names to SQL Server logins.
Have a look at the description of the following functions in Books Online:
sp_change_users_login
sp_changedbowner
Regards,
Axel
"Patricia" <Patricia@.discussions.microsoft.com> schrieb im Newsbeitrag
news:145F306A-FB47-4E7A-9263-FB905631E01F@.microsoft.com...
> Hiya,
> I have just detached and reattached a database from one server to another
> but its read only, can anyone tell me why ?
> Thanks
Attach onto different Server - Database Read Only
Hiya,
I have just detached and reattached a database from one server to another
but its read only, can anyone tell me why ?
ThanksHello,
Have you checked the read only flag in the database settings ?
Also check the access rights of the files themselves to see if there is
update permission on the server.
Peter
"A politician needs the ability to foretell what is going to happen
tomorrow, next week, next month, and next year. And to have the ability
afterwards to explain why it didn't happen."
Winston Churchill
"Patricia" wrote:
> Hiya,
> I have just detached and reattached a database from one server to another
> but its read only, can anyone tell me why ?
> Thanks|||Perhaps you need to re-assign user names to SQL Server logins.
Have a look at the description of the following functions in Books Online:
sp_change_users_login
sp_changedbowner
Regards,
Axel
--
"Patricia" <Patricia@.discussions.microsoft.com> schrieb im Newsbeitrag
news:145F306A-FB47-4E7A-9263-FB905631E01F@.microsoft.com...
> Hiya,
> I have just detached and reattached a database from one server to another
> but its read only, can anyone tell me why ?
> Thanks
I have just detached and reattached a database from one server to another
but its read only, can anyone tell me why ?
ThanksHello,
Have you checked the read only flag in the database settings ?
Also check the access rights of the files themselves to see if there is
update permission on the server.
Peter
"A politician needs the ability to foretell what is going to happen
tomorrow, next week, next month, and next year. And to have the ability
afterwards to explain why it didn't happen."
Winston Churchill
"Patricia" wrote:
> Hiya,
> I have just detached and reattached a database from one server to another
> but its read only, can anyone tell me why ?
> Thanks|||Perhaps you need to re-assign user names to SQL Server logins.
Have a look at the description of the following functions in Books Online:
sp_change_users_login
sp_changedbowner
Regards,
Axel
--
"Patricia" <Patricia@.discussions.microsoft.com> schrieb im Newsbeitrag
news:145F306A-FB47-4E7A-9263-FB905631E01F@.microsoft.com...
> Hiya,
> I have just detached and reattached a database from one server to another
> but its read only, can anyone tell me why ?
> Thanks
Subscribe to:
Posts (Atom)