I have 2 SQL 2K servers, ea running Server2k SP4 and SQL2K SP4. In EnterPrise
Manager, when I right-click on my 2 main databases, choose All
Tasks...Restore, I then get a perpetual hour-glass & have to terminate ER to
stop it. If I do this for any of the sample databases, the Restore dialogue
opens. I even verified there were no open connections to the 2 databases in
question, & it happens on both servers. I had to do a command line restore.
The backup, etc works fine, just the restore won't open. It did this on SQL
SP3 & I hoped installing SP4 would fix it, but no go. Any ideas? I even
terminated any non-critical services to no avail, i.e. Backup Exec services,
Trend Micro AV, etc.
Ted
Possibly a LOT of backuphistory to read. Check out the number of rows in the backup history tables
in msdb. Also, read about sp_delete_backuphistory (which takes a long time to run in order to delete
a lot of backup history).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ted Cole" <Ted Cole@.discussions.microsoft.com> wrote in message
news:99032F45-145B-4500-ABCB-9B922BB540E1@.microsoft.com...
>I have 2 SQL 2K servers, ea running Server2k SP4 and SQL2K SP4. In EnterPrise
> Manager, when I right-click on my 2 main databases, choose All
> Tasks...Restore, I then get a perpetual hour-glass & have to terminate ER to
> stop it. If I do this for any of the sample databases, the Restore dialogue
> opens. I even verified there were no open connections to the 2 databases in
> question, & it happens on both servers. I had to do a command line restore.
> The backup, etc works fine, just the restore won't open. It did this on SQL
> SP3 & I hoped installing SP4 would fix it, but no go. Any ideas? I even
> terminated any non-critical services to no avail, i.e. Backup Exec services,
> Trend Micro AV, etc.
> Ted
sql
Showing posts with label running. Show all posts
Showing posts with label running. Show all posts
Friday, March 30, 2012
Restore won't open
I have 2 SQL 2K servers, ea running Server2k SP4 and SQL2K SP4. In EnterPris
e
Manager, when I right-click on my 2 main databases, choose All
Tasks...Restore, I then get a perpetual hour-glass & have to terminate ER to
stop it. If I do this for any of the sample databases, the Restore dialogue
opens. I even verified there were no open connections to the 2 databases in
question, & it happens on both servers. I had to do a command line restore.
The backup, etc works fine, just the restore won't open. It did this on SQL
SP3 & I hoped installing SP4 would fix it, but no go. Any ideas? I even
terminated any non-critical services to no avail, i.e. Backup Exec services,
Trend Micro AV, etc.
TedPossibly a LOT of backuphistory to read. Check out the number of rows in the
backup history tables
in msdb. Also, read about sp_delete_backuphistory (which takes a long time t
o run in order to delete
a lot of backup history).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ted Cole" <Ted Cole@.discussions.microsoft.com> wrote in message
news:99032F45-145B-4500-ABCB-9B922BB540E1@.microsoft.com...
>I have 2 SQL 2K servers, ea running Server2k SP4 and SQL2K SP4. In EnterPri
se
> Manager, when I right-click on my 2 main databases, choose All
> Tasks...Restore, I then get a perpetual hour-glass & have to terminate ER
to
> stop it. If I do this for any of the sample databases, the Restore dialogu
e
> opens. I even verified there were no open connections to the 2 databases i
n
> question, & it happens on both servers. I had to do a command line restore
.
> The backup, etc works fine, just the restore won't open. It did this on SQ
L
> SP3 & I hoped installing SP4 would fix it, but no go. Any ideas? I even
> terminated any non-critical services to no avail, i.e. Backup Exec service
s,
> Trend Micro AV, etc.
> Ted
e
Manager, when I right-click on my 2 main databases, choose All
Tasks...Restore, I then get a perpetual hour-glass & have to terminate ER to
stop it. If I do this for any of the sample databases, the Restore dialogue
opens. I even verified there were no open connections to the 2 databases in
question, & it happens on both servers. I had to do a command line restore.
The backup, etc works fine, just the restore won't open. It did this on SQL
SP3 & I hoped installing SP4 would fix it, but no go. Any ideas? I even
terminated any non-critical services to no avail, i.e. Backup Exec services,
Trend Micro AV, etc.
TedPossibly a LOT of backuphistory to read. Check out the number of rows in the
backup history tables
in msdb. Also, read about sp_delete_backuphistory (which takes a long time t
o run in order to delete
a lot of backup history).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ted Cole" <Ted Cole@.discussions.microsoft.com> wrote in message
news:99032F45-145B-4500-ABCB-9B922BB540E1@.microsoft.com...
>I have 2 SQL 2K servers, ea running Server2k SP4 and SQL2K SP4. In EnterPri
se
> Manager, when I right-click on my 2 main databases, choose All
> Tasks...Restore, I then get a perpetual hour-glass & have to terminate ER
to
> stop it. If I do this for any of the sample databases, the Restore dialogu
e
> opens. I even verified there were no open connections to the 2 databases i
n
> question, & it happens on both servers. I had to do a command line restore
.
> The backup, etc works fine, just the restore won't open. It did this on SQ
L
> SP3 & I hoped installing SP4 would fix it, but no go. Any ideas? I even
> terminated any non-critical services to no avail, i.e. Backup Exec service
s,
> Trend Micro AV, etc.
> Ted
Restore won't open
I have 2 SQL 2K servers, ea running Server2k SP4 and SQL2K SP4. In EnterPrise
Manager, when I right-click on my 2 main databases, choose All
Tasks...Restore, I then get a perpetual hour-glass & have to terminate ER to
stop it. If I do this for any of the sample databases, the Restore dialogue
opens. I even verified there were no open connections to the 2 databases in
question, & it happens on both servers. I had to do a command line restore.
The backup, etc works fine, just the restore won't open. It did this on SQL
SP3 & I hoped installing SP4 would fix it, but no go. Any ideas? I even
terminated any non-critical services to no avail, i.e. Backup Exec services,
Trend Micro AV, etc.
TedPossibly a LOT of backuphistory to read. Check out the number of rows in the backup history tables
in msdb. Also, read about sp_delete_backuphistory (which takes a long time to run in order to delete
a lot of backup history).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ted Cole" <Ted Cole@.discussions.microsoft.com> wrote in message
news:99032F45-145B-4500-ABCB-9B922BB540E1@.microsoft.com...
>I have 2 SQL 2K servers, ea running Server2k SP4 and SQL2K SP4. In EnterPrise
> Manager, when I right-click on my 2 main databases, choose All
> Tasks...Restore, I then get a perpetual hour-glass & have to terminate ER to
> stop it. If I do this for any of the sample databases, the Restore dialogue
> opens. I even verified there were no open connections to the 2 databases in
> question, & it happens on both servers. I had to do a command line restore.
> The backup, etc works fine, just the restore won't open. It did this on SQL
> SP3 & I hoped installing SP4 would fix it, but no go. Any ideas? I even
> terminated any non-critical services to no avail, i.e. Backup Exec services,
> Trend Micro AV, etc.
> Ted
Manager, when I right-click on my 2 main databases, choose All
Tasks...Restore, I then get a perpetual hour-glass & have to terminate ER to
stop it. If I do this for any of the sample databases, the Restore dialogue
opens. I even verified there were no open connections to the 2 databases in
question, & it happens on both servers. I had to do a command line restore.
The backup, etc works fine, just the restore won't open. It did this on SQL
SP3 & I hoped installing SP4 would fix it, but no go. Any ideas? I even
terminated any non-critical services to no avail, i.e. Backup Exec services,
Trend Micro AV, etc.
TedPossibly a LOT of backuphistory to read. Check out the number of rows in the backup history tables
in msdb. Also, read about sp_delete_backuphistory (which takes a long time to run in order to delete
a lot of backup history).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ted Cole" <Ted Cole@.discussions.microsoft.com> wrote in message
news:99032F45-145B-4500-ABCB-9B922BB540E1@.microsoft.com...
>I have 2 SQL 2K servers, ea running Server2k SP4 and SQL2K SP4. In EnterPrise
> Manager, when I right-click on my 2 main databases, choose All
> Tasks...Restore, I then get a perpetual hour-glass & have to terminate ER to
> stop it. If I do this for any of the sample databases, the Restore dialogue
> opens. I even verified there were no open connections to the 2 databases in
> question, & it happens on both servers. I had to do a command line restore.
> The backup, etc works fine, just the restore won't open. It did this on SQL
> SP3 & I hoped installing SP4 would fix it, but no go. Any ideas? I even
> terminated any non-critical services to no avail, i.e. Backup Exec services,
> Trend Micro AV, etc.
> Ted
Wednesday, March 28, 2012
restore two databases from one device
Is it possible to have two restores running at the same
time restoring two databases to two different servers from
the same backup device? For example, I have server A and
server B. I want to restore pubs to both A and B at the
same time from last night's backup device. Thanks!
Hi,
A Single file can be opened for reading by only one process.
Thanks
Hari
MCDBA
<anonymous@.discussions.microsoft.com> wrote in message
news:275f201c46381$aa08f020$a501280a@.phx.gbl...
> Is it possible to have two restores running at the same
> time restoring two databases to two different servers from
> the same backup device? For example, I have server A and
> server B. I want to restore pubs to both A and B at the
> same time from last night's backup device. Thanks!
|||Darn NT!!!
>--Original Message--
>Hi,
>A Single file can be opened for reading by only one
process.[vbcol=seagreen]
>Thanks
>Hari
>MCDBA
>
><anonymous@.discussions.microsoft.com> wrote in message
>news:275f201c46381$aa08f020$a501280a@.phx.gbl...
from[vbcol=seagreen]
and
>
>.
>
|||No, files can be opened either shared or exclusive.
But sorry, I don't know which mode SQL does.
Why not just try it?
>--Original Message--
>Hi,
>A Single file can be opened for reading by only one
process.[vbcol=seagreen]
>Thanks
>Hari
>MCDBA
>
><anonymous@.discussions.microsoft.com> wrote in message
>news:275f201c46381$aa08f020$a501280a@.phx.gbl...
from[vbcol=seagreen]
and
>
>.
>
sql
time restoring two databases to two different servers from
the same backup device? For example, I have server A and
server B. I want to restore pubs to both A and B at the
same time from last night's backup device. Thanks!
Hi,
A Single file can be opened for reading by only one process.
Thanks
Hari
MCDBA
<anonymous@.discussions.microsoft.com> wrote in message
news:275f201c46381$aa08f020$a501280a@.phx.gbl...
> Is it possible to have two restores running at the same
> time restoring two databases to two different servers from
> the same backup device? For example, I have server A and
> server B. I want to restore pubs to both A and B at the
> same time from last night's backup device. Thanks!
|||Darn NT!!!
>--Original Message--
>Hi,
>A Single file can be opened for reading by only one
process.[vbcol=seagreen]
>Thanks
>Hari
>MCDBA
>
><anonymous@.discussions.microsoft.com> wrote in message
>news:275f201c46381$aa08f020$a501280a@.phx.gbl...
from[vbcol=seagreen]
and
>
>.
>
|||No, files can be opened either shared or exclusive.
But sorry, I don't know which mode SQL does.
Why not just try it?
>--Original Message--
>Hi,
>A Single file can be opened for reading by only one
process.[vbcol=seagreen]
>Thanks
>Hari
>MCDBA
>
><anonymous@.discussions.microsoft.com> wrote in message
>news:275f201c46381$aa08f020$a501280a@.phx.gbl...
from[vbcol=seagreen]
and
>
>.
>
sql
restore two databases from one device
Is it possible to have two restores running at the same
time restoring two databases to two different servers from
the same backup device? For example, I have server A and
server B. I want to restore pubs to both A and B at the
same time from last night's backup device. Thanks!Hi,
A Single file can be opened for reading by only one process.
Thanks
Hari
MCDBA
<anonymous@.discussions.microsoft.com> wrote in message
news:275f201c46381$aa08f020$a501280a@.phx
.gbl...
> Is it possible to have two restores running at the same
> time restoring two databases to two different servers from
> the same backup device? For example, I have server A and
> server B. I want to restore pubs to both A and B at the
> same time from last night's backup device. Thanks!|||Darn NT!!!
>--Original Message--
>Hi,
>A Single file can be opened for reading by only one
process.
>Thanks
>Hari
>MCDBA
>
><anonymous@.discussions.microsoft.com> wrote in message
> news:275f201c46381$aa08f020$a501280a@.phx
.gbl...
from[vbcol=seagreen]
and[vbcol=seagreen]
>
>.
>|||No, files can be opened either shared or exclusive.
But sorry, I don't know which mode SQL does.
Why not just try it?
>--Original Message--
>Hi,
>A Single file can be opened for reading by only one
process.
>Thanks
>Hari
>MCDBA
>
><anonymous@.discussions.microsoft.com> wrote in message
> news:275f201c46381$aa08f020$a501280a@.phx
.gbl...
from[vbcol=seagreen]
and[vbcol=seagreen]
>
>.
>
time restoring two databases to two different servers from
the same backup device? For example, I have server A and
server B. I want to restore pubs to both A and B at the
same time from last night's backup device. Thanks!Hi,
A Single file can be opened for reading by only one process.
Thanks
Hari
MCDBA
<anonymous@.discussions.microsoft.com> wrote in message
news:275f201c46381$aa08f020$a501280a@.phx
.gbl...
> Is it possible to have two restores running at the same
> time restoring two databases to two different servers from
> the same backup device? For example, I have server A and
> server B. I want to restore pubs to both A and B at the
> same time from last night's backup device. Thanks!|||Darn NT!!!
>--Original Message--
>Hi,
>A Single file can be opened for reading by only one
process.
>Thanks
>Hari
>MCDBA
>
><anonymous@.discussions.microsoft.com> wrote in message
> news:275f201c46381$aa08f020$a501280a@.phx
.gbl...
from[vbcol=seagreen]
and[vbcol=seagreen]
>
>.
>|||No, files can be opened either shared or exclusive.
But sorry, I don't know which mode SQL does.
Why not just try it?
>--Original Message--
>Hi,
>A Single file can be opened for reading by only one
process.
>Thanks
>Hari
>MCDBA
>
><anonymous@.discussions.microsoft.com> wrote in message
> news:275f201c46381$aa08f020$a501280a@.phx
.gbl...
from[vbcol=seagreen]
and[vbcol=seagreen]
>
>.
>
restore two databases from one device
Is it possible to have two restores running at the same
time restoring two databases to two different servers from
the same backup device? For example, I have server A and
server B. I want to restore pubs to both A and B at the
same time from last night's backup device. Thanks!Hi,
A Single file can be opened for reading by only one process.
Thanks
Hari
MCDBA
<anonymous@.discussions.microsoft.com> wrote in message
news:275f201c46381$aa08f020$a501280a@.phx.gbl...
> Is it possible to have two restores running at the same
> time restoring two databases to two different servers from
> the same backup device? For example, I have server A and
> server B. I want to restore pubs to both A and B at the
> same time from last night's backup device. Thanks!|||Darn NT!!!
>--Original Message--
>Hi,
>A Single file can be opened for reading by only one
process.
>Thanks
>Hari
>MCDBA
>
><anonymous@.discussions.microsoft.com> wrote in message
>news:275f201c46381$aa08f020$a501280a@.phx.gbl...
>> Is it possible to have two restores running at the same
>> time restoring two databases to two different servers
from
>> the same backup device? For example, I have server A
and
>> server B. I want to restore pubs to both A and B at the
>> same time from last night's backup device. Thanks!
>
>.
>|||No, files can be opened either shared or exclusive.
But sorry, I don't know which mode SQL does.
Why not just try it?
>--Original Message--
>Hi,
>A Single file can be opened for reading by only one
process.
>Thanks
>Hari
>MCDBA
>
><anonymous@.discussions.microsoft.com> wrote in message
>news:275f201c46381$aa08f020$a501280a@.phx.gbl...
>> Is it possible to have two restores running at the same
>> time restoring two databases to two different servers
from
>> the same backup device? For example, I have server A
and
>> server B. I want to restore pubs to both A and B at the
>> same time from last night's backup device. Thanks!
>
>.
>
time restoring two databases to two different servers from
the same backup device? For example, I have server A and
server B. I want to restore pubs to both A and B at the
same time from last night's backup device. Thanks!Hi,
A Single file can be opened for reading by only one process.
Thanks
Hari
MCDBA
<anonymous@.discussions.microsoft.com> wrote in message
news:275f201c46381$aa08f020$a501280a@.phx.gbl...
> Is it possible to have two restores running at the same
> time restoring two databases to two different servers from
> the same backup device? For example, I have server A and
> server B. I want to restore pubs to both A and B at the
> same time from last night's backup device. Thanks!|||Darn NT!!!
>--Original Message--
>Hi,
>A Single file can be opened for reading by only one
process.
>Thanks
>Hari
>MCDBA
>
><anonymous@.discussions.microsoft.com> wrote in message
>news:275f201c46381$aa08f020$a501280a@.phx.gbl...
>> Is it possible to have two restores running at the same
>> time restoring two databases to two different servers
from
>> the same backup device? For example, I have server A
and
>> server B. I want to restore pubs to both A and B at the
>> same time from last night's backup device. Thanks!
>
>.
>|||No, files can be opened either shared or exclusive.
But sorry, I don't know which mode SQL does.
Why not just try it?
>--Original Message--
>Hi,
>A Single file can be opened for reading by only one
process.
>Thanks
>Hari
>MCDBA
>
><anonymous@.discussions.microsoft.com> wrote in message
>news:275f201c46381$aa08f020$a501280a@.phx.gbl...
>> Is it possible to have two restores running at the same
>> time restoring two databases to two different servers
from
>> the same backup device? For example, I have server A
and
>> server B. I want to restore pubs to both A and B at the
>> same time from last night's backup device. Thanks!
>
>.
>
Monday, March 26, 2012
restore to another server of db with FT catalogs
If we restore a backup copy of a production db having FT catalogs onto a
laptop running SQL Server Developer version, the restored db will contain
references to FT catalogs whose underlying system files are not yet present
on the laptop (because backup doesn't grab the FT system files). The index
rebuild takes only 20 minutes, so I'd prefer to recreate them rather than
move the FT system files. In that scenario, is it safe for the db on the
laptop to deactivate and drop the FT catalogs? Or can the missing system
files cause SQL Server to become unstable during the deactivation/drop
process? I'm thinking it shouldn't cause a problem, because if it did,
there'd be no way to drop a catalog whose system files had gotten corrupted.
But I lack the mental fortitude to experiment after the 7342 error consumed
most of my weekend, and am hoping you FTS gurus could handle this scenario
with your eyes closed and one arm tied behind your back. :-)
Thanks
Timo
consult this kb article for more information.
http://support.microsoft.com/default...b;en-us;240867
"Timo" <timo@.noneofyer.biz> wrote in message
news:eglQLxBGFHA.1188@.tk2msftngp13.phx.gbl...
> If we restore a backup copy of a production db having FT catalogs onto a
> laptop running SQL Server Developer version, the restored db will contain
> references to FT catalogs whose underlying system files are not yet
> present
> on the laptop (because backup doesn't grab the FT system files). The index
> rebuild takes only 20 minutes, so I'd prefer to recreate them rather than
> move the FT system files. In that scenario, is it safe for the db on the
> laptop to deactivate and drop the FT catalogs? Or can the missing system
> files cause SQL Server to become unstable during the deactivation/drop
> process? I'm thinking it shouldn't cause a problem, because if it did,
> there'd be no way to drop a catalog whose system files had gotten
> corrupted.
> But I lack the mental fortitude to experiment after the 7342 error
> consumed
> most of my weekend, and am hoping you FTS gurus could handle this scenario
> with your eyes closed and one arm tied behind your back. :-)
> Thanks
> Timo
>
|||Timo,
Yes, it is best to re-create the small FT Catalogs via normal procedures on
your laptop. However, successfully restoring a FT-enabled SQL Server 2000
database and then being able to re-create the lost FT Catalog depends upon
several factors - are the disk drives (drive letter & path) exactly the same
on the source server as the destination server? Are you restoring over an
existing database or are you restoring the database as a new database on the
laptop? The first factor will cause you problems (that can be overcome), the
second factor should work successfully. Overall, for SQL Server 2000 when
backing up FT-enabled databases, its best to disenable Full Text and then
backup the database...
You can also use the procedures in KB article: 240867 (Q240867) "INF: How to
Move, Copy, and Backup Full-Text Catalog Folders and Files" at
http://support.microsoft.com/default...b;EN-US;240867 to help you
as well understand these issues.
Hope that helps!
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Timo" <timo@.noneofyer.biz> wrote in message
news:eglQLxBGFHA.1188@.tk2msftngp13.phx.gbl...
> If we restore a backup copy of a production db having FT catalogs onto a
> laptop running SQL Server Developer version, the restored db will contain
> references to FT catalogs whose underlying system files are not yet
present
> on the laptop (because backup doesn't grab the FT system files). The index
> rebuild takes only 20 minutes, so I'd prefer to recreate them rather than
> move the FT system files. In that scenario, is it safe for the db on the
> laptop to deactivate and drop the FT catalogs? Or can the missing system
> files cause SQL Server to become unstable during the deactivation/drop
> process? I'm thinking it shouldn't cause a problem, because if it did,
> there'd be no way to drop a catalog whose system files had gotten
corrupted.
> But I lack the mental fortitude to experiment after the 7342 error
consumed
> most of my weekend, and am hoping you FTS gurus could handle this scenario
> with your eyes closed and one arm tied behind your back. :-)
> Thanks
> Timo
>
|||FYI, SQL 2K5 backups (as with sp_attach/detach_db) will contain FT indexes
"Timo" <timo@.noneofyer.biz> wrote in message
news:eglQLxBGFHA.1188@.tk2msftngp13.phx.gbl...
> If we restore a backup copy of a production db having FT catalogs onto a
> laptop running SQL Server Developer version, the restored db will contain
> references to FT catalogs whose underlying system files are not yet
present
> on the laptop (because backup doesn't grab the FT system files). The index
> rebuild takes only 20 minutes, so I'd prefer to recreate them rather than
> move the FT system files. In that scenario, is it safe for the db on the
> laptop to deactivate and drop the FT catalogs? Or can the missing system
> files cause SQL Server to become unstable during the deactivation/drop
> process? I'm thinking it shouldn't cause a problem, because if it did,
> there'd be no way to drop a catalog whose system files had gotten
corrupted.
> But I lack the mental fortitude to experiment after the 7342 error
consumed
> most of my weekend, and am hoping you FTS gurus could handle this scenario
> with your eyes closed and one arm tied behind your back. :-)
> Thanks
> Timo
>
laptop running SQL Server Developer version, the restored db will contain
references to FT catalogs whose underlying system files are not yet present
on the laptop (because backup doesn't grab the FT system files). The index
rebuild takes only 20 minutes, so I'd prefer to recreate them rather than
move the FT system files. In that scenario, is it safe for the db on the
laptop to deactivate and drop the FT catalogs? Or can the missing system
files cause SQL Server to become unstable during the deactivation/drop
process? I'm thinking it shouldn't cause a problem, because if it did,
there'd be no way to drop a catalog whose system files had gotten corrupted.
But I lack the mental fortitude to experiment after the 7342 error consumed
most of my weekend, and am hoping you FTS gurus could handle this scenario
with your eyes closed and one arm tied behind your back. :-)
Thanks
Timo
consult this kb article for more information.
http://support.microsoft.com/default...b;en-us;240867
"Timo" <timo@.noneofyer.biz> wrote in message
news:eglQLxBGFHA.1188@.tk2msftngp13.phx.gbl...
> If we restore a backup copy of a production db having FT catalogs onto a
> laptop running SQL Server Developer version, the restored db will contain
> references to FT catalogs whose underlying system files are not yet
> present
> on the laptop (because backup doesn't grab the FT system files). The index
> rebuild takes only 20 minutes, so I'd prefer to recreate them rather than
> move the FT system files. In that scenario, is it safe for the db on the
> laptop to deactivate and drop the FT catalogs? Or can the missing system
> files cause SQL Server to become unstable during the deactivation/drop
> process? I'm thinking it shouldn't cause a problem, because if it did,
> there'd be no way to drop a catalog whose system files had gotten
> corrupted.
> But I lack the mental fortitude to experiment after the 7342 error
> consumed
> most of my weekend, and am hoping you FTS gurus could handle this scenario
> with your eyes closed and one arm tied behind your back. :-)
> Thanks
> Timo
>
|||Timo,
Yes, it is best to re-create the small FT Catalogs via normal procedures on
your laptop. However, successfully restoring a FT-enabled SQL Server 2000
database and then being able to re-create the lost FT Catalog depends upon
several factors - are the disk drives (drive letter & path) exactly the same
on the source server as the destination server? Are you restoring over an
existing database or are you restoring the database as a new database on the
laptop? The first factor will cause you problems (that can be overcome), the
second factor should work successfully. Overall, for SQL Server 2000 when
backing up FT-enabled databases, its best to disenable Full Text and then
backup the database...
You can also use the procedures in KB article: 240867 (Q240867) "INF: How to
Move, Copy, and Backup Full-Text Catalog Folders and Files" at
http://support.microsoft.com/default...b;EN-US;240867 to help you
as well understand these issues.
Hope that helps!
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Timo" <timo@.noneofyer.biz> wrote in message
news:eglQLxBGFHA.1188@.tk2msftngp13.phx.gbl...
> If we restore a backup copy of a production db having FT catalogs onto a
> laptop running SQL Server Developer version, the restored db will contain
> references to FT catalogs whose underlying system files are not yet
present
> on the laptop (because backup doesn't grab the FT system files). The index
> rebuild takes only 20 minutes, so I'd prefer to recreate them rather than
> move the FT system files. In that scenario, is it safe for the db on the
> laptop to deactivate and drop the FT catalogs? Or can the missing system
> files cause SQL Server to become unstable during the deactivation/drop
> process? I'm thinking it shouldn't cause a problem, because if it did,
> there'd be no way to drop a catalog whose system files had gotten
corrupted.
> But I lack the mental fortitude to experiment after the 7342 error
consumed
> most of my weekend, and am hoping you FTS gurus could handle this scenario
> with your eyes closed and one arm tied behind your back. :-)
> Thanks
> Timo
>
|||FYI, SQL 2K5 backups (as with sp_attach/detach_db) will contain FT indexes
"Timo" <timo@.noneofyer.biz> wrote in message
news:eglQLxBGFHA.1188@.tk2msftngp13.phx.gbl...
> If we restore a backup copy of a production db having FT catalogs onto a
> laptop running SQL Server Developer version, the restored db will contain
> references to FT catalogs whose underlying system files are not yet
present
> on the laptop (because backup doesn't grab the FT system files). The index
> rebuild takes only 20 minutes, so I'd prefer to recreate them rather than
> move the FT system files. In that scenario, is it safe for the db on the
> laptop to deactivate and drop the FT catalogs? Or can the missing system
> files cause SQL Server to become unstable during the deactivation/drop
> process? I'm thinking it shouldn't cause a problem, because if it did,
> there'd be no way to drop a catalog whose system files had gotten
corrupted.
> But I lack the mental fortitude to experiment after the 7342 error
consumed
> most of my weekend, and am hoping you FTS gurus could handle this scenario
> with your eyes closed and one arm tied behind your back. :-)
> Thanks
> Timo
>
Friday, March 23, 2012
Restore SQL2K on different machine
Hello,
Would anyone know or recommend/advise the easiest approach in bringing down
and retiring an existing SQL2K running on W2K Server and brining it up with
all of the data, jobs, etc. onto a newer server machine? Wondering if there
was a way maybe do a full server restore from one of our server backup tapes
instead of having to reinstall/reconfigure everything from scratch.
Thanks in advance.Imaging is one approach if you have an imaging software like StorageCraft or
Acronis. But a main consideration here is hardware and configuration. The
source and destination may have different disk configurations. Another
considertation maybe to use Win2K3 instead of Win2K. If what you're
intending to restore is simply SQL Server, just a backup of all system and
user database would be enough and a very good restore process
On the old SQL Server instance,
1) stop all applications accessing your SQL Server
2) backup all your system and user databases
3) identify the latest hotfix you have. This is necessary for you to
restore on the new one
On the new SQL Server instance,
1) Install SQL Server together with the service packs and hotfixes up to the
one you have on the old instance
2) start SQL Server in single-user mode using the sqlservr.exe -c -m
3) restore the master database and restart the SQL Server service
4) restore the msdb database - be sure the SQLAgent service is not runnig
before you do so
5) restore model database if necessary
6) reconfigure your tempdb if necessary
7) restore all user databases and reconfigure if necessary - file locations
in particular
"zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
> Hello,
> Would anyone know or recommend/advise the easiest approach in bringing
> down and retiring an existing SQL2K running on W2K Server and brining it
> up with all of the data, jobs, etc. onto a newer server machine?
> Wondering if there was a way maybe do a full server restore from one of
> our server backup tapes instead of having to reinstall/reconfigure
> everything from scratch.
> Thanks in advance.
>|||Actually I personally am leaning more towards putting it on a w2k3 OS
instead of w2k but am concerned if there would be anything in w2k3 that
wouldn't support w2k as in the system files, ad/domain, etc? Like would you
happen to know if there were anything that was left out in w2k3 that was in
w2k?
Thanks a bunch for your quick and helpful reply. Much appreciated
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
> Imaging is one approach if you have an imaging software like StorageCraft
> or Acronis. But a main consideration here is hardware and configuration.
> The source and destination may have different disk configurations. Another
> considertation maybe to use Win2K3 instead of Win2K. If what you're
> intending to restore is simply SQL Server, just a backup of all system and
> user database would be enough and a very good restore process
> On the old SQL Server instance,
> 1) stop all applications accessing your SQL Server
> 2) backup all your system and user databases
> 3) identify the latest hotfix you have. This is necessary for you to
> restore on the new one
> On the new SQL Server instance,
> 1) Install SQL Server together with the service packs and hotfixes up to
> the one you have on the old instance
> 2) start SQL Server in single-user mode using the sqlservr.exe -c -m
> 3) restore the master database and restart the SQL Server service
> 4) restore the msdb database - be sure the SQLAgent service is not runnig
> before you do so
> 5) restore model database if necessary
> 6) reconfigure your tempdb if necessary
> 7) restore all user databases and reconfigure if necessary - file
> locations in particular
>
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
>|||Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just remember
to ignore the warning when you install SQL Server 2000 on a Win2K3 telling
you that you do not have SP3. Install the latest service pack after
installing SQL Server 2000
"zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
> Actually I personally am leaning more towards putting it on a w2k3 OS
> instead of w2k but am concerned if there would be anything in w2k3 that
> wouldn't support w2k as in the system files, ad/domain, etc? Like would
> you happen to know if there were anything that was left out in w2k3 that
> was in w2k?
> Thanks a bunch for your quick and helpful reply. Much appreciated
>
> "bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
> news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
>|||I guess 2 main things that come to mind on that w2k server is that I've
installed a certificate from an ms ca service (in use for network ssl 'Force
protocol encryption' SQL Server Network Utility) in which I can just do
another certificate request/install and some .dll's that a VB app uses but I
would think that these shouldn't be an issue in that w2k3 would definitely
continue to support these. Will look into it further. Thanks so much for
your speedy informative reply. Will greatly help out in clearing things up
and expediting my research
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:u$QuvTm3HHA.5724@.TK2MSFTNGP05.phx.gbl...
> Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just
> remember to ignore the warning when you install SQL Server 2000 on a
> Win2K3 telling you that you do not have SP3. Install the latest service
> pack after installing SQL Server 2000
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
>|||Sorry if I'm over analyzing this perhaps but I can't seem to visualize some
of the "X" factors like how to keep the same server name, domain and IP
address the same after rebuilding/restoring the master db onto the new
machine since this holds the domain logins/jobs. Are there any websites
that can layout it out step by step in retiring an old w2k-sql2k and restore
it onto a newer machine with w2k3-sql2k?
Thanks for your helpful replies bass_player.
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:u$QuvTm3HHA.5724@.TK2MSFTNGP05.phx.gbl...
> Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just
> remember to ignore the warning when you install SQL Server 2000 on a
> Win2K3 telling you that you do not have SP3. Install the latest service
> pack after installing SQL Server 2000
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
>
Would anyone know or recommend/advise the easiest approach in bringing down
and retiring an existing SQL2K running on W2K Server and brining it up with
all of the data, jobs, etc. onto a newer server machine? Wondering if there
was a way maybe do a full server restore from one of our server backup tapes
instead of having to reinstall/reconfigure everything from scratch.
Thanks in advance.Imaging is one approach if you have an imaging software like StorageCraft or
Acronis. But a main consideration here is hardware and configuration. The
source and destination may have different disk configurations. Another
considertation maybe to use Win2K3 instead of Win2K. If what you're
intending to restore is simply SQL Server, just a backup of all system and
user database would be enough and a very good restore process
On the old SQL Server instance,
1) stop all applications accessing your SQL Server
2) backup all your system and user databases
3) identify the latest hotfix you have. This is necessary for you to
restore on the new one
On the new SQL Server instance,
1) Install SQL Server together with the service packs and hotfixes up to the
one you have on the old instance
2) start SQL Server in single-user mode using the sqlservr.exe -c -m
3) restore the master database and restart the SQL Server service
4) restore the msdb database - be sure the SQLAgent service is not runnig
before you do so
5) restore model database if necessary
6) reconfigure your tempdb if necessary
7) restore all user databases and reconfigure if necessary - file locations
in particular
"zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
> Hello,
> Would anyone know or recommend/advise the easiest approach in bringing
> down and retiring an existing SQL2K running on W2K Server and brining it
> up with all of the data, jobs, etc. onto a newer server machine?
> Wondering if there was a way maybe do a full server restore from one of
> our server backup tapes instead of having to reinstall/reconfigure
> everything from scratch.
> Thanks in advance.
>|||Actually I personally am leaning more towards putting it on a w2k3 OS
instead of w2k but am concerned if there would be anything in w2k3 that
wouldn't support w2k as in the system files, ad/domain, etc? Like would you
happen to know if there were anything that was left out in w2k3 that was in
w2k?
Thanks a bunch for your quick and helpful reply. Much appreciated
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
> Imaging is one approach if you have an imaging software like StorageCraft
> or Acronis. But a main consideration here is hardware and configuration.
> The source and destination may have different disk configurations. Another
> considertation maybe to use Win2K3 instead of Win2K. If what you're
> intending to restore is simply SQL Server, just a backup of all system and
> user database would be enough and a very good restore process
> On the old SQL Server instance,
> 1) stop all applications accessing your SQL Server
> 2) backup all your system and user databases
> 3) identify the latest hotfix you have. This is necessary for you to
> restore on the new one
> On the new SQL Server instance,
> 1) Install SQL Server together with the service packs and hotfixes up to
> the one you have on the old instance
> 2) start SQL Server in single-user mode using the sqlservr.exe -c -m
> 3) restore the master database and restart the SQL Server service
> 4) restore the msdb database - be sure the SQLAgent service is not runnig
> before you do so
> 5) restore model database if necessary
> 6) reconfigure your tempdb if necessary
> 7) restore all user databases and reconfigure if necessary - file
> locations in particular
>
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
>|||Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just remember
to ignore the warning when you install SQL Server 2000 on a Win2K3 telling
you that you do not have SP3. Install the latest service pack after
installing SQL Server 2000
"zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
> Actually I personally am leaning more towards putting it on a w2k3 OS
> instead of w2k but am concerned if there would be anything in w2k3 that
> wouldn't support w2k as in the system files, ad/domain, etc? Like would
> you happen to know if there were anything that was left out in w2k3 that
> was in w2k?
> Thanks a bunch for your quick and helpful reply. Much appreciated
>
> "bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
> news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
>|||I guess 2 main things that come to mind on that w2k server is that I've
installed a certificate from an ms ca service (in use for network ssl 'Force
protocol encryption' SQL Server Network Utility) in which I can just do
another certificate request/install and some .dll's that a VB app uses but I
would think that these shouldn't be an issue in that w2k3 would definitely
continue to support these. Will look into it further. Thanks so much for
your speedy informative reply. Will greatly help out in clearing things up
and expediting my research
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:u$QuvTm3HHA.5724@.TK2MSFTNGP05.phx.gbl...
> Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just
> remember to ignore the warning when you install SQL Server 2000 on a
> Win2K3 telling you that you do not have SP3. Install the latest service
> pack after installing SQL Server 2000
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
>|||Sorry if I'm over analyzing this perhaps but I can't seem to visualize some
of the "X" factors like how to keep the same server name, domain and IP
address the same after rebuilding/restoring the master db onto the new
machine since this holds the domain logins/jobs. Are there any websites
that can layout it out step by step in retiring an old w2k-sql2k and restore
it onto a newer machine with w2k3-sql2k?
Thanks for your helpful replies bass_player.
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:u$QuvTm3HHA.5724@.TK2MSFTNGP05.phx.gbl...
> Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just
> remember to ignore the warning when you install SQL Server 2000 on a
> Win2K3 telling you that you do not have SP3. Install the latest service
> pack after installing SQL Server 2000
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
>
Restore SQL2K on different machine
Hello,
Would anyone know or recommend/advise the easiest approach in bringing down
and retiring an existing SQL2K running on W2K Server and brining it up with
all of the data, jobs, etc. onto a newer server machine? Wondering if there
was a way maybe do a full server restore from one of our server backup tapes
instead of having to reinstall/reconfigure everything from scratch.
Thanks in advance.
Imaging is one approach if you have an imaging software like StorageCraft or
Acronis. But a main consideration here is hardware and configuration. The
source and destination may have different disk configurations. Another
considertation maybe to use Win2K3 instead of Win2K. If what you're
intending to restore is simply SQL Server, just a backup of all system and
user database would be enough and a very good restore process
On the old SQL Server instance,
1) stop all applications accessing your SQL Server
2) backup all your system and user databases
3) identify the latest hotfix you have. This is necessary for you to
restore on the new one
On the new SQL Server instance,
1) Install SQL Server together with the service packs and hotfixes up to the
one you have on the old instance
2) start SQL Server in single-user mode using the sqlservr.exe -c -m
3) restore the master database and restart the SQL Server service
4) restore the msdb database - be sure the SQLAgent service is not runnig
before you do so
5) restore model database if necessary
6) reconfigure your tempdb if necessary
7) restore all user databases and reconfigure if necessary - file locations
in particular
"zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
> Hello,
> Would anyone know or recommend/advise the easiest approach in bringing
> down and retiring an existing SQL2K running on W2K Server and brining it
> up with all of the data, jobs, etc. onto a newer server machine?
> Wondering if there was a way maybe do a full server restore from one of
> our server backup tapes instead of having to reinstall/reconfigure
> everything from scratch.
> Thanks in advance.
>
|||Actually I personally am leaning more towards putting it on a w2k3 OS
instead of w2k but am concerned if there would be anything in w2k3 that
wouldn't support w2k as in the system files, ad/domain, etc? Like would you
happen to know if there were anything that was left out in w2k3 that was in
w2k?
Thanks a bunch for your quick and helpful reply. Much appreciated
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
> Imaging is one approach if you have an imaging software like StorageCraft
> or Acronis. But a main consideration here is hardware and configuration.
> The source and destination may have different disk configurations. Another
> considertation maybe to use Win2K3 instead of Win2K. If what you're
> intending to restore is simply SQL Server, just a backup of all system and
> user database would be enough and a very good restore process
> On the old SQL Server instance,
> 1) stop all applications accessing your SQL Server
> 2) backup all your system and user databases
> 3) identify the latest hotfix you have. This is necessary for you to
> restore on the new one
> On the new SQL Server instance,
> 1) Install SQL Server together with the service packs and hotfixes up to
> the one you have on the old instance
> 2) start SQL Server in single-user mode using the sqlservr.exe -c -m
> 3) restore the master database and restart the SQL Server service
> 4) restore the msdb database - be sure the SQLAgent service is not runnig
> before you do so
> 5) restore model database if necessary
> 6) reconfigure your tempdb if necessary
> 7) restore all user databases and reconfigure if necessary - file
> locations in particular
>
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
>
|||Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just remember
to ignore the warning when you install SQL Server 2000 on a Win2K3 telling
you that you do not have SP3. Install the latest service pack after
installing SQL Server 2000
"zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
> Actually I personally am leaning more towards putting it on a w2k3 OS
> instead of w2k but am concerned if there would be anything in w2k3 that
> wouldn't support w2k as in the system files, ad/domain, etc? Like would
> you happen to know if there were anything that was left out in w2k3 that
> was in w2k?
> Thanks a bunch for your quick and helpful reply. Much appreciated
>
> "bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
> news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
>
|||I guess 2 main things that come to mind on that w2k server is that I've
installed a certificate from an ms ca service (in use for network ssl 'Force
protocol encryption' SQL Server Network Utility) in which I can just do
another certificate request/install and some .dll's that a VB app uses but I
would think that these shouldn't be an issue in that w2k3 would definitely
continue to support these. Will look into it further. Thanks so much for
your speedy informative reply. Will greatly help out in clearing things up
and expediting my research
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:u$QuvTm3HHA.5724@.TK2MSFTNGP05.phx.gbl...
> Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just
> remember to ignore the warning when you install SQL Server 2000 on a
> Win2K3 telling you that you do not have SP3. Install the latest service
> pack after installing SQL Server 2000
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
>
|||Sorry if I'm over analyzing this perhaps but I can't seem to visualize some
of the "X" factors like how to keep the same server name, domain and IP
address the same after rebuilding/restoring the master db onto the new
machine since this holds the domain logins/jobs. Are there any websites
that can layout it out step by step in retiring an old w2k-sql2k and restore
it onto a newer machine with w2k3-sql2k?
Thanks for your helpful replies bass_player.
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:u$QuvTm3HHA.5724@.TK2MSFTNGP05.phx.gbl...
> Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just
> remember to ignore the warning when you install SQL Server 2000 on a
> Win2K3 telling you that you do not have SP3. Install the latest service
> pack after installing SQL Server 2000
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
>
Would anyone know or recommend/advise the easiest approach in bringing down
and retiring an existing SQL2K running on W2K Server and brining it up with
all of the data, jobs, etc. onto a newer server machine? Wondering if there
was a way maybe do a full server restore from one of our server backup tapes
instead of having to reinstall/reconfigure everything from scratch.
Thanks in advance.
Imaging is one approach if you have an imaging software like StorageCraft or
Acronis. But a main consideration here is hardware and configuration. The
source and destination may have different disk configurations. Another
considertation maybe to use Win2K3 instead of Win2K. If what you're
intending to restore is simply SQL Server, just a backup of all system and
user database would be enough and a very good restore process
On the old SQL Server instance,
1) stop all applications accessing your SQL Server
2) backup all your system and user databases
3) identify the latest hotfix you have. This is necessary for you to
restore on the new one
On the new SQL Server instance,
1) Install SQL Server together with the service packs and hotfixes up to the
one you have on the old instance
2) start SQL Server in single-user mode using the sqlservr.exe -c -m
3) restore the master database and restart the SQL Server service
4) restore the msdb database - be sure the SQLAgent service is not runnig
before you do so
5) restore model database if necessary
6) reconfigure your tempdb if necessary
7) restore all user databases and reconfigure if necessary - file locations
in particular
"zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
> Hello,
> Would anyone know or recommend/advise the easiest approach in bringing
> down and retiring an existing SQL2K running on W2K Server and brining it
> up with all of the data, jobs, etc. onto a newer server machine?
> Wondering if there was a way maybe do a full server restore from one of
> our server backup tapes instead of having to reinstall/reconfigure
> everything from scratch.
> Thanks in advance.
>
|||Actually I personally am leaning more towards putting it on a w2k3 OS
instead of w2k but am concerned if there would be anything in w2k3 that
wouldn't support w2k as in the system files, ad/domain, etc? Like would you
happen to know if there were anything that was left out in w2k3 that was in
w2k?
Thanks a bunch for your quick and helpful reply. Much appreciated
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
> Imaging is one approach if you have an imaging software like StorageCraft
> or Acronis. But a main consideration here is hardware and configuration.
> The source and destination may have different disk configurations. Another
> considertation maybe to use Win2K3 instead of Win2K. If what you're
> intending to restore is simply SQL Server, just a backup of all system and
> user database would be enough and a very good restore process
> On the old SQL Server instance,
> 1) stop all applications accessing your SQL Server
> 2) backup all your system and user databases
> 3) identify the latest hotfix you have. This is necessary for you to
> restore on the new one
> On the new SQL Server instance,
> 1) Install SQL Server together with the service packs and hotfixes up to
> the one you have on the old instance
> 2) start SQL Server in single-user mode using the sqlservr.exe -c -m
> 3) restore the master database and restart the SQL Server service
> 4) restore the msdb database - be sure the SQLAgent service is not runnig
> before you do so
> 5) restore model database if necessary
> 6) reconfigure your tempdb if necessary
> 7) restore all user databases and reconfigure if necessary - file
> locations in particular
>
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
>
|||Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just remember
to ignore the warning when you install SQL Server 2000 on a Win2K3 telling
you that you do not have SP3. Install the latest service pack after
installing SQL Server 2000
"zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
> Actually I personally am leaning more towards putting it on a w2k3 OS
> instead of w2k but am concerned if there would be anything in w2k3 that
> wouldn't support w2k as in the system files, ad/domain, etc? Like would
> you happen to know if there were anything that was left out in w2k3 that
> was in w2k?
> Thanks a bunch for your quick and helpful reply. Much appreciated
>
> "bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
> news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
>
|||I guess 2 main things that come to mind on that w2k server is that I've
installed a certificate from an ms ca service (in use for network ssl 'Force
protocol encryption' SQL Server Network Utility) in which I can just do
another certificate request/install and some .dll's that a VB app uses but I
would think that these shouldn't be an issue in that w2k3 would definitely
continue to support these. Will look into it further. Thanks so much for
your speedy informative reply. Will greatly help out in clearing things up
and expediting my research
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:u$QuvTm3HHA.5724@.TK2MSFTNGP05.phx.gbl...
> Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just
> remember to ignore the warning when you install SQL Server 2000 on a
> Win2K3 telling you that you do not have SP3. Install the latest service
> pack after installing SQL Server 2000
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
>
|||Sorry if I'm over analyzing this perhaps but I can't seem to visualize some
of the "X" factors like how to keep the same server name, domain and IP
address the same after rebuilding/restoring the master db onto the new
machine since this holds the domain logins/jobs. Are there any websites
that can layout it out step by step in retiring an old w2k-sql2k and restore
it onto a newer machine with w2k3-sql2k?
Thanks for your helpful replies bass_player.
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:u$QuvTm3HHA.5724@.TK2MSFTNGP05.phx.gbl...
> Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just
> remember to ignore the warning when you install SQL Server 2000 on a
> Win2K3 telling you that you do not have SP3. Install the latest service
> pack after installing SQL Server 2000
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
>
Restore SQL2K on different machine
Hello,
Would anyone know or recommend/advise the easiest approach in bringing down
and retiring an existing SQL2K running on W2K Server and brining it up with
all of the data, jobs, etc. onto a newer server machine? Wondering if there
was a way maybe do a full server restore from one of our server backup tapes
instead of having to reinstall/reconfigure everything from scratch.
Thanks in advance.Imaging is one approach if you have an imaging software like StorageCraft or
Acronis. But a main consideration here is hardware and configuration. The
source and destination may have different disk configurations. Another
considertation maybe to use Win2K3 instead of Win2K. If what you're
intending to restore is simply SQL Server, just a backup of all system and
user database would be enough and a very good restore process
On the old SQL Server instance,
1) stop all applications accessing your SQL Server
2) backup all your system and user databases
3) identify the latest hotfix you have. This is necessary for you to
restore on the new one
On the new SQL Server instance,
1) Install SQL Server together with the service packs and hotfixes up to the
one you have on the old instance
2) start SQL Server in single-user mode using the sqlservr.exe -c -m
3) restore the master database and restart the SQL Server service
4) restore the msdb database - be sure the SQLAgent service is not runnig
before you do so
5) restore model database if necessary
6) reconfigure your tempdb if necessary
7) restore all user databases and reconfigure if necessary - file locations
in particular
"zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
> Hello,
> Would anyone know or recommend/advise the easiest approach in bringing
> down and retiring an existing SQL2K running on W2K Server and brining it
> up with all of the data, jobs, etc. onto a newer server machine?
> Wondering if there was a way maybe do a full server restore from one of
> our server backup tapes instead of having to reinstall/reconfigure
> everything from scratch.
> Thanks in advance.
>|||Actually I personally am leaning more towards putting it on a w2k3 OS
instead of w2k but am concerned if there would be anything in w2k3 that
wouldn't support w2k as in the system files, ad/domain, etc? Like would you
happen to know if there were anything that was left out in w2k3 that was in
w2k?
Thanks a bunch for your quick and helpful reply. Much appreciated :)
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
> Imaging is one approach if you have an imaging software like StorageCraft
> or Acronis. But a main consideration here is hardware and configuration.
> The source and destination may have different disk configurations. Another
> considertation maybe to use Win2K3 instead of Win2K. If what you're
> intending to restore is simply SQL Server, just a backup of all system and
> user database would be enough and a very good restore process
> On the old SQL Server instance,
> 1) stop all applications accessing your SQL Server
> 2) backup all your system and user databases
> 3) identify the latest hotfix you have. This is necessary for you to
> restore on the new one
> On the new SQL Server instance,
> 1) Install SQL Server together with the service packs and hotfixes up to
> the one you have on the old instance
> 2) start SQL Server in single-user mode using the sqlservr.exe -c -m
> 3) restore the master database and restart the SQL Server service
> 4) restore the msdb database - be sure the SQLAgent service is not runnig
> before you do so
> 5) restore model database if necessary
> 6) reconfigure your tempdb if necessary
> 7) restore all user databases and reconfigure if necessary - file
> locations in particular
>
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
>> Hello,
>> Would anyone know or recommend/advise the easiest approach in bringing
>> down and retiring an existing SQL2K running on W2K Server and brining it
>> up with all of the data, jobs, etc. onto a newer server machine?
>> Wondering if there was a way maybe do a full server restore from one of
>> our server backup tapes instead of having to reinstall/reconfigure
>> everything from scratch.
>> Thanks in advance.
>|||Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just remember
to ignore the warning when you install SQL Server 2000 on a Win2K3 telling
you that you do not have SP3. Install the latest service pack after
installing SQL Server 2000
"zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
> Actually I personally am leaning more towards putting it on a w2k3 OS
> instead of w2k but am concerned if there would be anything in w2k3 that
> wouldn't support w2k as in the system files, ad/domain, etc? Like would
> you happen to know if there were anything that was left out in w2k3 that
> was in w2k?
> Thanks a bunch for your quick and helpful reply. Much appreciated :)
>
> "bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
> news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
>> Imaging is one approach if you have an imaging software like StorageCraft
>> or Acronis. But a main consideration here is hardware and configuration.
>> The source and destination may have different disk configurations.
>> Another considertation maybe to use Win2K3 instead of Win2K. If what
>> you're intending to restore is simply SQL Server, just a backup of all
>> system and user database would be enough and a very good restore process
>> On the old SQL Server instance,
>> 1) stop all applications accessing your SQL Server
>> 2) backup all your system and user databases
>> 3) identify the latest hotfix you have. This is necessary for you to
>> restore on the new one
>> On the new SQL Server instance,
>> 1) Install SQL Server together with the service packs and hotfixes up to
>> the one you have on the old instance
>> 2) start SQL Server in single-user mode using the sqlservr.exe -c -m
>> 3) restore the master database and restart the SQL Server service
>> 4) restore the msdb database - be sure the SQLAgent service is not runnig
>> before you do so
>> 5) restore model database if necessary
>> 6) reconfigure your tempdb if necessary
>> 7) restore all user databases and reconfigure if necessary - file
>> locations in particular
>>
>> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
>> news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
>> Hello,
>> Would anyone know or recommend/advise the easiest approach in bringing
>> down and retiring an existing SQL2K running on W2K Server and brining it
>> up with all of the data, jobs, etc. onto a newer server machine?
>> Wondering if there was a way maybe do a full server restore from one of
>> our server backup tapes instead of having to reinstall/reconfigure
>> everything from scratch.
>> Thanks in advance.
>>
>|||I guess 2 main things that come to mind on that w2k server is that I've
installed a certificate from an ms ca service (in use for network ssl 'Force
protocol encryption' SQL Server Network Utility) in which I can just do
another certificate request/install and some .dll's that a VB app uses but I
would think that these shouldn't be an issue in that w2k3 would definitely
continue to support these. Will look into it further. Thanks so much for
your speedy informative reply. Will greatly help out in clearing things up
and expediting my research :)
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:u$QuvTm3HHA.5724@.TK2MSFTNGP05.phx.gbl...
> Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just
> remember to ignore the warning when you install SQL Server 2000 on a
> Win2K3 telling you that you do not have SP3. Install the latest service
> pack after installing SQL Server 2000
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
>> Actually I personally am leaning more towards putting it on a w2k3 OS
>> instead of w2k but am concerned if there would be anything in w2k3 that
>> wouldn't support w2k as in the system files, ad/domain, etc? Like would
>> you happen to know if there were anything that was left out in w2k3 that
>> was in w2k?
>> Thanks a bunch for your quick and helpful reply. Much appreciated :)
>>
>> "bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
>> news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
>> Imaging is one approach if you have an imaging software like
>> StorageCraft or Acronis. But a main consideration here is hardware and
>> configuration. The source and destination may have different disk
>> configurations. Another considertation maybe to use Win2K3 instead of
>> Win2K. If what you're intending to restore is simply SQL Server, just a
>> backup of all system and user database would be enough and a very good
>> restore process
>> On the old SQL Server instance,
>> 1) stop all applications accessing your SQL Server
>> 2) backup all your system and user databases
>> 3) identify the latest hotfix you have. This is necessary for you to
>> restore on the new one
>> On the new SQL Server instance,
>> 1) Install SQL Server together with the service packs and hotfixes up to
>> the one you have on the old instance
>> 2) start SQL Server in single-user mode using the sqlservr.exe -c -m
>> 3) restore the master database and restart the SQL Server service
>> 4) restore the msdb database - be sure the SQLAgent service is not
>> runnig before you do so
>> 5) restore model database if necessary
>> 6) reconfigure your tempdb if necessary
>> 7) restore all user databases and reconfigure if necessary - file
>> locations in particular
>>
>> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
>> news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
>> Hello,
>> Would anyone know or recommend/advise the easiest approach in bringing
>> down and retiring an existing SQL2K running on W2K Server and brining
>> it up with all of the data, jobs, etc. onto a newer server machine?
>> Wondering if there was a way maybe do a full server restore from one of
>> our server backup tapes instead of having to reinstall/reconfigure
>> everything from scratch.
>> Thanks in advance.
>>
>>
>|||Sorry if I'm over analyzing this perhaps but I can't seem to visualize some
of the "X" factors like how to keep the same server name, domain and IP
address the same after rebuilding/restoring the master db onto the new
machine since this holds the domain logins/jobs. Are there any websites
that can layout it out step by step in retiring an old w2k-sql2k and restore
it onto a newer machine with w2k3-sql2k?
Thanks for your helpful replies bass_player.
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:u$QuvTm3HHA.5724@.TK2MSFTNGP05.phx.gbl...
> Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just
> remember to ignore the warning when you install SQL Server 2000 on a
> Win2K3 telling you that you do not have SP3. Install the latest service
> pack after installing SQL Server 2000
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
>> Actually I personally am leaning more towards putting it on a w2k3 OS
>> instead of w2k but am concerned if there would be anything in w2k3 that
>> wouldn't support w2k as in the system files, ad/domain, etc? Like would
>> you happen to know if there were anything that was left out in w2k3 that
>> was in w2k?
>> Thanks a bunch for your quick and helpful reply. Much appreciated :)
>>
>> "bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
>> news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
>> Imaging is one approach if you have an imaging software like
>> StorageCraft or Acronis. But a main consideration here is hardware and
>> configuration. The source and destination may have different disk
>> configurations. Another considertation maybe to use Win2K3 instead of
>> Win2K. If what you're intending to restore is simply SQL Server, just a
>> backup of all system and user database would be enough and a very good
>> restore process
>> On the old SQL Server instance,
>> 1) stop all applications accessing your SQL Server
>> 2) backup all your system and user databases
>> 3) identify the latest hotfix you have. This is necessary for you to
>> restore on the new one
>> On the new SQL Server instance,
>> 1) Install SQL Server together with the service packs and hotfixes up to
>> the one you have on the old instance
>> 2) start SQL Server in single-user mode using the sqlservr.exe -c -m
>> 3) restore the master database and restart the SQL Server service
>> 4) restore the msdb database - be sure the SQLAgent service is not
>> runnig before you do so
>> 5) restore model database if necessary
>> 6) reconfigure your tempdb if necessary
>> 7) restore all user databases and reconfigure if necessary - file
>> locations in particular
>>
>> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
>> news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
>> Hello,
>> Would anyone know or recommend/advise the easiest approach in bringing
>> down and retiring an existing SQL2K running on W2K Server and brining
>> it up with all of the data, jobs, etc. onto a newer server machine?
>> Wondering if there was a way maybe do a full server restore from one of
>> our server backup tapes instead of having to reinstall/reconfigure
>> everything from scratch.
>> Thanks in advance.
>>
>>
>|||Just a quick question in that did you mean w2k3 SP2 instead of SP3? My
coworker the network admin had w2k3 SP1 currently installed on our new
server and was wondering if he should go ahead and install SP2 which then
I'll install the sql2k or should I install sql2k first and then let him
install w2k3 SP2 and the rest of the windows updates?
Thanks again bass_player.
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:u$QuvTm3HHA.5724@.TK2MSFTNGP05.phx.gbl...
> Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just
> remember to ignore the warning when you install SQL Server 2000 on a
> Win2K3 telling you that you do not have SP3. Install the latest service
> pack after installing SQL Server 2000
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
>> Actually I personally am leaning more towards putting it on a w2k3 OS
>> instead of w2k but am concerned if there would be anything in w2k3 that
>> wouldn't support w2k as in the system files, ad/domain, etc? Like would
>> you happen to know if there were anything that was left out in w2k3 that
>> was in w2k?
>> Thanks a bunch for your quick and helpful reply. Much appreciated :)
>>
>> "bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
>> news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
>> Imaging is one approach if you have an imaging software like
>> StorageCraft or Acronis. But a main consideration here is hardware and
>> configuration. The source and destination may have different disk
>> configurations. Another considertation maybe to use Win2K3 instead of
>> Win2K. If what you're intending to restore is simply SQL Server, just a
>> backup of all system and user database would be enough and a very good
>> restore process
>> On the old SQL Server instance,
>> 1) stop all applications accessing your SQL Server
>> 2) backup all your system and user databases
>> 3) identify the latest hotfix you have. This is necessary for you to
>> restore on the new one
>> On the new SQL Server instance,
>> 1) Install SQL Server together with the service packs and hotfixes up to
>> the one you have on the old instance
>> 2) start SQL Server in single-user mode using the sqlservr.exe -c -m
>> 3) restore the master database and restart the SQL Server service
>> 4) restore the msdb database - be sure the SQLAgent service is not
>> runnig before you do so
>> 5) restore model database if necessary
>> 6) reconfigure your tempdb if necessary
>> 7) restore all user databases and reconfigure if necessary - file
>> locations in particular
>>
>> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
>> news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
>> Hello,
>> Would anyone know or recommend/advise the easiest approach in bringing
>> down and retiring an existing SQL2K running on W2K Server and brining
>> it up with all of the data, jobs, etc. onto a newer server machine?
>> Wondering if there was a way maybe do a full server restore from one of
>> our server backup tapes instead of having to reinstall/reconfigure
>> everything from scratch.
>> Thanks in advance.
>>
>>
>sql
Would anyone know or recommend/advise the easiest approach in bringing down
and retiring an existing SQL2K running on W2K Server and brining it up with
all of the data, jobs, etc. onto a newer server machine? Wondering if there
was a way maybe do a full server restore from one of our server backup tapes
instead of having to reinstall/reconfigure everything from scratch.
Thanks in advance.Imaging is one approach if you have an imaging software like StorageCraft or
Acronis. But a main consideration here is hardware and configuration. The
source and destination may have different disk configurations. Another
considertation maybe to use Win2K3 instead of Win2K. If what you're
intending to restore is simply SQL Server, just a backup of all system and
user database would be enough and a very good restore process
On the old SQL Server instance,
1) stop all applications accessing your SQL Server
2) backup all your system and user databases
3) identify the latest hotfix you have. This is necessary for you to
restore on the new one
On the new SQL Server instance,
1) Install SQL Server together with the service packs and hotfixes up to the
one you have on the old instance
2) start SQL Server in single-user mode using the sqlservr.exe -c -m
3) restore the master database and restart the SQL Server service
4) restore the msdb database - be sure the SQLAgent service is not runnig
before you do so
5) restore model database if necessary
6) reconfigure your tempdb if necessary
7) restore all user databases and reconfigure if necessary - file locations
in particular
"zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
> Hello,
> Would anyone know or recommend/advise the easiest approach in bringing
> down and retiring an existing SQL2K running on W2K Server and brining it
> up with all of the data, jobs, etc. onto a newer server machine?
> Wondering if there was a way maybe do a full server restore from one of
> our server backup tapes instead of having to reinstall/reconfigure
> everything from scratch.
> Thanks in advance.
>|||Actually I personally am leaning more towards putting it on a w2k3 OS
instead of w2k but am concerned if there would be anything in w2k3 that
wouldn't support w2k as in the system files, ad/domain, etc? Like would you
happen to know if there were anything that was left out in w2k3 that was in
w2k?
Thanks a bunch for your quick and helpful reply. Much appreciated :)
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
> Imaging is one approach if you have an imaging software like StorageCraft
> or Acronis. But a main consideration here is hardware and configuration.
> The source and destination may have different disk configurations. Another
> considertation maybe to use Win2K3 instead of Win2K. If what you're
> intending to restore is simply SQL Server, just a backup of all system and
> user database would be enough and a very good restore process
> On the old SQL Server instance,
> 1) stop all applications accessing your SQL Server
> 2) backup all your system and user databases
> 3) identify the latest hotfix you have. This is necessary for you to
> restore on the new one
> On the new SQL Server instance,
> 1) Install SQL Server together with the service packs and hotfixes up to
> the one you have on the old instance
> 2) start SQL Server in single-user mode using the sqlservr.exe -c -m
> 3) restore the master database and restart the SQL Server service
> 4) restore the msdb database - be sure the SQLAgent service is not runnig
> before you do so
> 5) restore model database if necessary
> 6) reconfigure your tempdb if necessary
> 7) restore all user databases and reconfigure if necessary - file
> locations in particular
>
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
>> Hello,
>> Would anyone know or recommend/advise the easiest approach in bringing
>> down and retiring an existing SQL2K running on W2K Server and brining it
>> up with all of the data, jobs, etc. onto a newer server machine?
>> Wondering if there was a way maybe do a full server restore from one of
>> our server backup tapes instead of having to reinstall/reconfigure
>> everything from scratch.
>> Thanks in advance.
>|||Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just remember
to ignore the warning when you install SQL Server 2000 on a Win2K3 telling
you that you do not have SP3. Install the latest service pack after
installing SQL Server 2000
"zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
> Actually I personally am leaning more towards putting it on a w2k3 OS
> instead of w2k but am concerned if there would be anything in w2k3 that
> wouldn't support w2k as in the system files, ad/domain, etc? Like would
> you happen to know if there were anything that was left out in w2k3 that
> was in w2k?
> Thanks a bunch for your quick and helpful reply. Much appreciated :)
>
> "bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
> news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
>> Imaging is one approach if you have an imaging software like StorageCraft
>> or Acronis. But a main consideration here is hardware and configuration.
>> The source and destination may have different disk configurations.
>> Another considertation maybe to use Win2K3 instead of Win2K. If what
>> you're intending to restore is simply SQL Server, just a backup of all
>> system and user database would be enough and a very good restore process
>> On the old SQL Server instance,
>> 1) stop all applications accessing your SQL Server
>> 2) backup all your system and user databases
>> 3) identify the latest hotfix you have. This is necessary for you to
>> restore on the new one
>> On the new SQL Server instance,
>> 1) Install SQL Server together with the service packs and hotfixes up to
>> the one you have on the old instance
>> 2) start SQL Server in single-user mode using the sqlservr.exe -c -m
>> 3) restore the master database and restart the SQL Server service
>> 4) restore the msdb database - be sure the SQLAgent service is not runnig
>> before you do so
>> 5) restore model database if necessary
>> 6) reconfigure your tempdb if necessary
>> 7) restore all user databases and reconfigure if necessary - file
>> locations in particular
>>
>> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
>> news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
>> Hello,
>> Would anyone know or recommend/advise the easiest approach in bringing
>> down and retiring an existing SQL2K running on W2K Server and brining it
>> up with all of the data, jobs, etc. onto a newer server machine?
>> Wondering if there was a way maybe do a full server restore from one of
>> our server backup tapes instead of having to reinstall/reconfigure
>> everything from scratch.
>> Thanks in advance.
>>
>|||I guess 2 main things that come to mind on that w2k server is that I've
installed a certificate from an ms ca service (in use for network ssl 'Force
protocol encryption' SQL Server Network Utility) in which I can just do
another certificate request/install and some .dll's that a VB app uses but I
would think that these shouldn't be an issue in that w2k3 would definitely
continue to support these. Will look into it further. Thanks so much for
your speedy informative reply. Will greatly help out in clearing things up
and expediting my research :)
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:u$QuvTm3HHA.5724@.TK2MSFTNGP05.phx.gbl...
> Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just
> remember to ignore the warning when you install SQL Server 2000 on a
> Win2K3 telling you that you do not have SP3. Install the latest service
> pack after installing SQL Server 2000
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
>> Actually I personally am leaning more towards putting it on a w2k3 OS
>> instead of w2k but am concerned if there would be anything in w2k3 that
>> wouldn't support w2k as in the system files, ad/domain, etc? Like would
>> you happen to know if there were anything that was left out in w2k3 that
>> was in w2k?
>> Thanks a bunch for your quick and helpful reply. Much appreciated :)
>>
>> "bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
>> news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
>> Imaging is one approach if you have an imaging software like
>> StorageCraft or Acronis. But a main consideration here is hardware and
>> configuration. The source and destination may have different disk
>> configurations. Another considertation maybe to use Win2K3 instead of
>> Win2K. If what you're intending to restore is simply SQL Server, just a
>> backup of all system and user database would be enough and a very good
>> restore process
>> On the old SQL Server instance,
>> 1) stop all applications accessing your SQL Server
>> 2) backup all your system and user databases
>> 3) identify the latest hotfix you have. This is necessary for you to
>> restore on the new one
>> On the new SQL Server instance,
>> 1) Install SQL Server together with the service packs and hotfixes up to
>> the one you have on the old instance
>> 2) start SQL Server in single-user mode using the sqlservr.exe -c -m
>> 3) restore the master database and restart the SQL Server service
>> 4) restore the msdb database - be sure the SQLAgent service is not
>> runnig before you do so
>> 5) restore model database if necessary
>> 6) reconfigure your tempdb if necessary
>> 7) restore all user databases and reconfigure if necessary - file
>> locations in particular
>>
>> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
>> news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
>> Hello,
>> Would anyone know or recommend/advise the easiest approach in bringing
>> down and retiring an existing SQL2K running on W2K Server and brining
>> it up with all of the data, jobs, etc. onto a newer server machine?
>> Wondering if there was a way maybe do a full server restore from one of
>> our server backup tapes instead of having to reinstall/reconfigure
>> everything from scratch.
>> Thanks in advance.
>>
>>
>|||Sorry if I'm over analyzing this perhaps but I can't seem to visualize some
of the "X" factors like how to keep the same server name, domain and IP
address the same after rebuilding/restoring the master db onto the new
machine since this holds the domain logins/jobs. Are there any websites
that can layout it out step by step in retiring an old w2k-sql2k and restore
it onto a newer machine with w2k3-sql2k?
Thanks for your helpful replies bass_player.
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:u$QuvTm3HHA.5724@.TK2MSFTNGP05.phx.gbl...
> Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just
> remember to ignore the warning when you install SQL Server 2000 on a
> Win2K3 telling you that you do not have SP3. Install the latest service
> pack after installing SQL Server 2000
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
>> Actually I personally am leaning more towards putting it on a w2k3 OS
>> instead of w2k but am concerned if there would be anything in w2k3 that
>> wouldn't support w2k as in the system files, ad/domain, etc? Like would
>> you happen to know if there were anything that was left out in w2k3 that
>> was in w2k?
>> Thanks a bunch for your quick and helpful reply. Much appreciated :)
>>
>> "bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
>> news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
>> Imaging is one approach if you have an imaging software like
>> StorageCraft or Acronis. But a main consideration here is hardware and
>> configuration. The source and destination may have different disk
>> configurations. Another considertation maybe to use Win2K3 instead of
>> Win2K. If what you're intending to restore is simply SQL Server, just a
>> backup of all system and user database would be enough and a very good
>> restore process
>> On the old SQL Server instance,
>> 1) stop all applications accessing your SQL Server
>> 2) backup all your system and user databases
>> 3) identify the latest hotfix you have. This is necessary for you to
>> restore on the new one
>> On the new SQL Server instance,
>> 1) Install SQL Server together with the service packs and hotfixes up to
>> the one you have on the old instance
>> 2) start SQL Server in single-user mode using the sqlservr.exe -c -m
>> 3) restore the master database and restart the SQL Server service
>> 4) restore the msdb database - be sure the SQLAgent service is not
>> runnig before you do so
>> 5) restore model database if necessary
>> 6) reconfigure your tempdb if necessary
>> 7) restore all user databases and reconfigure if necessary - file
>> locations in particular
>>
>> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
>> news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
>> Hello,
>> Would anyone know or recommend/advise the easiest approach in bringing
>> down and retiring an existing SQL2K running on W2K Server and brining
>> it up with all of the data, jobs, etc. onto a newer server machine?
>> Wondering if there was a way maybe do a full server restore from one of
>> our server backup tapes instead of having to reinstall/reconfigure
>> everything from scratch.
>> Thanks in advance.
>>
>>
>|||Just a quick question in that did you mean w2k3 SP2 instead of SP3? My
coworker the network admin had w2k3 SP1 currently installed on our new
server and was wondering if he should go ahead and install SP2 which then
I'll install the sql2k or should I install sql2k first and then let him
install w2k3 SP2 and the rest of the windows updates?
Thanks again bass_player.
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:u$QuvTm3HHA.5724@.TK2MSFTNGP05.phx.gbl...
> Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just
> remember to ignore the warning when you install SQL Server 2000 on a
> Win2K3 telling you that you do not have SP3. Install the latest service
> pack after installing SQL Server 2000
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
>> Actually I personally am leaning more towards putting it on a w2k3 OS
>> instead of w2k but am concerned if there would be anything in w2k3 that
>> wouldn't support w2k as in the system files, ad/domain, etc? Like would
>> you happen to know if there were anything that was left out in w2k3 that
>> was in w2k?
>> Thanks a bunch for your quick and helpful reply. Much appreciated :)
>>
>> "bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
>> news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
>> Imaging is one approach if you have an imaging software like
>> StorageCraft or Acronis. But a main consideration here is hardware and
>> configuration. The source and destination may have different disk
>> configurations. Another considertation maybe to use Win2K3 instead of
>> Win2K. If what you're intending to restore is simply SQL Server, just a
>> backup of all system and user database would be enough and a very good
>> restore process
>> On the old SQL Server instance,
>> 1) stop all applications accessing your SQL Server
>> 2) backup all your system and user databases
>> 3) identify the latest hotfix you have. This is necessary for you to
>> restore on the new one
>> On the new SQL Server instance,
>> 1) Install SQL Server together with the service packs and hotfixes up to
>> the one you have on the old instance
>> 2) start SQL Server in single-user mode using the sqlservr.exe -c -m
>> 3) restore the master database and restart the SQL Server service
>> 4) restore the msdb database - be sure the SQLAgent service is not
>> runnig before you do so
>> 5) restore model database if necessary
>> 6) reconfigure your tempdb if necessary
>> 7) restore all user databases and reconfigure if necessary - file
>> locations in particular
>>
>> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
>> news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
>> Hello,
>> Would anyone know or recommend/advise the easiest approach in bringing
>> down and retiring an existing SQL2K running on W2K Server and brining
>> it up with all of the data, jobs, etc. onto a newer server machine?
>> Wondering if there was a way maybe do a full server restore from one of
>> our server backup tapes instead of having to reinstall/reconfigure
>> everything from scratch.
>> Thanks in advance.
>>
>>
>sql
Wednesday, March 21, 2012
Restore SQL 7 Database to SQL 2000 (urgent)
I have a 225Gb SQL 7 database on an NT 4 server that I need to restore to a
Win2k Server running SQL 2000. Is it possible to restore a SQL 7 database
onto a SQL 2000 server?
GavHi,
You can backup the SQL 7 database and restore it in SQL 2000. Do a update
statistics after the restore to get the effective performance.
Thanks
Hari
MCDBA
"Gavin Metcalfe" <gavin.metcalfe@.btinternet.com> wrote in message
news:c6t40b$s74$1@.titan.btinternet.com...
> I have a 225Gb SQL 7 database on an NT 4 server that I need to restore to
a
> Win2k Server running SQL 2000. Is it possible to restore a SQL 7 database
> onto a SQL 2000 server?
> Gav
>|||thanks for that. :o)
"Hari" <hari_prasad_k@.hotmail.com> wrote in message
news:OF$DsLpLEHA.2500@.TK2MSFTNGP12.phx.gbl...
> Hi,
> You can backup the SQL 7 database and restore it in SQL 2000. Do a update
> statistics after the restore to get the effective performance.
> Thanks
> Hari
> MCDBA
> "Gavin Metcalfe" <gavin.metcalfe@.btinternet.com> wrote in message
> news:c6t40b$s74$1@.titan.btinternet.com...
to[vbcol=seagreen]
> a
database[vbcol=seagreen]
>sql
Win2k Server running SQL 2000. Is it possible to restore a SQL 7 database
onto a SQL 2000 server?
GavHi,
You can backup the SQL 7 database and restore it in SQL 2000. Do a update
statistics after the restore to get the effective performance.
Thanks
Hari
MCDBA
"Gavin Metcalfe" <gavin.metcalfe@.btinternet.com> wrote in message
news:c6t40b$s74$1@.titan.btinternet.com...
> I have a 225Gb SQL 7 database on an NT 4 server that I need to restore to
a
> Win2k Server running SQL 2000. Is it possible to restore a SQL 7 database
> onto a SQL 2000 server?
> Gav
>|||thanks for that. :o)
"Hari" <hari_prasad_k@.hotmail.com> wrote in message
news:OF$DsLpLEHA.2500@.TK2MSFTNGP12.phx.gbl...
> Hi,
> You can backup the SQL 7 database and restore it in SQL 2000. Do a update
> statistics after the restore to get the effective performance.
> Thanks
> Hari
> MCDBA
> "Gavin Metcalfe" <gavin.metcalfe@.btinternet.com> wrote in message
> news:c6t40b$s74$1@.titan.btinternet.com...
to[vbcol=seagreen]
> a
database[vbcol=seagreen]
>sql
Restore SQL 7 Database to SQL 2000 (urgent)
I have a 225Gb SQL 7 database on an NT 4 server that I need to restore to a
Win2k Server running SQL 2000. Is it possible to restore a SQL 7 database
onto a SQL 2000 server?
Gav
Hi,
You can backup the SQL 7 database and restore it in SQL 2000. Do a update
statistics after the restore to get the effective performance.
Thanks
Hari
MCDBA
"Gavin Metcalfe" <gavin.metcalfe@.btinternet.com> wrote in message
news:c6t40b$s74$1@.titan.btinternet.com...
> I have a 225Gb SQL 7 database on an NT 4 server that I need to restore to
a
> Win2k Server running SQL 2000. Is it possible to restore a SQL 7 database
> onto a SQL 2000 server?
> Gav
>
|||thanks for that. :o)
"Hari" <hari_prasad_k@.hotmail.com> wrote in message
news:OF$DsLpLEHA.2500@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> Hi,
> You can backup the SQL 7 database and restore it in SQL 2000. Do a update
> statistics after the restore to get the effective performance.
> Thanks
> Hari
> MCDBA
> "Gavin Metcalfe" <gavin.metcalfe@.btinternet.com> wrote in message
> news:c6t40b$s74$1@.titan.btinternet.com...
to[vbcol=seagreen]
> a
database
>
Win2k Server running SQL 2000. Is it possible to restore a SQL 7 database
onto a SQL 2000 server?
Gav
Hi,
You can backup the SQL 7 database and restore it in SQL 2000. Do a update
statistics after the restore to get the effective performance.
Thanks
Hari
MCDBA
"Gavin Metcalfe" <gavin.metcalfe@.btinternet.com> wrote in message
news:c6t40b$s74$1@.titan.btinternet.com...
> I have a 225Gb SQL 7 database on an NT 4 server that I need to restore to
a
> Win2k Server running SQL 2000. Is it possible to restore a SQL 7 database
> onto a SQL 2000 server?
> Gav
>
|||thanks for that. :o)
"Hari" <hari_prasad_k@.hotmail.com> wrote in message
news:OF$DsLpLEHA.2500@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> Hi,
> You can backup the SQL 7 database and restore it in SQL 2000. Do a update
> statistics after the restore to get the effective performance.
> Thanks
> Hari
> MCDBA
> "Gavin Metcalfe" <gavin.metcalfe@.btinternet.com> wrote in message
> news:c6t40b$s74$1@.titan.btinternet.com...
to[vbcol=seagreen]
> a
database
>
Restore SQL 7 Database to SQL 2000 (urgent)
I have a 225Gb SQL 7 database on an NT 4 server that I need to restore to a
Win2k Server running SQL 2000. Is it possible to restore a SQL 7 database
onto a SQL 2000 server?
GavHi,
You can backup the SQL 7 database and restore it in SQL 2000. Do a update
statistics after the restore to get the effective performance.
Thanks
Hari
MCDBA
"Gavin Metcalfe" <gavin.metcalfe@.btinternet.com> wrote in message
news:c6t40b$s74$1@.titan.btinternet.com...
> I have a 225Gb SQL 7 database on an NT 4 server that I need to restore to
a
> Win2k Server running SQL 2000. Is it possible to restore a SQL 7 database
> onto a SQL 2000 server?
> Gav
>|||thanks for that. :o)
"Hari" <hari_prasad_k@.hotmail.com> wrote in message
news:OF$DsLpLEHA.2500@.TK2MSFTNGP12.phx.gbl...
> Hi,
> You can backup the SQL 7 database and restore it in SQL 2000. Do a update
> statistics after the restore to get the effective performance.
> Thanks
> Hari
> MCDBA
> "Gavin Metcalfe" <gavin.metcalfe@.btinternet.com> wrote in message
> news:c6t40b$s74$1@.titan.btinternet.com...
> > I have a 225Gb SQL 7 database on an NT 4 server that I need to restore
to
> a
> > Win2k Server running SQL 2000. Is it possible to restore a SQL 7
database
> > onto a SQL 2000 server?
> >
> > Gav
> >
> >
>
Win2k Server running SQL 2000. Is it possible to restore a SQL 7 database
onto a SQL 2000 server?
GavHi,
You can backup the SQL 7 database and restore it in SQL 2000. Do a update
statistics after the restore to get the effective performance.
Thanks
Hari
MCDBA
"Gavin Metcalfe" <gavin.metcalfe@.btinternet.com> wrote in message
news:c6t40b$s74$1@.titan.btinternet.com...
> I have a 225Gb SQL 7 database on an NT 4 server that I need to restore to
a
> Win2k Server running SQL 2000. Is it possible to restore a SQL 7 database
> onto a SQL 2000 server?
> Gav
>|||thanks for that. :o)
"Hari" <hari_prasad_k@.hotmail.com> wrote in message
news:OF$DsLpLEHA.2500@.TK2MSFTNGP12.phx.gbl...
> Hi,
> You can backup the SQL 7 database and restore it in SQL 2000. Do a update
> statistics after the restore to get the effective performance.
> Thanks
> Hari
> MCDBA
> "Gavin Metcalfe" <gavin.metcalfe@.btinternet.com> wrote in message
> news:c6t40b$s74$1@.titan.btinternet.com...
> > I have a 225Gb SQL 7 database on an NT 4 server that I need to restore
to
> a
> > Win2k Server running SQL 2000. Is it possible to restore a SQL 7
database
> > onto a SQL 2000 server?
> >
> > Gav
> >
> >
>
Tuesday, March 20, 2012
Restore readonly filegroup sqlserver 2000
Hi,
I have a database running on sqlserver 2000. This database (let's call it TestDatabase) has 2 filegroups called 'PRIMARY' and 'SECONDARY', and is bulk-logged. The 'SECONDARY' filegroup is set to readonly since no data gets changed there by the applications, it is read-only data. Sometimes this read-only data needs an update, so I need to update the data in the 'SECONDARY' filegroup by running some long data-operations. These data-operations are executed and checked on a another database (which is a backup of TestDatabase) called TestDatabaseDemo. When everything is correct in TestDatabaseDemo we can copy all objects from the 'SECONDARY'-filegroup of TestDatabaseDemo to the 'SECONDARY'-filegroup of TestDatabase using DTS. This takes a long time and I want to try if I could speed up things by using the following strategy:
Take a full backup of TestDatabase
Restore full backup as TestDatabaseDemo
Run long-running data-operations on TestDatabaseDemo
Take a backup of TestDatabaseDemo
Restore only the 'SECONDARY'-filegroup from TestDatabaseDemo to TestDatabase, and keeping the 'PRIMARY' filegroup from TestDatabase as it was at that moment.
Suppose we arrived at step 5, I am executing the following commands:
Code Snippet
--make full backup of TestDatabase
backup database TestDatabase to DISK='G:\temp\testdatabase.bak' with init
--make full backup of TestDatabaseDemo
backup database TestDatabaseDemo to DISK='G:\temp\testdatabasedemo.bak' with init
backup log TestDatabase to DISK='g:\temp\testdatabase.log'
--restore secondary filegroup from TestDatabasedemo-backup
restore database TestDatabase FILEGROUP='SECONDARY' FROM DISK='G:\temp\testdatabasedemo.bak'
with move 'TestDatabase_Data_Secondary' to 'G:\temp\TestDatabase_Data_secondary.ndf', NORECOVERY
--restore primary filegroup from Testdatabase-backup
restore database TestDatabase FILEGROUP='PRIMARY' FROM DISK='G:\temp\testdatabase.bak'
with move 'TestDatabase_Data' to 'G:\temp\TestDatabase_Data.mdf', NORECOVERY
--restore log and try to get db onlin
restore log TestDatabase FROM DISK='g:\temp\testdatabase.log' with recovery
I get the following error:
The log in this backup set terminates at LSN 6000000021500001, which is too early to apply to the database. A more recent log backup that includes LSN 6000000022400003 can be restored.
When trying to execute "RESTORE DATABASE TestDatabase WITH RECOVERY; " as last statement
I get error:
The database cannot be recovered because the files have been restored to inconsistent points in time.
How i can restore the read-only filegroup correctly?
Hi Stijn,
Simple answer is that you can't do that. The SECONDARY filegroup is now at a different (more recent) point in time than the rest of the TestDatabase - exactly like the final error message says. What you're essentially trying to do is mix-n-match filegroups from different databases.
Thanks
|||Hi Paul,
Thanks for the answer! I was thinking the mix-n-match would work, because that filegroup is readonly for the database, so applying the transaction log would be good enough for the other (read-write) filegroup, since there couldn't be any inserts/updates/deletes on the secondary filegroup. Which technique is used on very large databases to update a read-only filegroup? Using dts to copy objects from a test-database to the production database? Or is there a more efficient way?
Restore readonly filegroup sqlserver 2000
Hi,
I have a database running on sqlserver 2000. This database (let's call it TestDatabase) has 2 filegroups called 'PRIMARY' and 'SECONDARY', and is bulk-logged. The 'SECONDARY' filegroup is set to readonly since no data gets changed there by the applications, it is read-only data. Sometimes this read-only data needs an update, so I need to update the data in the 'SECONDARY' filegroup by running some long data-operations. These data-operations are executed and checked on a another database (which is a backup of TestDatabase) called TestDatabaseDemo. When everything is correct in TestDatabaseDemo we can copy all objects from the 'SECONDARY'-filegroup of TestDatabaseDemo to the 'SECONDARY'-filegroup of TestDatabase using DTS. This takes a long time and I want to try if I could speed up things by using the following strategy:
Take a full backup of TestDatabase
Restore full backup as TestDatabaseDemo
Run long-running data-operations on TestDatabaseDemo
Take a backup of TestDatabaseDemo
Restore only the 'SECONDARY'-filegroup from TestDatabaseDemo to TestDatabase, and keeping the 'PRIMARY' filegroup from TestDatabase as it was at that moment.
Suppose we arrived at step 5, I am executing the following commands:
Code Snippet
--make full backup of TestDatabase
backup database TestDatabase to DISK='G:\temp\testdatabase.bak' with init
--make full backup of TestDatabaseDemo
backup database TestDatabaseDemo to DISK='G:\temp\testdatabasedemo.bak' with init
backup log TestDatabase to DISK='g:\temp\testdatabase.log'
--restore secondary filegroup from TestDatabasedemo-backup
restore database TestDatabase FILEGROUP='SECONDARY' FROM DISK='G:\temp\testdatabasedemo.bak'
with move 'TestDatabase_Data_Secondary' to 'G:\temp\TestDatabase_Data_secondary.ndf', NORECOVERY
--restore primary filegroup from Testdatabase-backup
restore database TestDatabase FILEGROUP='PRIMARY' FROM DISK='G:\temp\testdatabase.bak'
with move 'TestDatabase_Data' to 'G:\temp\TestDatabase_Data.mdf', NORECOVERY
--restore log and try to get db onlin
restore log TestDatabase FROM DISK='g:\temp\testdatabase.log' with recovery
I get the following error:
The log in this backup set terminates at LSN 6000000021500001, which is too early to apply to the database. A more recent log backup that includes LSN 6000000022400003 can be restored.
When trying to execute "RESTORE DATABASE TestDatabase WITH RECOVERY; " as last statement
I get error:
The database cannot be recovered because the files have been restored to inconsistent points in time.
How i can restore the read-only filegroup correctly?
Hi Stijn,
Simple answer is that you can't do that. The SECONDARY filegroup is now at a different (more recent) point in time than the rest of the TestDatabase - exactly like the final error message says. What you're essentially trying to do is mix-n-match filegroups from different databases.
Thanks
|||Hi Paul,
Thanks for the answer! I was thinking the mix-n-match would work, because that filegroup is readonly for the database, so applying the transaction log would be good enough for the other (read-write) filegroup, since there couldn't be any inserts/updates/deletes on the secondary filegroup. Which technique is used on very large databases to update a read-only filegroup? Using dts to copy objects from a test-database to the production database? Or is there a more efficient way?
Monday, March 12, 2012
Restore publication db
Hello All -
When trying to restore the publication database, I am losing the
publication! ( Running merge replication, SQL Server 2000, push
subscriptions).
I am using the RESTORE command as follows:
RESTORE DATABASE CDB FROM DISK = 'c:\temp\somefile.bu'
WITH KEEP_REPLICATION
I had a 'successful' return from running the above command.
When I open EM \ DB \ Replication, my publication is gone. The merge
agents are there but if I try to reinit, it tells me that the publication
does not exist.
What am I doing wrong?
Thanks,
bruce
Something is strange here. This should work. Does the server you are doing
your restore on have replication installed on it?
What happens if you enable the database you are going to restore to for
merge replication and then do the restore with the keep_replication switch?
"rr" <bruceradtke@.REMOVEspamREMOVE.earthlink.net> wrote in message
news:JUREc.10114$oW6.1420194@.twister.nyc.rr.com...
> Hello All -
> When trying to restore the publication database, I am losing the
> publication! ( Running merge replication, SQL Server 2000, push
> subscriptions).
> I am using the RESTORE command as follows:
> RESTORE DATABASE CDB FROM DISK = 'c:\temp\somefile.bu'
> WITH KEEP_REPLICATION
> I had a 'successful' return from running the above command.
> When I open EM \ DB \ Replication, my publication is gone. The merge
> agents are there but if I try to reinit, it tells me that the publication
> does not exist.
> What am I doing wrong?
> Thanks,
> bruce
>
>
>
|||Bruce,
are you restoring to a different server. If the servername is different,
this is normal behaviour in my experience as the servername is entered into
several metadata tables eg In sysmerge articles there is a publisherid. This
ID needs to have a corresponding record in sysmergepublications. However, in
sysmergepublications, the 'publisher' column needs to match the servername,
which it doesn't in this case as you have restored to another servername. In
this case you need to script out the publications on the initial server,
modify the scripts and then reapply them on the second server.
HTH,
Paul Ibison
|||Hillary -
I have merge replication working on the publication database ( publication &
distribution on same machine). I then stop all agents to get exclusive
access to the db. I run the restore command with the KEEP_REPLICATION flag.
When I go to reinit all subscribers, the publication is gone.
I'm not sure of your question
> What happens if you enable the database you are going to restore to for
> merge replication and then do the restore with the keep_replication
switch?
I am backing up the publication database and then restore the publication
database.
Regards,
bruce
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:uTGIZ$1XEHA.1656@.TK2MSFTNGP09.phx.gbl...
> Something is strange here. This should work. Does the server you are doing
> your restore on have replication installed on it?
>
> What happens if you enable the database you are going to restore to for
> merge replication and then do the restore with the keep_replication
switch?[vbcol=seagreen]
> "rr" <bruceradtke@.REMOVEspamREMOVE.earthlink.net> wrote in message
> news:JUREc.10114$oW6.1420194@.twister.nyc.rr.com...
publication
>
|||Paul & Hillary-
Thanks for the replies.
That's it! I am restoring a backup from the production machine to my
developement machine.
I guess to do this I should use the scripting repl. wizard to create the
repl setting on the development machine. Oh the tangled web we weave...
Regards,
bruce
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:eC$UYE2XEHA.3512@.TK2MSFTNGP12.phx.gbl...
> Bruce,
> are you restoring to a different server. If the servername is different,
> this is normal behaviour in my experience as the servername is entered
into
> several metadata tables eg In sysmerge articles there is a publisherid.
This
> ID needs to have a corresponding record in sysmergepublications. However,
in
> sysmergepublications, the 'publisher' column needs to match the
servername,
> which it doesn't in this case as you have restored to another servername.
In
> this case you need to script out the publications on the initial server,
> modify the scripts and then reapply them on the second server.
> HTH,
> Paul Ibison
>
|||again this should restore your merge publications intact.
To go over the steps you have a production machine and a test machine.
replication is installed on both of them. You have two databases which are
enabled for merge replication. You back up the existing production merge
replication database and restored it to a database which is enabled for
merge replication in the test environment.
Your merge replication publications (but not the subscriptions or agent
info) is restored into the test database.
"rr" <bruceradtke@.REMOVEspamREMOVE.earthlink.net> wrote in message
news:PMTEc.10124$oW6.1440077@.twister.nyc.rr.com... [vbcol=seagreen]
> Paul & Hillary-
> Thanks for the replies.
> That's it! I am restoring a backup from the production machine to my
> developement machine.
> I guess to do this I should use the scripting repl. wizard to create the
> repl setting on the development machine. Oh the tangled web we weave...
> Regards,
> bruce
> "Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
> news:eC$UYE2XEHA.3512@.TK2MSFTNGP12.phx.gbl...
> into
> This
However,[vbcol=seagreen]
> in
> servername,
servername.
> In
>
|||Yes that is the scenario.
It seems that the BACKUP command should have a NOT_FOR_REPLICATION flag or
something similar. In order to skip the replication backup.
Thanks again for the replies.
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:eTCpL02XEHA.1000@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> again this should restore your merge publications intact.
> To go over the steps you have a production machine and a test machine.
> replication is installed on both of them. You have two databases which are
> enabled for merge replication. You back up the existing production merge
> replication database and restored it to a database which is enabled for
> merge replication in the test environment.
> Your merge replication publications (but not the subscriptions or agent
> info) is restored into the test database.
> "rr" <bruceradtke@.REMOVEspamREMOVE.earthlink.net> wrote in message
> news:PMTEc.10124$oW6.1440077@.twister.nyc.rr.com...
weave...[vbcol=seagreen]
different,[vbcol=seagreen]
publisherid.[vbcol=seagreen]
> However,
> servername.
server,
>
When trying to restore the publication database, I am losing the
publication! ( Running merge replication, SQL Server 2000, push
subscriptions).
I am using the RESTORE command as follows:
RESTORE DATABASE CDB FROM DISK = 'c:\temp\somefile.bu'
WITH KEEP_REPLICATION
I had a 'successful' return from running the above command.
When I open EM \ DB \ Replication, my publication is gone. The merge
agents are there but if I try to reinit, it tells me that the publication
does not exist.
What am I doing wrong?
Thanks,
bruce
Something is strange here. This should work. Does the server you are doing
your restore on have replication installed on it?
What happens if you enable the database you are going to restore to for
merge replication and then do the restore with the keep_replication switch?
"rr" <bruceradtke@.REMOVEspamREMOVE.earthlink.net> wrote in message
news:JUREc.10114$oW6.1420194@.twister.nyc.rr.com...
> Hello All -
> When trying to restore the publication database, I am losing the
> publication! ( Running merge replication, SQL Server 2000, push
> subscriptions).
> I am using the RESTORE command as follows:
> RESTORE DATABASE CDB FROM DISK = 'c:\temp\somefile.bu'
> WITH KEEP_REPLICATION
> I had a 'successful' return from running the above command.
> When I open EM \ DB \ Replication, my publication is gone. The merge
> agents are there but if I try to reinit, it tells me that the publication
> does not exist.
> What am I doing wrong?
> Thanks,
> bruce
>
>
>
|||Bruce,
are you restoring to a different server. If the servername is different,
this is normal behaviour in my experience as the servername is entered into
several metadata tables eg In sysmerge articles there is a publisherid. This
ID needs to have a corresponding record in sysmergepublications. However, in
sysmergepublications, the 'publisher' column needs to match the servername,
which it doesn't in this case as you have restored to another servername. In
this case you need to script out the publications on the initial server,
modify the scripts and then reapply them on the second server.
HTH,
Paul Ibison
|||Hillary -
I have merge replication working on the publication database ( publication &
distribution on same machine). I then stop all agents to get exclusive
access to the db. I run the restore command with the KEEP_REPLICATION flag.
When I go to reinit all subscribers, the publication is gone.
I'm not sure of your question
> What happens if you enable the database you are going to restore to for
> merge replication and then do the restore with the keep_replication
switch?
I am backing up the publication database and then restore the publication
database.
Regards,
bruce
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:uTGIZ$1XEHA.1656@.TK2MSFTNGP09.phx.gbl...
> Something is strange here. This should work. Does the server you are doing
> your restore on have replication installed on it?
>
> What happens if you enable the database you are going to restore to for
> merge replication and then do the restore with the keep_replication
switch?[vbcol=seagreen]
> "rr" <bruceradtke@.REMOVEspamREMOVE.earthlink.net> wrote in message
> news:JUREc.10114$oW6.1420194@.twister.nyc.rr.com...
publication
>
|||Paul & Hillary-
Thanks for the replies.
That's it! I am restoring a backup from the production machine to my
developement machine.
I guess to do this I should use the scripting repl. wizard to create the
repl setting on the development machine. Oh the tangled web we weave...
Regards,
bruce
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:eC$UYE2XEHA.3512@.TK2MSFTNGP12.phx.gbl...
> Bruce,
> are you restoring to a different server. If the servername is different,
> this is normal behaviour in my experience as the servername is entered
into
> several metadata tables eg In sysmerge articles there is a publisherid.
This
> ID needs to have a corresponding record in sysmergepublications. However,
in
> sysmergepublications, the 'publisher' column needs to match the
servername,
> which it doesn't in this case as you have restored to another servername.
In
> this case you need to script out the publications on the initial server,
> modify the scripts and then reapply them on the second server.
> HTH,
> Paul Ibison
>
|||again this should restore your merge publications intact.
To go over the steps you have a production machine and a test machine.
replication is installed on both of them. You have two databases which are
enabled for merge replication. You back up the existing production merge
replication database and restored it to a database which is enabled for
merge replication in the test environment.
Your merge replication publications (but not the subscriptions or agent
info) is restored into the test database.
"rr" <bruceradtke@.REMOVEspamREMOVE.earthlink.net> wrote in message
news:PMTEc.10124$oW6.1440077@.twister.nyc.rr.com... [vbcol=seagreen]
> Paul & Hillary-
> Thanks for the replies.
> That's it! I am restoring a backup from the production machine to my
> developement machine.
> I guess to do this I should use the scripting repl. wizard to create the
> repl setting on the development machine. Oh the tangled web we weave...
> Regards,
> bruce
> "Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
> news:eC$UYE2XEHA.3512@.TK2MSFTNGP12.phx.gbl...
> into
> This
However,[vbcol=seagreen]
> in
> servername,
servername.
> In
>
|||Yes that is the scenario.
It seems that the BACKUP command should have a NOT_FOR_REPLICATION flag or
something similar. In order to skip the replication backup.
Thanks again for the replies.
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:eTCpL02XEHA.1000@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> again this should restore your merge publications intact.
> To go over the steps you have a production machine and a test machine.
> replication is installed on both of them. You have two databases which are
> enabled for merge replication. You back up the existing production merge
> replication database and restored it to a database which is enabled for
> merge replication in the test environment.
> Your merge replication publications (but not the subscriptions or agent
> info) is restored into the test database.
> "rr" <bruceradtke@.REMOVEspamREMOVE.earthlink.net> wrote in message
> news:PMTEc.10124$oW6.1440077@.twister.nyc.rr.com...
weave...[vbcol=seagreen]
different,[vbcol=seagreen]
publisherid.[vbcol=seagreen]
> However,
> servername.
server,
>
restore problem
Hi
i started a restore on a little db, it is still running (more than 15 mins),
how can i understand what is it doing?
Carlo
How little is the database?
In the future you can use the WITH STATS option to show you the percent
complete.
I am guessing that the SQL Server's disks are busy creating the database
files that will hold the data.
Keith
"Carlo" <marcocci@.ingv.it> wrote in message
news:utG3YN8fEHA.704@.TK2MSFTNGP09.phx.gbl...
> Hi
> i started a restore on a little db, it is still running (more than 15
mins),
> how can i understand what is it doing?
> Carlo
> --
>
>
|||the size of db is around 9 mb, it is a test db, it is still loading, how can
i stop the restore?
|||Are you able to see the new data/log files created in OS?
Also check to see if there's blocks.
"Carlo" <marcocci@.ingv.it> wrote in message
news:%23KaggZ8fEHA.2984@.tk2msftngp13.phx.gbl...
> the size of db is around 9 mb, it is a test db, it is still loading, how
can
> i stop the restore?
>
|||9MB. That is darn small. It has not finished yet? 22 minutes have gone by
since your original post and your second post. That is a too long to wait
for a 9MB database.
What did you use to begin the restore? Query Analyzer? Enterprise Manager?
Perhaps you could try closing the app. You could also kill that specific
connection, but that would be harsh.
Keith
"Carlo" <marcocci@.ingv.it> wrote in message
news:%23KaggZ8fEHA.2984@.tk2msftngp13.phx.gbl...
> the size of db is around 9 mb, it is a test db, it is still loading, how
can
> i stop the restore?
>
|||i stop the service and start it again, the db is alwais loading, i found in
the log this message:
Bypassing recovery for database 'db_rsnd' because it is marked IN LOAD.
what have i to do?
i'd like to know if i can delete the db from the server, but i cant do it
from the manager because it is loading and i suppose i cant delete it from
the console too. is there a way to delete the "row" in the master db that
let it know that my db exists? i hope you understand what i mean.
Carlo
********************************************
Carlo Marcocci
Istituto Nazionale di Geofisica e Vulcanologia
Via di Vigna Murata 605, 00143 Roma
Tel. +39-6-51860391
Fax. +39-6-51860507
mailto: marcocci@.ingv.it
******************************************** L&P
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> ha scritto nel messaggio
news:ufwtZL9fEHA.3024@.TK2MSFTNGP10.phx.gbl...
> 9MB. That is darn small. It has not finished yet? 22 minutes have gone
by
> since your original post and your second post. That is a too long to wait
> for a 9MB database.
> What did you use to begin the restore? Query Analyzer? Enterprise
Manager?
> Perhaps you could try closing the app. You could also kill that specific
> connection, but that would be harsh.
> --
> Keith
>
> "Carlo" <marcocci@.ingv.it> wrote in message
> news:%23KaggZ8fEHA.2984@.tk2msftngp13.phx.gbl...
> can
>
|||may i use this ?
UPDATE sysdatabases
SET status=16
WHERE name='daCancellare'
does it change anything?
********************************************
Carlo Marcocci
Istituto Nazionale di Geofisica e Vulcanologia
Via di Vigna Murata 605, 00143 Roma
Tel. +39-6-51860391
Fax. +39-6-51860507
mailto: marcocci@.ingv.it
******************************************** L&P
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> ha scritto nel messaggio
news:ufwtZL9fEHA.3024@.TK2MSFTNGP10.phx.gbl...
> 9MB. That is darn small. It has not finished yet? 22 minutes have gone
by
> since your original post and your second post. That is a too long to wait
> for a 9MB database.
> What did you use to begin the restore? Query Analyzer? Enterprise
Manager?
> Perhaps you could try closing the app. You could also kill that specific
> connection, but that would be harsh.
> --
> Keith
>
> "Carlo" <marcocci@.ingv.it> wrote in message
> news:%23KaggZ8fEHA.2984@.tk2msftngp13.phx.gbl...
> can
>
|||I would try using DROP DATABASE
Information within Books Online (within the SQL Server program group).
Keith
"Carlo" <marcocci@.ingv.it> wrote in message
news:OyzQU09fEHA.3916@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> may i use this ?
> UPDATE sysdatabases
> SET status=16
> WHERE name='daCancellare'
> does it change anything?
>
> --
>
> ********************************************
> Carlo Marcocci
> Istituto Nazionale di Geofisica e Vulcanologia
> Via di Vigna Murata 605, 00143 Roma
> Tel. +39-6-51860391
> Fax. +39-6-51860507
> mailto: marcocci@.ingv.it
> ******************************************** L&P
> "Keith Kratochvil" <sqlguy.back2u@.comcast.net> ha scritto nel messaggio
> news:ufwtZL9fEHA.3024@.TK2MSFTNGP10.phx.gbl...
gone[vbcol=seagreen]
> by
wait[vbcol=seagreen]
> Manager?
specific[vbcol=seagreen]
how
>
|||Read up on DROP DATABASE within Books Online (within the SQL Server program
group).
Keith
"Carlo" <marcocci@.ingv.it> wrote in message
news:ex%23jop9fEHA.3932@.TK2MSFTNGP09.phx.gbl...
> i stop the service and start it again, the db is alwais loading, i found
in[vbcol=seagreen]
> the log this message:
> Bypassing recovery for database 'db_rsnd' because it is marked IN LOAD.
> what have i to do?
> i'd like to know if i can delete the db from the server, but i cant do it
> from the manager because it is loading and i suppose i cant delete it from
> the console too. is there a way to delete the "row" in the master db that
> let it know that my db exists? i hope you understand what i mean.
> Carlo
> --
>
> ********************************************
> Carlo Marcocci
> Istituto Nazionale di Geofisica e Vulcanologia
> Via di Vigna Murata 605, 00143 Roma
> Tel. +39-6-51860391
> Fax. +39-6-51860507
> mailto: marcocci@.ingv.it
> ******************************************** L&P
> "Keith Kratochvil" <sqlguy.back2u@.comcast.net> ha scritto nel messaggio
> news:ufwtZL9fEHA.3024@.TK2MSFTNGP10.phx.gbl...
gone[vbcol=seagreen]
> by
wait[vbcol=seagreen]
> Manager?
specific[vbcol=seagreen]
how
>
|||By now you have fixed your problem. Some added thoughts.
I had a similar issue running SQL Server on a small PC that runs 24x7 (far
too little memory). There were times when a process that normally took 15
minutes ran for more than 3 hours.
1. Sometimes a reboot would speed up the process. Evidently, SQL Server
would grow and grow far beyond the physical memory. The PC spent all its
time paging memory in and out. There is a property to prevent this and set
the maximum memory that SQL Server can use.
2. I also had to set logging to a simple type rather than the full logging.
This is not a production database and we perform daily backups since it is
small. Simple logging is all that is required. With full logging, my tiny
databases (under 50 MB) grew to almost a gigabyte.
3. Wrote a stored procedure that runs in the SQL Server job scheduler every
night that performs a reindex on every table, then gets rid of the log ,
then shrinks the database. Issue has pretty much gone away.
"Carlo" <marcocci@.ingv.it> wrote in message
news:utG3YN8fEHA.704@.TK2MSFTNGP09.phx.gbl...
> Hi
> i started a restore on a little db, it is still running (more than 15
mins),
> how can i understand what is it doing?
> Carlo
> --
>
>
i started a restore on a little db, it is still running (more than 15 mins),
how can i understand what is it doing?
Carlo
How little is the database?
In the future you can use the WITH STATS option to show you the percent
complete.
I am guessing that the SQL Server's disks are busy creating the database
files that will hold the data.
Keith
"Carlo" <marcocci@.ingv.it> wrote in message
news:utG3YN8fEHA.704@.TK2MSFTNGP09.phx.gbl...
> Hi
> i started a restore on a little db, it is still running (more than 15
mins),
> how can i understand what is it doing?
> Carlo
> --
>
>
|||the size of db is around 9 mb, it is a test db, it is still loading, how can
i stop the restore?
|||Are you able to see the new data/log files created in OS?
Also check to see if there's blocks.
"Carlo" <marcocci@.ingv.it> wrote in message
news:%23KaggZ8fEHA.2984@.tk2msftngp13.phx.gbl...
> the size of db is around 9 mb, it is a test db, it is still loading, how
can
> i stop the restore?
>
|||9MB. That is darn small. It has not finished yet? 22 minutes have gone by
since your original post and your second post. That is a too long to wait
for a 9MB database.
What did you use to begin the restore? Query Analyzer? Enterprise Manager?
Perhaps you could try closing the app. You could also kill that specific
connection, but that would be harsh.
Keith
"Carlo" <marcocci@.ingv.it> wrote in message
news:%23KaggZ8fEHA.2984@.tk2msftngp13.phx.gbl...
> the size of db is around 9 mb, it is a test db, it is still loading, how
can
> i stop the restore?
>
|||i stop the service and start it again, the db is alwais loading, i found in
the log this message:
Bypassing recovery for database 'db_rsnd' because it is marked IN LOAD.
what have i to do?
i'd like to know if i can delete the db from the server, but i cant do it
from the manager because it is loading and i suppose i cant delete it from
the console too. is there a way to delete the "row" in the master db that
let it know that my db exists? i hope you understand what i mean.
Carlo
********************************************
Carlo Marcocci
Istituto Nazionale di Geofisica e Vulcanologia
Via di Vigna Murata 605, 00143 Roma
Tel. +39-6-51860391
Fax. +39-6-51860507
mailto: marcocci@.ingv.it
******************************************** L&P
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> ha scritto nel messaggio
news:ufwtZL9fEHA.3024@.TK2MSFTNGP10.phx.gbl...
> 9MB. That is darn small. It has not finished yet? 22 minutes have gone
by
> since your original post and your second post. That is a too long to wait
> for a 9MB database.
> What did you use to begin the restore? Query Analyzer? Enterprise
Manager?
> Perhaps you could try closing the app. You could also kill that specific
> connection, but that would be harsh.
> --
> Keith
>
> "Carlo" <marcocci@.ingv.it> wrote in message
> news:%23KaggZ8fEHA.2984@.tk2msftngp13.phx.gbl...
> can
>
|||may i use this ?
UPDATE sysdatabases
SET status=16
WHERE name='daCancellare'
does it change anything?
********************************************
Carlo Marcocci
Istituto Nazionale di Geofisica e Vulcanologia
Via di Vigna Murata 605, 00143 Roma
Tel. +39-6-51860391
Fax. +39-6-51860507
mailto: marcocci@.ingv.it
******************************************** L&P
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> ha scritto nel messaggio
news:ufwtZL9fEHA.3024@.TK2MSFTNGP10.phx.gbl...
> 9MB. That is darn small. It has not finished yet? 22 minutes have gone
by
> since your original post and your second post. That is a too long to wait
> for a 9MB database.
> What did you use to begin the restore? Query Analyzer? Enterprise
Manager?
> Perhaps you could try closing the app. You could also kill that specific
> connection, but that would be harsh.
> --
> Keith
>
> "Carlo" <marcocci@.ingv.it> wrote in message
> news:%23KaggZ8fEHA.2984@.tk2msftngp13.phx.gbl...
> can
>
|||I would try using DROP DATABASE
Information within Books Online (within the SQL Server program group).
Keith
"Carlo" <marcocci@.ingv.it> wrote in message
news:OyzQU09fEHA.3916@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> may i use this ?
> UPDATE sysdatabases
> SET status=16
> WHERE name='daCancellare'
> does it change anything?
>
> --
>
> ********************************************
> Carlo Marcocci
> Istituto Nazionale di Geofisica e Vulcanologia
> Via di Vigna Murata 605, 00143 Roma
> Tel. +39-6-51860391
> Fax. +39-6-51860507
> mailto: marcocci@.ingv.it
> ******************************************** L&P
> "Keith Kratochvil" <sqlguy.back2u@.comcast.net> ha scritto nel messaggio
> news:ufwtZL9fEHA.3024@.TK2MSFTNGP10.phx.gbl...
gone[vbcol=seagreen]
> by
wait[vbcol=seagreen]
> Manager?
specific[vbcol=seagreen]
how
>
|||Read up on DROP DATABASE within Books Online (within the SQL Server program
group).
Keith
"Carlo" <marcocci@.ingv.it> wrote in message
news:ex%23jop9fEHA.3932@.TK2MSFTNGP09.phx.gbl...
> i stop the service and start it again, the db is alwais loading, i found
in[vbcol=seagreen]
> the log this message:
> Bypassing recovery for database 'db_rsnd' because it is marked IN LOAD.
> what have i to do?
> i'd like to know if i can delete the db from the server, but i cant do it
> from the manager because it is loading and i suppose i cant delete it from
> the console too. is there a way to delete the "row" in the master db that
> let it know that my db exists? i hope you understand what i mean.
> Carlo
> --
>
> ********************************************
> Carlo Marcocci
> Istituto Nazionale di Geofisica e Vulcanologia
> Via di Vigna Murata 605, 00143 Roma
> Tel. +39-6-51860391
> Fax. +39-6-51860507
> mailto: marcocci@.ingv.it
> ******************************************** L&P
> "Keith Kratochvil" <sqlguy.back2u@.comcast.net> ha scritto nel messaggio
> news:ufwtZL9fEHA.3024@.TK2MSFTNGP10.phx.gbl...
gone[vbcol=seagreen]
> by
wait[vbcol=seagreen]
> Manager?
specific[vbcol=seagreen]
how
>
|||By now you have fixed your problem. Some added thoughts.
I had a similar issue running SQL Server on a small PC that runs 24x7 (far
too little memory). There were times when a process that normally took 15
minutes ran for more than 3 hours.
1. Sometimes a reboot would speed up the process. Evidently, SQL Server
would grow and grow far beyond the physical memory. The PC spent all its
time paging memory in and out. There is a property to prevent this and set
the maximum memory that SQL Server can use.
2. I also had to set logging to a simple type rather than the full logging.
This is not a production database and we perform daily backups since it is
small. Simple logging is all that is required. With full logging, my tiny
databases (under 50 MB) grew to almost a gigabyte.
3. Wrote a stored procedure that runs in the SQL Server job scheduler every
night that performs a reindex on every table, then gets rid of the log ,
then shrinks the database. Issue has pretty much gone away.
"Carlo" <marcocci@.ingv.it> wrote in message
news:utG3YN8fEHA.704@.TK2MSFTNGP09.phx.gbl...
> Hi
> i started a restore on a little db, it is still running (more than 15
mins),
> how can i understand what is it doing?
> Carlo
> --
>
>
restore problem
HELLO ALL
I have a problem about DB restor:
I have a backup file of a DB about 600MB,when i try to restore on
another server running SQL SERVER 2000 with same sp3,it show me the error :
Microsoft SQL-DMO(ODBC SQLState:42000)
An internal consistency occurred.Contact Technical Support for
assistance.RESTORE DATABASE is terminating abnormally.
The original database has been erased,all i have is the backup file.
Anyone tell me how this happen and how to resolve it?
Thanks a lot.
Danny
Can you show us your RESTORE command?
"Danny Lu" <xlu2@.hotmail.com> wrote in message
news:elbc%23YlGFHA.2132@.TK2MSFTNGP14.phx.gbl...
> HELLO ALL
> I have a problem about DB restor:
> I have a backup file of a DB about 600MB,when i try to restore on
> another server running SQL SERVER 2000 with same sp3,it show me the error
:
> Microsoft SQL-DMO(ODBC SQLState:42000)
> An internal consistency occurred.Contact Technical Support for
> assistance.RESTORE DATABASE is terminating abnormally.
> The original database has been erased,all i have is the backup file.
> Anyone tell me how this happen and how to resolve it?
> Thanks a lot.
>
|||Sounds to me like you should do what the error say. There is a problem in the backup and you need MS
to possibly help you. Or go to the prior database backup (and possibly all subsequent log backups).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Danny Lu" <xlu2@.hotmail.com> wrote in message news:elbc%23YlGFHA.2132@.TK2MSFTNGP14.phx.gbl...
> HELLO ALL
> I have a problem about DB restor:
> I have a backup file of a DB about 600MB,when i try to restore on another server running SQL
> SERVER 2000 with same sp3,it show me the error :
> Microsoft SQL-DMO(ODBC SQLState:42000)
> An internal consistency occurred.Contact Technical Support for assistance.RESTORE DATABASE is
> terminating abnormally.
> The original database has been erased,all i have is the backup file.
> Anyone tell me how this happen and how to resolve it?
> Thanks a lot.
>
I have a problem about DB restor:
I have a backup file of a DB about 600MB,when i try to restore on
another server running SQL SERVER 2000 with same sp3,it show me the error :
Microsoft SQL-DMO(ODBC SQLState:42000)
An internal consistency occurred.Contact Technical Support for
assistance.RESTORE DATABASE is terminating abnormally.
The original database has been erased,all i have is the backup file.
Anyone tell me how this happen and how to resolve it?
Thanks a lot.
Danny
Can you show us your RESTORE command?
"Danny Lu" <xlu2@.hotmail.com> wrote in message
news:elbc%23YlGFHA.2132@.TK2MSFTNGP14.phx.gbl...
> HELLO ALL
> I have a problem about DB restor:
> I have a backup file of a DB about 600MB,when i try to restore on
> another server running SQL SERVER 2000 with same sp3,it show me the error
:
> Microsoft SQL-DMO(ODBC SQLState:42000)
> An internal consistency occurred.Contact Technical Support for
> assistance.RESTORE DATABASE is terminating abnormally.
> The original database has been erased,all i have is the backup file.
> Anyone tell me how this happen and how to resolve it?
> Thanks a lot.
>
|||Sounds to me like you should do what the error say. There is a problem in the backup and you need MS
to possibly help you. Or go to the prior database backup (and possibly all subsequent log backups).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Danny Lu" <xlu2@.hotmail.com> wrote in message news:elbc%23YlGFHA.2132@.TK2MSFTNGP14.phx.gbl...
> HELLO ALL
> I have a problem about DB restor:
> I have a backup file of a DB about 600MB,when i try to restore on another server running SQL
> SERVER 2000 with same sp3,it show me the error :
> Microsoft SQL-DMO(ODBC SQLState:42000)
> An internal consistency occurred.Contact Technical Support for assistance.RESTORE DATABASE is
> terminating abnormally.
> The original database has been erased,all i have is the backup file.
> Anyone tell me how this happen and how to resolve it?
> Thanks a lot.
>
restore problem
Hi
i started a restore on a little db, it is still running (more than 15 mins),
how can i understand what is it doing?
Carlo
How little is the database?
In the future you can use the WITH STATS option to show you the percent
complete.
I am guessing that the SQL Server's disks are busy creating the database
files that will hold the data.
Keith
"Carlo" <marcocci@.ingv.it> wrote in message
news:utG3YN8fEHA.704@.TK2MSFTNGP09.phx.gbl...
> Hi
> i started a restore on a little db, it is still running (more than 15
mins),
> how can i understand what is it doing?
> Carlo
> --
>
>
|||the size of db is around 9 mb, it is a test db, it is still loading, how can
i stop the restore?
|||Are you able to see the new data/log files created in OS?
Also check to see if there's blocks.
"Carlo" <marcocci@.ingv.it> wrote in message
news:%23KaggZ8fEHA.2984@.tk2msftngp13.phx.gbl...
> the size of db is around 9 mb, it is a test db, it is still loading, how
can
> i stop the restore?
>
|||9MB. That is darn small. It has not finished yet? 22 minutes have gone by
since your original post and your second post. That is a too long to wait
for a 9MB database.
What did you use to begin the restore? Query Analyzer? Enterprise Manager?
Perhaps you could try closing the app. You could also kill that specific
connection, but that would be harsh.
Keith
"Carlo" <marcocci@.ingv.it> wrote in message
news:%23KaggZ8fEHA.2984@.tk2msftngp13.phx.gbl...
> the size of db is around 9 mb, it is a test db, it is still loading, how
can
> i stop the restore?
>
|||i stop the service and start it again, the db is alwais loading, i found in
the log this message:
Bypassing recovery for database 'db_rsnd' because it is marked IN LOAD.
what have i to do?
i'd like to know if i can delete the db from the server, but i cant do it
from the manager because it is loading and i suppose i cant delete it from
the console too. is there a way to delete the "row" in the master db that
let it know that my db exists? i hope you understand what i mean.
Carlo
********************************************
Carlo Marcocci
Istituto Nazionale di Geofisica e Vulcanologia
Via di Vigna Murata 605, 00143 Roma
Tel. +39-6-51860391
Fax. +39-6-51860507
mailto: marcocci@.ingv.it
******************************************** L&P
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> ha scritto nel messaggio
news:ufwtZL9fEHA.3024@.TK2MSFTNGP10.phx.gbl...
> 9MB. That is darn small. It has not finished yet? 22 minutes have gone
by
> since your original post and your second post. That is a too long to wait
> for a 9MB database.
> What did you use to begin the restore? Query Analyzer? Enterprise
Manager?
> Perhaps you could try closing the app. You could also kill that specific
> connection, but that would be harsh.
> --
> Keith
>
> "Carlo" <marcocci@.ingv.it> wrote in message
> news:%23KaggZ8fEHA.2984@.tk2msftngp13.phx.gbl...
> can
>
|||may i use this ?
UPDATE sysdatabases
SET status=16
WHERE name='daCancellare'
does it change anything?
********************************************
Carlo Marcocci
Istituto Nazionale di Geofisica e Vulcanologia
Via di Vigna Murata 605, 00143 Roma
Tel. +39-6-51860391
Fax. +39-6-51860507
mailto: marcocci@.ingv.it
******************************************** L&P
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> ha scritto nel messaggio
news:ufwtZL9fEHA.3024@.TK2MSFTNGP10.phx.gbl...
> 9MB. That is darn small. It has not finished yet? 22 minutes have gone
by
> since your original post and your second post. That is a too long to wait
> for a 9MB database.
> What did you use to begin the restore? Query Analyzer? Enterprise
Manager?
> Perhaps you could try closing the app. You could also kill that specific
> connection, but that would be harsh.
> --
> Keith
>
> "Carlo" <marcocci@.ingv.it> wrote in message
> news:%23KaggZ8fEHA.2984@.tk2msftngp13.phx.gbl...
> can
>
|||I would try using DROP DATABASE
Information within Books Online (within the SQL Server program group).
Keith
"Carlo" <marcocci@.ingv.it> wrote in message
news:OyzQU09fEHA.3916@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> may i use this ?
> UPDATE sysdatabases
> SET status=16
> WHERE name='daCancellare'
> does it change anything?
>
> --
>
> ********************************************
> Carlo Marcocci
> Istituto Nazionale di Geofisica e Vulcanologia
> Via di Vigna Murata 605, 00143 Roma
> Tel. +39-6-51860391
> Fax. +39-6-51860507
> mailto: marcocci@.ingv.it
> ******************************************** L&P
> "Keith Kratochvil" <sqlguy.back2u@.comcast.net> ha scritto nel messaggio
> news:ufwtZL9fEHA.3024@.TK2MSFTNGP10.phx.gbl...
gone[vbcol=seagreen]
> by
wait[vbcol=seagreen]
> Manager?
specific[vbcol=seagreen]
how
>
|||Read up on DROP DATABASE within Books Online (within the SQL Server program
group).
Keith
"Carlo" <marcocci@.ingv.it> wrote in message
news:ex%23jop9fEHA.3932@.TK2MSFTNGP09.phx.gbl...
> i stop the service and start it again, the db is alwais loading, i found
in[vbcol=seagreen]
> the log this message:
> Bypassing recovery for database 'db_rsnd' because it is marked IN LOAD.
> what have i to do?
> i'd like to know if i can delete the db from the server, but i cant do it
> from the manager because it is loading and i suppose i cant delete it from
> the console too. is there a way to delete the "row" in the master db that
> let it know that my db exists? i hope you understand what i mean.
> Carlo
> --
>
> ********************************************
> Carlo Marcocci
> Istituto Nazionale di Geofisica e Vulcanologia
> Via di Vigna Murata 605, 00143 Roma
> Tel. +39-6-51860391
> Fax. +39-6-51860507
> mailto: marcocci@.ingv.it
> ******************************************** L&P
> "Keith Kratochvil" <sqlguy.back2u@.comcast.net> ha scritto nel messaggio
> news:ufwtZL9fEHA.3024@.TK2MSFTNGP10.phx.gbl...
gone[vbcol=seagreen]
> by
wait[vbcol=seagreen]
> Manager?
specific[vbcol=seagreen]
how
>
|||By now you have fixed your problem. Some added thoughts.
I had a similar issue running SQL Server on a small PC that runs 24x7 (far
too little memory). There were times when a process that normally took 15
minutes ran for more than 3 hours.
1. Sometimes a reboot would speed up the process. Evidently, SQL Server
would grow and grow far beyond the physical memory. The PC spent all its
time paging memory in and out. There is a property to prevent this and set
the maximum memory that SQL Server can use.
2. I also had to set logging to a simple type rather than the full logging.
This is not a production database and we perform daily backups since it is
small. Simple logging is all that is required. With full logging, my tiny
databases (under 50 MB) grew to almost a gigabyte.
3. Wrote a stored procedure that runs in the SQL Server job scheduler every
night that performs a reindex on every table, then gets rid of the log ,
then shrinks the database. Issue has pretty much gone away.
"Carlo" <marcocci@.ingv.it> wrote in message
news:utG3YN8fEHA.704@.TK2MSFTNGP09.phx.gbl...
> Hi
> i started a restore on a little db, it is still running (more than 15
mins),
> how can i understand what is it doing?
> Carlo
> --
>
>
i started a restore on a little db, it is still running (more than 15 mins),
how can i understand what is it doing?
Carlo
How little is the database?
In the future you can use the WITH STATS option to show you the percent
complete.
I am guessing that the SQL Server's disks are busy creating the database
files that will hold the data.
Keith
"Carlo" <marcocci@.ingv.it> wrote in message
news:utG3YN8fEHA.704@.TK2MSFTNGP09.phx.gbl...
> Hi
> i started a restore on a little db, it is still running (more than 15
mins),
> how can i understand what is it doing?
> Carlo
> --
>
>
|||the size of db is around 9 mb, it is a test db, it is still loading, how can
i stop the restore?
|||Are you able to see the new data/log files created in OS?
Also check to see if there's blocks.
"Carlo" <marcocci@.ingv.it> wrote in message
news:%23KaggZ8fEHA.2984@.tk2msftngp13.phx.gbl...
> the size of db is around 9 mb, it is a test db, it is still loading, how
can
> i stop the restore?
>
|||9MB. That is darn small. It has not finished yet? 22 minutes have gone by
since your original post and your second post. That is a too long to wait
for a 9MB database.
What did you use to begin the restore? Query Analyzer? Enterprise Manager?
Perhaps you could try closing the app. You could also kill that specific
connection, but that would be harsh.
Keith
"Carlo" <marcocci@.ingv.it> wrote in message
news:%23KaggZ8fEHA.2984@.tk2msftngp13.phx.gbl...
> the size of db is around 9 mb, it is a test db, it is still loading, how
can
> i stop the restore?
>
|||i stop the service and start it again, the db is alwais loading, i found in
the log this message:
Bypassing recovery for database 'db_rsnd' because it is marked IN LOAD.
what have i to do?
i'd like to know if i can delete the db from the server, but i cant do it
from the manager because it is loading and i suppose i cant delete it from
the console too. is there a way to delete the "row" in the master db that
let it know that my db exists? i hope you understand what i mean.
Carlo
********************************************
Carlo Marcocci
Istituto Nazionale di Geofisica e Vulcanologia
Via di Vigna Murata 605, 00143 Roma
Tel. +39-6-51860391
Fax. +39-6-51860507
mailto: marcocci@.ingv.it
******************************************** L&P
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> ha scritto nel messaggio
news:ufwtZL9fEHA.3024@.TK2MSFTNGP10.phx.gbl...
> 9MB. That is darn small. It has not finished yet? 22 minutes have gone
by
> since your original post and your second post. That is a too long to wait
> for a 9MB database.
> What did you use to begin the restore? Query Analyzer? Enterprise
Manager?
> Perhaps you could try closing the app. You could also kill that specific
> connection, but that would be harsh.
> --
> Keith
>
> "Carlo" <marcocci@.ingv.it> wrote in message
> news:%23KaggZ8fEHA.2984@.tk2msftngp13.phx.gbl...
> can
>
|||may i use this ?
UPDATE sysdatabases
SET status=16
WHERE name='daCancellare'
does it change anything?
********************************************
Carlo Marcocci
Istituto Nazionale di Geofisica e Vulcanologia
Via di Vigna Murata 605, 00143 Roma
Tel. +39-6-51860391
Fax. +39-6-51860507
mailto: marcocci@.ingv.it
******************************************** L&P
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> ha scritto nel messaggio
news:ufwtZL9fEHA.3024@.TK2MSFTNGP10.phx.gbl...
> 9MB. That is darn small. It has not finished yet? 22 minutes have gone
by
> since your original post and your second post. That is a too long to wait
> for a 9MB database.
> What did you use to begin the restore? Query Analyzer? Enterprise
Manager?
> Perhaps you could try closing the app. You could also kill that specific
> connection, but that would be harsh.
> --
> Keith
>
> "Carlo" <marcocci@.ingv.it> wrote in message
> news:%23KaggZ8fEHA.2984@.tk2msftngp13.phx.gbl...
> can
>
|||I would try using DROP DATABASE
Information within Books Online (within the SQL Server program group).
Keith
"Carlo" <marcocci@.ingv.it> wrote in message
news:OyzQU09fEHA.3916@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> may i use this ?
> UPDATE sysdatabases
> SET status=16
> WHERE name='daCancellare'
> does it change anything?
>
> --
>
> ********************************************
> Carlo Marcocci
> Istituto Nazionale di Geofisica e Vulcanologia
> Via di Vigna Murata 605, 00143 Roma
> Tel. +39-6-51860391
> Fax. +39-6-51860507
> mailto: marcocci@.ingv.it
> ******************************************** L&P
> "Keith Kratochvil" <sqlguy.back2u@.comcast.net> ha scritto nel messaggio
> news:ufwtZL9fEHA.3024@.TK2MSFTNGP10.phx.gbl...
gone[vbcol=seagreen]
> by
wait[vbcol=seagreen]
> Manager?
specific[vbcol=seagreen]
how
>
|||Read up on DROP DATABASE within Books Online (within the SQL Server program
group).
Keith
"Carlo" <marcocci@.ingv.it> wrote in message
news:ex%23jop9fEHA.3932@.TK2MSFTNGP09.phx.gbl...
> i stop the service and start it again, the db is alwais loading, i found
in[vbcol=seagreen]
> the log this message:
> Bypassing recovery for database 'db_rsnd' because it is marked IN LOAD.
> what have i to do?
> i'd like to know if i can delete the db from the server, but i cant do it
> from the manager because it is loading and i suppose i cant delete it from
> the console too. is there a way to delete the "row" in the master db that
> let it know that my db exists? i hope you understand what i mean.
> Carlo
> --
>
> ********************************************
> Carlo Marcocci
> Istituto Nazionale di Geofisica e Vulcanologia
> Via di Vigna Murata 605, 00143 Roma
> Tel. +39-6-51860391
> Fax. +39-6-51860507
> mailto: marcocci@.ingv.it
> ******************************************** L&P
> "Keith Kratochvil" <sqlguy.back2u@.comcast.net> ha scritto nel messaggio
> news:ufwtZL9fEHA.3024@.TK2MSFTNGP10.phx.gbl...
gone[vbcol=seagreen]
> by
wait[vbcol=seagreen]
> Manager?
specific[vbcol=seagreen]
how
>
|||By now you have fixed your problem. Some added thoughts.
I had a similar issue running SQL Server on a small PC that runs 24x7 (far
too little memory). There were times when a process that normally took 15
minutes ran for more than 3 hours.
1. Sometimes a reboot would speed up the process. Evidently, SQL Server
would grow and grow far beyond the physical memory. The PC spent all its
time paging memory in and out. There is a property to prevent this and set
the maximum memory that SQL Server can use.
2. I also had to set logging to a simple type rather than the full logging.
This is not a production database and we perform daily backups since it is
small. Simple logging is all that is required. With full logging, my tiny
databases (under 50 MB) grew to almost a gigabyte.
3. Wrote a stored procedure that runs in the SQL Server job scheduler every
night that performs a reindex on every table, then gets rid of the log ,
then shrinks the database. Issue has pretty much gone away.
"Carlo" <marcocci@.ingv.it> wrote in message
news:utG3YN8fEHA.704@.TK2MSFTNGP09.phx.gbl...
> Hi
> i started a restore on a little db, it is still running (more than 15
mins),
> how can i understand what is it doing?
> Carlo
> --
>
>
restore problem
Hi
i started a restore on a little db, it is still running (more than 15 mins),
how can i understand what is it doing?
Carlo
--How little is the database?
In the future you can use the WITH STATS option to show you the percent
complete.
I am guessing that the SQL Server's disks are busy creating the database
files that will hold the data.
--
Keith
"Carlo" <marcocci@.ingv.it> wrote in message
news:utG3YN8fEHA.704@.TK2MSFTNGP09.phx.gbl...
> Hi
> i started a restore on a little db, it is still running (more than 15
mins),
> how can i understand what is it doing?
> Carlo
> --
>
>|||the size of db is around 9 mb, it is a test db, it is still loading, how can
i stop the restore'|||Are you able to see the new data/log files created in OS?
Also check to see if there's blocks.
"Carlo" <marcocci@.ingv.it> wrote in message
news:%23KaggZ8fEHA.2984@.tk2msftngp13.phx.gbl...
> the size of db is around 9 mb, it is a test db, it is still loading, how
can
> i stop the restore'
>|||9MB. That is darn small. It has not finished yet? 22 minutes have gone by
since your original post and your second post. That is a too long to wait
for a 9MB database.
What did you use to begin the restore? Query Analyzer? Enterprise Manager?
Perhaps you could try closing the app. You could also kill that specific
connection, but that would be harsh.
--
Keith
"Carlo" <marcocci@.ingv.it> wrote in message
news:%23KaggZ8fEHA.2984@.tk2msftngp13.phx.gbl...
> the size of db is around 9 mb, it is a test db, it is still loading, how
can
> i stop the restore'
>|||i stop the service and start it again, the db is alwais loading, i found in
the log this message:
Bypassing recovery for database 'db_rsnd' because it is marked IN LOAD.
what have i to do'
i'd like to know if i can delete the db from the server, but i cant do it
from the manager because it is loading and i suppose i cant delete it from
the console too. is there a way to delete the "row" in the master db that
let it know that my db exists? i hope you understand what i mean.
Carlo
--
********************************************
Carlo Marcocci
Istituto Nazionale di Geofisica e Vulcanologia
Via di Vigna Murata 605, 00143 Roma
Tel. +39-6-51860391
Fax. +39-6-51860507
mailto: marcocci@.ingv.it
******************************************** L&P
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> ha scritto nel messaggio
news:ufwtZL9fEHA.3024@.TK2MSFTNGP10.phx.gbl...
> 9MB. That is darn small. It has not finished yet? 22 minutes have gone
by
> since your original post and your second post. That is a too long to wait
> for a 9MB database.
> What did you use to begin the restore? Query Analyzer? Enterprise
Manager?
> Perhaps you could try closing the app. You could also kill that specific
> connection, but that would be harsh.
> --
> Keith
>
> "Carlo" <marcocci@.ingv.it> wrote in message
> news:%23KaggZ8fEHA.2984@.tk2msftngp13.phx.gbl...
> > the size of db is around 9 mb, it is a test db, it is still loading, how
> can
> > i stop the restore'
> >
> >
>|||may i use this '
UPDATE sysdatabases
SET status=16
WHERE name='daCancellare'
does it change anything'
********************************************
Carlo Marcocci
Istituto Nazionale di Geofisica e Vulcanologia
Via di Vigna Murata 605, 00143 Roma
Tel. +39-6-51860391
Fax. +39-6-51860507
mailto: marcocci@.ingv.it
******************************************** L&P
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> ha scritto nel messaggio
news:ufwtZL9fEHA.3024@.TK2MSFTNGP10.phx.gbl...
> 9MB. That is darn small. It has not finished yet? 22 minutes have gone
by
> since your original post and your second post. That is a too long to wait
> for a 9MB database.
> What did you use to begin the restore? Query Analyzer? Enterprise
Manager?
> Perhaps you could try closing the app. You could also kill that specific
> connection, but that would be harsh.
> --
> Keith
>
> "Carlo" <marcocci@.ingv.it> wrote in message
> news:%23KaggZ8fEHA.2984@.tk2msftngp13.phx.gbl...
> > the size of db is around 9 mb, it is a test db, it is still loading, how
> can
> > i stop the restore'
> >
> >
>|||I would try using DROP DATABASE
Information within Books Online (within the SQL Server program group).
--
Keith
"Carlo" <marcocci@.ingv.it> wrote in message
news:OyzQU09fEHA.3916@.TK2MSFTNGP11.phx.gbl...
> may i use this '
> UPDATE sysdatabases
> SET status=16
> WHERE name='daCancellare'
> does it change anything'
>
> --
>
> ********************************************
> Carlo Marcocci
> Istituto Nazionale di Geofisica e Vulcanologia
> Via di Vigna Murata 605, 00143 Roma
> Tel. +39-6-51860391
> Fax. +39-6-51860507
> mailto: marcocci@.ingv.it
> ******************************************** L&P
> "Keith Kratochvil" <sqlguy.back2u@.comcast.net> ha scritto nel messaggio
> news:ufwtZL9fEHA.3024@.TK2MSFTNGP10.phx.gbl...
> > 9MB. That is darn small. It has not finished yet? 22 minutes have
gone
> by
> > since your original post and your second post. That is a too long to
wait
> > for a 9MB database.
> >
> > What did you use to begin the restore? Query Analyzer? Enterprise
> Manager?
> > Perhaps you could try closing the app. You could also kill that
specific
> > connection, but that would be harsh.
> >
> > --
> > Keith
> >
> >
> > "Carlo" <marcocci@.ingv.it> wrote in message
> > news:%23KaggZ8fEHA.2984@.tk2msftngp13.phx.gbl...
> > > the size of db is around 9 mb, it is a test db, it is still loading,
how
> > can
> > > i stop the restore'
> > >
> > >
> >
>|||Read up on DROP DATABASE within Books Online (within the SQL Server program
group).
--
Keith
"Carlo" <marcocci@.ingv.it> wrote in message
news:ex%23jop9fEHA.3932@.TK2MSFTNGP09.phx.gbl...
> i stop the service and start it again, the db is alwais loading, i found
in
> the log this message:
> Bypassing recovery for database 'db_rsnd' because it is marked IN LOAD.
> what have i to do'
> i'd like to know if i can delete the db from the server, but i cant do it
> from the manager because it is loading and i suppose i cant delete it from
> the console too. is there a way to delete the "row" in the master db that
> let it know that my db exists? i hope you understand what i mean.
> Carlo
> --
>
> ********************************************
> Carlo Marcocci
> Istituto Nazionale di Geofisica e Vulcanologia
> Via di Vigna Murata 605, 00143 Roma
> Tel. +39-6-51860391
> Fax. +39-6-51860507
> mailto: marcocci@.ingv.it
> ******************************************** L&P
> "Keith Kratochvil" <sqlguy.back2u@.comcast.net> ha scritto nel messaggio
> news:ufwtZL9fEHA.3024@.TK2MSFTNGP10.phx.gbl...
> > 9MB. That is darn small. It has not finished yet? 22 minutes have
gone
> by
> > since your original post and your second post. That is a too long to
wait
> > for a 9MB database.
> >
> > What did you use to begin the restore? Query Analyzer? Enterprise
> Manager?
> > Perhaps you could try closing the app. You could also kill that
specific
> > connection, but that would be harsh.
> >
> > --
> > Keith
> >
> >
> > "Carlo" <marcocci@.ingv.it> wrote in message
> > news:%23KaggZ8fEHA.2984@.tk2msftngp13.phx.gbl...
> > > the size of db is around 9 mb, it is a test db, it is still loading,
how
> > can
> > > i stop the restore'
> > >
> > >
> >
>|||By now you have fixed your problem. Some added thoughts.
I had a similar issue running SQL Server on a small PC that runs 24x7 (far
too little memory). There were times when a process that normally took 15
minutes ran for more than 3 hours.
1. Sometimes a reboot would speed up the process. Evidently, SQL Server
would grow and grow far beyond the physical memory. The PC spent all its
time paging memory in and out. There is a property to prevent this and set
the maximum memory that SQL Server can use.
2. I also had to set logging to a simple type rather than the full logging.
This is not a production database and we perform daily backups since it is
small. Simple logging is all that is required. With full logging, my tiny
databases (under 50 MB) grew to almost a gigabyte.
3. Wrote a stored procedure that runs in the SQL Server job scheduler every
night that performs a reindex on every table, then gets rid of the log ,
then shrinks the database. Issue has pretty much gone away.
"Carlo" <marcocci@.ingv.it> wrote in message
news:utG3YN8fEHA.704@.TK2MSFTNGP09.phx.gbl...
> Hi
> i started a restore on a little db, it is still running (more than 15
mins),
> how can i understand what is it doing?
> Carlo
> --
>
>
i started a restore on a little db, it is still running (more than 15 mins),
how can i understand what is it doing?
Carlo
--How little is the database?
In the future you can use the WITH STATS option to show you the percent
complete.
I am guessing that the SQL Server's disks are busy creating the database
files that will hold the data.
--
Keith
"Carlo" <marcocci@.ingv.it> wrote in message
news:utG3YN8fEHA.704@.TK2MSFTNGP09.phx.gbl...
> Hi
> i started a restore on a little db, it is still running (more than 15
mins),
> how can i understand what is it doing?
> Carlo
> --
>
>|||the size of db is around 9 mb, it is a test db, it is still loading, how can
i stop the restore'|||Are you able to see the new data/log files created in OS?
Also check to see if there's blocks.
"Carlo" <marcocci@.ingv.it> wrote in message
news:%23KaggZ8fEHA.2984@.tk2msftngp13.phx.gbl...
> the size of db is around 9 mb, it is a test db, it is still loading, how
can
> i stop the restore'
>|||9MB. That is darn small. It has not finished yet? 22 minutes have gone by
since your original post and your second post. That is a too long to wait
for a 9MB database.
What did you use to begin the restore? Query Analyzer? Enterprise Manager?
Perhaps you could try closing the app. You could also kill that specific
connection, but that would be harsh.
--
Keith
"Carlo" <marcocci@.ingv.it> wrote in message
news:%23KaggZ8fEHA.2984@.tk2msftngp13.phx.gbl...
> the size of db is around 9 mb, it is a test db, it is still loading, how
can
> i stop the restore'
>|||i stop the service and start it again, the db is alwais loading, i found in
the log this message:
Bypassing recovery for database 'db_rsnd' because it is marked IN LOAD.
what have i to do'
i'd like to know if i can delete the db from the server, but i cant do it
from the manager because it is loading and i suppose i cant delete it from
the console too. is there a way to delete the "row" in the master db that
let it know that my db exists? i hope you understand what i mean.
Carlo
--
********************************************
Carlo Marcocci
Istituto Nazionale di Geofisica e Vulcanologia
Via di Vigna Murata 605, 00143 Roma
Tel. +39-6-51860391
Fax. +39-6-51860507
mailto: marcocci@.ingv.it
******************************************** L&P
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> ha scritto nel messaggio
news:ufwtZL9fEHA.3024@.TK2MSFTNGP10.phx.gbl...
> 9MB. That is darn small. It has not finished yet? 22 minutes have gone
by
> since your original post and your second post. That is a too long to wait
> for a 9MB database.
> What did you use to begin the restore? Query Analyzer? Enterprise
Manager?
> Perhaps you could try closing the app. You could also kill that specific
> connection, but that would be harsh.
> --
> Keith
>
> "Carlo" <marcocci@.ingv.it> wrote in message
> news:%23KaggZ8fEHA.2984@.tk2msftngp13.phx.gbl...
> > the size of db is around 9 mb, it is a test db, it is still loading, how
> can
> > i stop the restore'
> >
> >
>|||may i use this '
UPDATE sysdatabases
SET status=16
WHERE name='daCancellare'
does it change anything'
********************************************
Carlo Marcocci
Istituto Nazionale di Geofisica e Vulcanologia
Via di Vigna Murata 605, 00143 Roma
Tel. +39-6-51860391
Fax. +39-6-51860507
mailto: marcocci@.ingv.it
******************************************** L&P
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> ha scritto nel messaggio
news:ufwtZL9fEHA.3024@.TK2MSFTNGP10.phx.gbl...
> 9MB. That is darn small. It has not finished yet? 22 minutes have gone
by
> since your original post and your second post. That is a too long to wait
> for a 9MB database.
> What did you use to begin the restore? Query Analyzer? Enterprise
Manager?
> Perhaps you could try closing the app. You could also kill that specific
> connection, but that would be harsh.
> --
> Keith
>
> "Carlo" <marcocci@.ingv.it> wrote in message
> news:%23KaggZ8fEHA.2984@.tk2msftngp13.phx.gbl...
> > the size of db is around 9 mb, it is a test db, it is still loading, how
> can
> > i stop the restore'
> >
> >
>|||I would try using DROP DATABASE
Information within Books Online (within the SQL Server program group).
--
Keith
"Carlo" <marcocci@.ingv.it> wrote in message
news:OyzQU09fEHA.3916@.TK2MSFTNGP11.phx.gbl...
> may i use this '
> UPDATE sysdatabases
> SET status=16
> WHERE name='daCancellare'
> does it change anything'
>
> --
>
> ********************************************
> Carlo Marcocci
> Istituto Nazionale di Geofisica e Vulcanologia
> Via di Vigna Murata 605, 00143 Roma
> Tel. +39-6-51860391
> Fax. +39-6-51860507
> mailto: marcocci@.ingv.it
> ******************************************** L&P
> "Keith Kratochvil" <sqlguy.back2u@.comcast.net> ha scritto nel messaggio
> news:ufwtZL9fEHA.3024@.TK2MSFTNGP10.phx.gbl...
> > 9MB. That is darn small. It has not finished yet? 22 minutes have
gone
> by
> > since your original post and your second post. That is a too long to
wait
> > for a 9MB database.
> >
> > What did you use to begin the restore? Query Analyzer? Enterprise
> Manager?
> > Perhaps you could try closing the app. You could also kill that
specific
> > connection, but that would be harsh.
> >
> > --
> > Keith
> >
> >
> > "Carlo" <marcocci@.ingv.it> wrote in message
> > news:%23KaggZ8fEHA.2984@.tk2msftngp13.phx.gbl...
> > > the size of db is around 9 mb, it is a test db, it is still loading,
how
> > can
> > > i stop the restore'
> > >
> > >
> >
>|||Read up on DROP DATABASE within Books Online (within the SQL Server program
group).
--
Keith
"Carlo" <marcocci@.ingv.it> wrote in message
news:ex%23jop9fEHA.3932@.TK2MSFTNGP09.phx.gbl...
> i stop the service and start it again, the db is alwais loading, i found
in
> the log this message:
> Bypassing recovery for database 'db_rsnd' because it is marked IN LOAD.
> what have i to do'
> i'd like to know if i can delete the db from the server, but i cant do it
> from the manager because it is loading and i suppose i cant delete it from
> the console too. is there a way to delete the "row" in the master db that
> let it know that my db exists? i hope you understand what i mean.
> Carlo
> --
>
> ********************************************
> Carlo Marcocci
> Istituto Nazionale di Geofisica e Vulcanologia
> Via di Vigna Murata 605, 00143 Roma
> Tel. +39-6-51860391
> Fax. +39-6-51860507
> mailto: marcocci@.ingv.it
> ******************************************** L&P
> "Keith Kratochvil" <sqlguy.back2u@.comcast.net> ha scritto nel messaggio
> news:ufwtZL9fEHA.3024@.TK2MSFTNGP10.phx.gbl...
> > 9MB. That is darn small. It has not finished yet? 22 minutes have
gone
> by
> > since your original post and your second post. That is a too long to
wait
> > for a 9MB database.
> >
> > What did you use to begin the restore? Query Analyzer? Enterprise
> Manager?
> > Perhaps you could try closing the app. You could also kill that
specific
> > connection, but that would be harsh.
> >
> > --
> > Keith
> >
> >
> > "Carlo" <marcocci@.ingv.it> wrote in message
> > news:%23KaggZ8fEHA.2984@.tk2msftngp13.phx.gbl...
> > > the size of db is around 9 mb, it is a test db, it is still loading,
how
> > can
> > > i stop the restore'
> > >
> > >
> >
>|||By now you have fixed your problem. Some added thoughts.
I had a similar issue running SQL Server on a small PC that runs 24x7 (far
too little memory). There were times when a process that normally took 15
minutes ran for more than 3 hours.
1. Sometimes a reboot would speed up the process. Evidently, SQL Server
would grow and grow far beyond the physical memory. The PC spent all its
time paging memory in and out. There is a property to prevent this and set
the maximum memory that SQL Server can use.
2. I also had to set logging to a simple type rather than the full logging.
This is not a production database and we perform daily backups since it is
small. Simple logging is all that is required. With full logging, my tiny
databases (under 50 MB) grew to almost a gigabyte.
3. Wrote a stored procedure that runs in the SQL Server job scheduler every
night that performs a reindex on every table, then gets rid of the log ,
then shrinks the database. Issue has pretty much gone away.
"Carlo" <marcocci@.ingv.it> wrote in message
news:utG3YN8fEHA.704@.TK2MSFTNGP09.phx.gbl...
> Hi
> i started a restore on a little db, it is still running (more than 15
mins),
> how can i understand what is it doing?
> Carlo
> --
>
>
Subscribe to:
Posts (Atom)