Question related to recovery of SQL Server database..

In the event of SQL Server recovery... I have listed the following steps
(not detailed) as per reading SQL Server books online.
Step1. Install the SQL Server and related Service Packs
Step2. Restore the master database.
Step3. Restore the msdb (to restore the DTS packages and job schedules.)
Stpe4. Restore other system databases if it is required (optional).
Step5. Restore the user databases one after the other.. (Full backup,
differential backup and transactional backup..)
My question is..
After restoring the MASTER database, all the user databases information is
restored in the master database.
So.. Is it possible to restore the user database as the entries exist in
MASTER database? Is it possible to restore the user database just like any
other time that we restore the user database under different database name?
Since I cannot test the complete scenario I am looking for your opinion..
I am using SQL Server 2K.
Thank you all for your opinion.
Hanuman
Hi,
You can restore the user databases in any order. The order will not really
matter. You can also restore the user databases with new name this will add
new entries to sysdatabases, but the old entries in sysdatabases will remain
there. Only issue is incase if you have any logins defaulted to ur old
database
name needs to be changed using SP_defaultdb system stored procedure.
Thanks
Hari
SQL Server MVP
"Hanuman Mishra" <Mishra_Hanuman@.rediffmail.com> wrote in message
news:OpwFwX8ZFHA.4000@.TK2MSFTNGP10.phx.gbl...
>
> In the event of SQL Server recovery... I have listed the following steps
> (not detailed) as per reading SQL Server books online.
> Step1. Install the SQL Server and related Service Packs
> Step2. Restore the master database.
> Step3. Restore the msdb (to restore the DTS packages and job schedules.)
> Stpe4. Restore other system databases if it is required (optional).
> Step5. Restore the user databases one after the other.. (Full backup,
> differential backup and transactional backup..)
>
> My question is..
> After restoring the MASTER database, all the user databases information is
> restored in the master database.
> So.. Is it possible to restore the user database as the entries exist in
> MASTER database? Is it possible to restore the user database just like any
> other time that we restore the user database under different database
> name?
> Since I cannot test the complete scenario I am looking for your opinion..
>
> I am using SQL Server 2K.
> Thank you all for your opinion.
> Hanuman
>

Question related to recovery of SQL Server database..

In the event of SQL Server recovery... I have listed the following steps
(not detailed) as per reading SQL Server books online.
Step1. Install the SQL Server and related Service Packs
Step2. Restore the master database.
Step3. Restore the msdb (to restore the DTS packages and job schedules.)
Stpe4. Restore other system databases if it is required (optional).
Step5. Restore the user databases one after the other.. (Full backup,
differential backup and transactional backup..)
My question is..
After restoring the MASTER database, all the user databases information is
restored in the master database.
So.. Is it possible to restore the user database as the entries exist in
MASTER database? Is it possible to restore the user database just like any
other time that we restore the user database under different database name?
Since I cannot test the complete scenario I am looking for your opinion..
I am using SQL Server 2K.
Thank you all for your opinion.
HanumanHi,
You can restore the user databases in any order. The order will not really
matter. You can also restore the user databases with new name this will add
new entries to sysdatabases, but the old entries in sysdatabases will remain
there. Only issue is incase if you have any logins defaulted to ur old
database
name needs to be changed using SP_defaultdb system stored procedure.
Thanks
Hari
SQL Server MVP
"Hanuman Mishra" <Mishra_Hanuman@.rediffmail.com> wrote in message
news:OpwFwX8ZFHA.4000@.TK2MSFTNGP10.phx.gbl...
>
> In the event of SQL Server recovery... I have listed the following steps
> (not detailed) as per reading SQL Server books online.
> Step1. Install the SQL Server and related Service Packs
> Step2. Restore the master database.
> Step3. Restore the msdb (to restore the DTS packages and job schedules.)
> Stpe4. Restore other system databases if it is required (optional).
> Step5. Restore the user databases one after the other.. (Full backup,
> differential backup and transactional backup..)
>
> My question is..
> After restoring the MASTER database, all the user databases information is
> restored in the master database.
> So.. Is it possible to restore the user database as the entries exist in
> MASTER database? Is it possible to restore the user database just like any
> other time that we restore the user database under different database
> name?
> Since I cannot test the complete scenario I am looking for your opinion..
>
> I am using SQL Server 2K.
> Thank you all for your opinion.
> Hanuman
>

Question related to recovery of SQL Server database..

In the event of SQL Server recovery... I have listed the following steps
(not detailed) as per reading SQL Server books online.
Step1. Install the SQL Server and related Service Packs
Step2. Restore the master database.
Step3. Restore the msdb (to restore the DTS packages and job schedules.)
Stpe4. Restore other system databases if it is required (optional).
Step5. Restore the user databases one after the other.. (Full backup,
differential backup and transactional backup..)
My question is..
After restoring the MASTER database, all the user databases information is
restored in the master database.
So.. Is it possible to restore the user database as the entries exist in
MASTER database? Is it possible to restore the user database just like any
other time that we restore the user database under different database name?
Since I cannot test the complete scenario I am looking for your opinion..
I am using SQL Server 2K.
Thank you all for your opinion.
HanumanHi,
You can restore the user databases in any order. The order will not really
matter. You can also restore the user databases with new name this will add
new entries to sysdatabases, but the old entries in sysdatabases will remain
there. Only issue is incase if you have any logins defaulted to ur old
database
name needs to be changed using SP_defaultdb system stored procedure.
Thanks
Hari
SQL Server MVP
"Hanuman Mishra" <Mishra_Hanuman@.rediffmail.com> wrote in message
news:OpwFwX8ZFHA.4000@.TK2MSFTNGP10.phx.gbl...
>
> In the event of SQL Server recovery... I have listed the following steps
> (not detailed) as per reading SQL Server books online.
> Step1. Install the SQL Server and related Service Packs
> Step2. Restore the master database.
> Step3. Restore the msdb (to restore the DTS packages and job schedules.)
> Stpe4. Restore other system databases if it is required (optional).
> Step5. Restore the user databases one after the other.. (Full backup,
> differential backup and transactional backup..)
>
> My question is..
> After restoring the MASTER database, all the user databases information is
> restored in the master database.
> So.. Is it possible to restore the user database as the entries exist in
> MASTER database? Is it possible to restore the user database just like any
> other time that we restore the user database under different database
> name?
> Since I cannot test the complete scenario I am looking for your opinion..
>
> I am using SQL Server 2K.
> Thank you all for your opinion.
> Hanuman
>

question on recovery sql server 2000

Hi
I am using SQL 2000 std edition and hence using custom scripts to
restore the DB using standby file. I am backing up T-LOGs every 30 mins on
production and copying them on a network location which is accessible to
standby machine.
I run a job on standby machine which applies the transaction logs every 30
mins by checking in backmediaset & backupmediafamily tables of Production. DB
is running in read only and is working.
Question : In case my Production machine goes down and does not come up how
can I start the Standby "with data loss" if it has already appiled the last
T-logs generated on production.
Since Produciton (primary) is down I can not backup the last T-log.
Thanks
Mangesh
From BOL
This example sets up the MyNwind database on a standby server. The database
can be used in read-only mode between restore operations.
-- Restore the initial database backup on the standby server.
USE master
GO
RESTORE DATABASE MyNwind
FROM MyNwind_1
WITH STANDBY = 'c:\undo.ldf'
GO
-- Apply the first transaction log backup.
RESTORE LOG MyNwind
FROM MyNwind_log1
WITH STANDBY = 'c:\undo.ldf'
GO
-- Apply the next transaction log backup.
RESTORE LOG MyNwind
FROM MyNwind_log2
WITH STANDBY = 'c:\undo.ldf'
GO
-- Repeat for each transaction log backup created on the
-- primary server.
-- Time elapses.. .. ..
-- The primary server has failed. Back up the
-- active transaction log on the primary server.
BACKUP LOG MyNwind
TO MyNwind_log3
WITH NO_TRUNCATE
GO
-- Apply the final (active) transaction log backup
-- to the standby server. All preceding transaction
-- log backups must have been already applied.
RESTORE LOG MyNwind
FROM MyNwind_log3
WITH STANDBY = 'c:\undo.ldf'
GO
-- Recover the database on the standby server,
-- making it available for normal operations.
RESTORE DATABASE MyNwind
WITH RECOVERY
GO
"Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in
message news:72D84926-67E3-4A3F-A011-E5F5A6ACA8CC@.microsoft.com...
> Hi
> I am using SQL 2000 std edition and hence using custom scripts to
> restore the DB using standby file. I am backing up T-LOGs every 30 mins on
> production and copying them on a network location which is accessible to
> standby machine.
> I run a job on standby machine which applies the transaction logs every 30
> mins by checking in backmediaset & backupmediafamily tables of Production.
DB
> is running in read only and is working.
> Question : In case my Production machine goes down and does not come up
how
> can I start the Standby "with data loss" if it has already appiled the
last
> T-logs generated on production.
> Since Produciton (primary) is down I can not backup the last T-log.
> Thanks
> Mangesh
>
|||So you are continuously doing RESTORE WITH STANDBY? And you now wand to make the database fully
accessible? If so:
RESTORE DATABASE dbname WITH RECOVERY
No actual restore is performed, only the recovery work to get it out of standby mode.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in message
news:72D84926-67E3-4A3F-A011-E5F5A6ACA8CC@.microsoft.com...
> Hi
> I am using SQL 2000 std edition and hence using custom scripts to
> restore the DB using standby file. I am backing up T-LOGs every 30 mins on
> production and copying them on a network location which is accessible to
> standby machine.
> I run a job on standby machine which applies the transaction logs every 30
> mins by checking in backmediaset & backupmediafamily tables of Production. DB
> is running in read only and is working.
> Question : In case my Production machine goes down and does not come up how
> can I start the Standby "with data loss" if it has already appiled the last
> T-logs generated on production.
> Since Produciton (primary) is down I can not backup the last T-log.
> Thanks
> Mangesh
>
|||Yes. I am doing a continuous restoration of my standby database using standby
file.
Thanks for help.
"Tibor Karaszi" wrote:

> So you are continuously doing RESTORE WITH STANDBY? And you now wand to make the database fully
> accessible? If so:
> RESTORE DATABASE dbname WITH RECOVERY
> No actual restore is performed, only the recovery work to get it out of standby mode.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in message
> news:72D84926-67E3-4A3F-A011-E5F5A6ACA8CC@.microsoft.com...
>
>

question on recovery sql server 2000

Hi
I am using SQL 2000 std edition and hence using custom scripts to
restore the DB using standby file. I am backing up T-LOGs every 30 mins on
production and copying them on a network location which is accessible to
standby machine.
I run a job on standby machine which applies the transaction logs every 30
mins by checking in backmediaset & backupmediafamily tables of Production. D
B
is running in read only and is working.
Question : In case my Production machine goes down and does not come up how
can I start the Standby "with data loss" if it has already appiled the last
T-logs generated on production.
Since Produciton (primary) is down I can not backup the last T-log.
Thanks
MangeshFrom BOL
This example sets up the MyNwind database on a standby server. The database
can be used in read-only mode between restore operations.
-- Restore the initial database backup on the standby server.
USE master
GO
RESTORE DATABASE MyNwind
FROM MyNwind_1
WITH STANDBY = 'c:\undo.ldf'
GO
-- Apply the first transaction log backup.
RESTORE LOG MyNwind
FROM MyNwind_log1
WITH STANDBY = 'c:\undo.ldf'
GO
-- Apply the next transaction log backup.
RESTORE LOG MyNwind
FROM MyNwind_log2
WITH STANDBY = 'c:\undo.ldf'
GO
-- Repeat for each transaction log backup created on the
-- primary server.
--
-- Time elapses.. .. ..
--
-- The primary server has failed. Back up the
-- active transaction log on the primary server.
BACKUP LOG MyNwind
TO MyNwind_log3
WITH NO_TRUNCATE
GO
-- Apply the final (active) transaction log backup
-- to the standby server. All preceding transaction
-- log backups must have been already applied.
RESTORE LOG MyNwind
FROM MyNwind_log3
WITH STANDBY = 'c:\undo.ldf'
GO
-- Recover the database on the standby server,
-- making it available for normal operations.
RESTORE DATABASE MyNwind
WITH RECOVERY
GO
"Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in
message news:72D84926-67E3-4A3F-A011-E5F5A6ACA8CC@.microsoft.com...
> Hi
> I am using SQL 2000 std edition and hence using custom scripts to
> restore the DB using standby file. I am backing up T-LOGs every 30 mins on
> production and copying them on a network location which is accessible to
> standby machine.
> I run a job on standby machine which applies the transaction logs every 30
> mins by checking in backmediaset & backupmediafamily tables of Production.
DB
> is running in read only and is working.
> Question : In case my Production machine goes down and does not come up
how
> can I start the Standby "with data loss" if it has already appiled the
last
> T-logs generated on production.
> Since Produciton (primary) is down I can not backup the last T-log.
> Thanks
> Mangesh
>|||So you are continuously doing RESTORE WITH STANDBY? And you now wand to make
the database fully
accessible? If so:
RESTORE DATABASE dbname WITH RECOVERY
No actual restore is performed, only the recovery work to get it out of stan
dby mode.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in me
ssage
news:72D84926-67E3-4A3F-A011-E5F5A6ACA8CC@.microsoft.com...
> Hi
> I am using SQL 2000 std edition and hence using custom scripts to
> restore the DB using standby file. I am backing up T-LOGs every 30 mins on
> production and copying them on a network location which is accessible to
> standby machine.
> I run a job on standby machine which applies the transaction logs every 30
> mins by checking in backmediaset & backupmediafamily tables of Production.
DB
> is running in read only and is working.
> Question : In case my Production machine goes down and does not come up h
ow
> can I start the Standby "with data loss" if it has already appiled the las
t
> T-logs generated on production.
> Since Produciton (primary) is down I can not backup the last T-log.
> Thanks
> Mangesh
>|||Yes. I am doing a continuous restoration of my standby database using standb
y
file.
Thanks for help.
"Tibor Karaszi" wrote:

> So you are continuously doing RESTORE WITH STANDBY? And you now wand to ma
ke the database fully
> accessible? If so:
> RESTORE DATABASE dbname WITH RECOVERY
> No actual restore is performed, only the recovery work to get it out of st
andby mode.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in
message
> news:72D84926-67E3-4A3F-A011-E5F5A6ACA8CC@.microsoft.com...
>
>

question on recovery sql server 2000

Hi
I am using SQL 2000 std edition and hence using custom scripts to
restore the DB using standby file. I am backing up T-LOGs every 30 mins on
production and copying them on a network location which is accessible to
standby machine.
I run a job on standby machine which applies the transaction logs every 30
mins by checking in backmediaset & backupmediafamily tables of Production. DB
is running in read only and is working.
Question : In case my Production machine goes down and does not come up how
can I start the Standby "with data loss" if it has already appiled the last
T-logs generated on production.
Since Produciton (primary) is down I can not backup the last T-log.
Thanks
MangeshFrom BOL
This example sets up the MyNwind database on a standby server. The database
can be used in read-only mode between restore operations.
-- Restore the initial database backup on the standby server.
USE master
GO
RESTORE DATABASE MyNwind
FROM MyNwind_1
WITH STANDBY = 'c:\undo.ldf'
GO
-- Apply the first transaction log backup.
RESTORE LOG MyNwind
FROM MyNwind_log1
WITH STANDBY = 'c:\undo.ldf'
GO
-- Apply the next transaction log backup.
RESTORE LOG MyNwind
FROM MyNwind_log2
WITH STANDBY = 'c:\undo.ldf'
GO
-- Repeat for each transaction log backup created on the
-- primary server.
--
-- Time elapses.. .. ..
--
-- The primary server has failed. Back up the
-- active transaction log on the primary server.
BACKUP LOG MyNwind
TO MyNwind_log3
WITH NO_TRUNCATE
GO
-- Apply the final (active) transaction log backup
-- to the standby server. All preceding transaction
-- log backups must have been already applied.
RESTORE LOG MyNwind
FROM MyNwind_log3
WITH STANDBY = 'c:\undo.ldf'
GO
-- Recover the database on the standby server,
-- making it available for normal operations.
RESTORE DATABASE MyNwind
WITH RECOVERY
GO
"Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in
message news:72D84926-67E3-4A3F-A011-E5F5A6ACA8CC@.microsoft.com...
> Hi
> I am using SQL 2000 std edition and hence using custom scripts to
> restore the DB using standby file. I am backing up T-LOGs every 30 mins on
> production and copying them on a network location which is accessible to
> standby machine.
> I run a job on standby machine which applies the transaction logs every 30
> mins by checking in backmediaset & backupmediafamily tables of Production.
DB
> is running in read only and is working.
> Question : In case my Production machine goes down and does not come up
how
> can I start the Standby "with data loss" if it has already appiled the
last
> T-logs generated on production.
> Since Produciton (primary) is down I can not backup the last T-log.
> Thanks
> Mangesh
>|||So you are continuously doing RESTORE WITH STANDBY? And you now wand to make the database fully
accessible? If so:
RESTORE DATABASE dbname WITH RECOVERY
No actual restore is performed, only the recovery work to get it out of standby mode.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in message
news:72D84926-67E3-4A3F-A011-E5F5A6ACA8CC@.microsoft.com...
> Hi
> I am using SQL 2000 std edition and hence using custom scripts to
> restore the DB using standby file. I am backing up T-LOGs every 30 mins on
> production and copying them on a network location which is accessible to
> standby machine.
> I run a job on standby machine which applies the transaction logs every 30
> mins by checking in backmediaset & backupmediafamily tables of Production. DB
> is running in read only and is working.
> Question : In case my Production machine goes down and does not come up how
> can I start the Standby "with data loss" if it has already appiled the last
> T-logs generated on production.
> Since Produciton (primary) is down I can not backup the last T-log.
> Thanks
> Mangesh
>|||Yes. I am doing a continuous restoration of my standby database using standby
file.
Thanks for help.
"Tibor Karaszi" wrote:
> So you are continuously doing RESTORE WITH STANDBY? And you now wand to make the database fully
> accessible? If so:
> RESTORE DATABASE dbname WITH RECOVERY
> No actual restore is performed, only the recovery work to get it out of standby mode.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in message
> news:72D84926-67E3-4A3F-A011-E5F5A6ACA8CC@.microsoft.com...
> > Hi
> >
> > I am using SQL 2000 std edition and hence using custom scripts to
> > restore the DB using standby file. I am backing up T-LOGs every 30 mins on
> > production and copying them on a network location which is accessible to
> > standby machine.
> >
> > I run a job on standby machine which applies the transaction logs every 30
> > mins by checking in backmediaset & backupmediafamily tables of Production. DB
> > is running in read only and is working.
> >
> > Question : In case my Production machine goes down and does not come up how
> > can I start the Standby "with data loss" if it has already appiled the last
> > T-logs generated on production.
> > Since Produciton (primary) is down I can not backup the last T-log.
> >
> > Thanks
> > Mangesh
> >
> >
>
>

question on memory

Win2K Advanced Server
SQL2K Enterprise
I need to set up 1 big fat Disaster Recovery box for my 6 production boxes.
I will do this by putting 6 instances of SQL on the DR box. I know that
there is an 8 gig max (using AWE) limit. But what I don't know is can each
instance have its own 8 gigs, or do all 6 instances need to share the same 8
gigs? Also, would switching to Win2K3 help me to be able to use more RAM?
Basically, I dont want to tell anyone to order 48 gigs or RAM (6 instances
with 8 gigs each) when Im only going to be able to use 8.
TIA, ChrisR
Chris,
Each instance can use it's own block of memory but I don't think Win2K Adv
server can use more than 8GB. I believe you need Data Center for more than
8GB. Certainly for 48GB. Do you need 8GB for each instance? Do each of
the 6 Prod boxes have 8GB now? Does your DR plan say you need to run all 6
instances on the one box at the same time? Seems kind of silly to have 6
individual boxes in prod and expect to run all 6 instances at once on one
box. In any case Win2K3 will not allow you to use any more ram but it does
have certain performance enhancements over 2K that you should take advantage
of.
Andrew J. Kelly SQL MVP
"ChrisR" <noemail@.bla.com> wrote in message
news:euDyuWiYFHA.2380@.tk2msftngp13.phx.gbl...
> Win2K Advanced Server
> SQL2K Enterprise
> I need to set up 1 big fat Disaster Recovery box for my 6 production
> boxes. I will do this by putting 6 instances of SQL on the DR box. I know
> that there is an 8 gig max (using AWE) limit. But what I don't know is can
> each instance have its own 8 gigs, or do all 6 instances need to share the
> same 8 gigs? Also, would switching to Win2K3 help me to be able to use
> more RAM? Basically, I dont want to tell anyone to order 48 gigs or RAM (6
> instances with 8 gigs each) when Im only going to be able to use 8.
>
> TIA, ChrisR
>
|||I typed out a reply yesterday but I guess I forgot to hit the reply button.
No I don't need 8 gigs per instance, but 6 boxes sharing 8 gigs wont do
either. Yes, all of them may need to be on at once.
Thanks Andrew.
CR
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23MHGH$jYFHA.1152@.tk2msftngp13.phx.gbl...
> Chris,
> Each instance can use it's own block of memory but I don't think Win2K Adv
> server can use more than 8GB. I believe you need Data Center for more
> than 8GB. Certainly for 48GB. Do you need 8GB for each instance? Do
> each of the 6 Prod boxes have 8GB now? Does your DR plan say you need to
> run all 6 instances on the one box at the same time? Seems kind of silly
> to have 6 individual boxes in prod and expect to run all 6 instances at
> once on one box. In any case Win2K3 will not allow you to use any more
> ram but it does have certain performance enhancements over 2K that you
> should take advantage of.
> --
> Andrew J. Kelly SQL MVP
>
> "ChrisR" <noemail@.bla.com> wrote in message
> news:euDyuWiYFHA.2380@.tk2msftngp13.phx.gbl...
>

question on memory

Win2K Advanced Server
SQL2K Enterprise
I need to set up 1 big fat Disaster Recovery box for my 6 production boxes.
I will do this by putting 6 instances of SQL on the DR box. I know that
there is an 8 gig max (using AWE) limit. But what I don't know is can each
instance have its own 8 gigs, or do all 6 instances need to share the same 8
gigs? Also, would switching to Win2K3 help me to be able to use more RAM?
Basically, I dont want to tell anyone to order 48 gigs or RAM (6 instances
with 8 gigs each) when Im only going to be able to use 8.
TIA, ChrisRChris,
Each instance can use it's own block of memory but I don't think Win2K Adv
server can use more than 8GB. I believe you need Data Center for more than
8GB. Certainly for 48GB. Do you need 8GB for each instance? Do each of
the 6 Prod boxes have 8GB now? Does your DR plan say you need to run all 6
instances on the one box at the same time? Seems kind of silly to have 6
individual boxes in prod and expect to run all 6 instances at once on one
box. In any case Win2K3 will not allow you to use any more ram but it does
have certain performance enhancements over 2K that you should take advantage
of.
--
Andrew J. Kelly SQL MVP
"ChrisR" <noemail@.bla.com> wrote in message
news:euDyuWiYFHA.2380@.tk2msftngp13.phx.gbl...
> Win2K Advanced Server
> SQL2K Enterprise
> I need to set up 1 big fat Disaster Recovery box for my 6 production
> boxes. I will do this by putting 6 instances of SQL on the DR box. I know
> that there is an 8 gig max (using AWE) limit. But what I don't know is can
> each instance have its own 8 gigs, or do all 6 instances need to share the
> same 8 gigs? Also, would switching to Win2K3 help me to be able to use
> more RAM? Basically, I dont want to tell anyone to order 48 gigs or RAM (6
> instances with 8 gigs each) when Im only going to be able to use 8.
>
> TIA, ChrisR
>|||I typed out a reply yesterday but I guess I forgot to hit the reply button.
No I don't need 8 gigs per instance, but 6 boxes sharing 8 gigs wont do
either. Yes, all of them may need to be on at once.
Thanks Andrew.
CR
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23MHGH$jYFHA.1152@.tk2msftngp13.phx.gbl...
> Chris,
> Each instance can use it's own block of memory but I don't think Win2K Adv
> server can use more than 8GB. I believe you need Data Center for more
> than 8GB. Certainly for 48GB. Do you need 8GB for each instance? Do
> each of the 6 Prod boxes have 8GB now? Does your DR plan say you need to
> run all 6 instances on the one box at the same time? Seems kind of silly
> to have 6 individual boxes in prod and expect to run all 6 instances at
> once on one box. In any case Win2K3 will not allow you to use any more
> ram but it does have certain performance enhancements over 2K that you
> should take advantage of.
> --
> Andrew J. Kelly SQL MVP
>
> "ChrisR" <noemail@.bla.com> wrote in message
> news:euDyuWiYFHA.2380@.tk2msftngp13.phx.gbl...
>> Win2K Advanced Server
>> SQL2K Enterprise
>> I need to set up 1 big fat Disaster Recovery box for my 6 production
>> boxes. I will do this by putting 6 instances of SQL on the DR box. I know
>> that there is an 8 gig max (using AWE) limit. But what I don't know is
>> can each instance have its own 8 gigs, or do all 6 instances need to
>> share the same 8 gigs? Also, would switching to Win2K3 help me to be able
>> to use more RAM? Basically, I dont want to tell anyone to order 48 gigs
>> or RAM (6 instances with 8 gigs each) when Im only going to be able to
>> use 8.
>>
>> TIA, ChrisR
>

question on memory

Win2K Advanced Server
SQL2K Enterprise
I need to set up 1 big fat Disaster Recovery box for my 6 production boxes.
I will do this by putting 6 instances of SQL on the DR box. I know that
there is an 8 gig max (using AWE) limit. But what I don't know is can each
instance have its own 8 gigs, or do all 6 instances need to share the same 8
gigs? Also, would switching to Win2K3 help me to be able to use more RAM?
Basically, I dont want to tell anyone to order 48 gigs or RAM (6 instances
with 8 gigs each) when Im only going to be able to use 8.
TIA, ChrisRChris,
Each instance can use it's own block of memory but I don't think Win2K Adv
server can use more than 8GB. I believe you need Data Center for more than
8GB. Certainly for 48GB. Do you need 8GB for each instance? Do each of
the 6 Prod boxes have 8GB now? Does your DR plan say you need to run all 6
instances on the one box at the same time? Seems kind of silly to have 6
individual boxes in prod and expect to run all 6 instances at once on one
box. In any case Win2K3 will not allow you to use any more ram but it does
have certain performance enhancements over 2K that you should take advantage
of.
Andrew J. Kelly SQL MVP
"ChrisR" <noemail@.bla.com> wrote in message
news:euDyuWiYFHA.2380@.tk2msftngp13.phx.gbl...
> Win2K Advanced Server
> SQL2K Enterprise
> I need to set up 1 big fat Disaster Recovery box for my 6 production
> boxes. I will do this by putting 6 instances of SQL on the DR box. I know
> that there is an 8 gig max (using AWE) limit. But what I don't know is can
> each instance have its own 8 gigs, or do all 6 instances need to share the
> same 8 gigs? Also, would switching to Win2K3 help me to be able to use
> more RAM? Basically, I dont want to tell anyone to order 48 gigs or RAM (6
> instances with 8 gigs each) when Im only going to be able to use 8.
>
> TIA, ChrisR
>|||I typed out a reply yesterday but I guess I forgot to hit the reply button.
No I don't need 8 gigs per instance, but 6 boxes sharing 8 gigs wont do
either. Yes, all of them may need to be on at once.
Thanks Andrew.
CR
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23MHGH$jYFHA.1152@.tk2msftngp13.phx.gbl...
> Chris,
> Each instance can use it's own block of memory but I don't think Win2K Adv
> server can use more than 8GB. I believe you need Data Center for more
> than 8GB. Certainly for 48GB. Do you need 8GB for each instance? Do
> each of the 6 Prod boxes have 8GB now? Does your DR plan say you need to
> run all 6 instances on the one box at the same time? Seems kind of silly
> to have 6 individual boxes in prod and expect to run all 6 instances at
> once on one box. In any case Win2K3 will not allow you to use any more
> ram but it does have certain performance enhancements over 2K that you
> should take advantage of.
> --
> Andrew J. Kelly SQL MVP
>
> "ChrisR" <noemail@.bla.com> wrote in message
> news:euDyuWiYFHA.2380@.tk2msftngp13.phx.gbl...
>

question on changing recovery model on DB

Hi,
I've got several production DBs that I want to change the recovery model
on from simple to full. Are there any caveats I need to be aware of in
making this change? Or is it just a matter of selecting the 'Full' recovery
model under the 'Options' tab of the DBs Properties and hitting the 'OK'
button? Thanks.
Make sure you set up log backup jobs for the databases to prevent the log
file sizes getting out of hand.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"mb" <mb@.discussions.microsoft.com> wrote in message
news:2547FAF9-8BB6-407C-AFCA-E5D2F9082EB0@.microsoft.com...
> Hi,
> I've got several production DBs that I want to change the recovery model
> on from simple to full. Are there any caveats I need to be aware of in
> making this change? Or is it just a matter of selecting the 'Full'
> recovery
> model under the 'Options' tab of the DBs Properties and hitting the 'OK'
> button? Thanks.
|||mb wrote:
> Hi,
> I've got several production DBs that I want to change the recovery
> model on from simple to full. Are there any caveats I need to be
> aware of in making this change? Or is it just a matter of selecting
> the 'Full' recovery model under the 'Options' tab of the DBs
> Properties and hitting the 'OK' button? Thanks.
You must immediately perform a Full Backup or your t-logs will still get
truncated every checkpoint.
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||Hi,
Once you change your database from SIMPLE to FULL recovery model, you need
to recreate your backup chain by doing:-
1. A Full databaase backup
2. Schedule a transaction log backup frequently
In FULL recovery you need to perform the log backup, this will be helpful to
recover the database point-in-time as
well as help you to keep your LDF file size in control.
Have a look into Recovery model topic in books online for more detail.
Thanks
Hari
SQL SERVER MVP
"mb" <mb@.discussions.microsoft.com> wrote in message
news:2547FAF9-8BB6-407C-AFCA-E5D2F9082EB0@.microsoft.com...
> Hi,
> I've got several production DBs that I want to change the recovery model
> on from simple to full. Are there any caveats I need to be aware of in
> making this change? Or is it just a matter of selecting the 'Full'
> recovery
> model under the 'Options' tab of the DBs Properties and hitting the 'OK'
> button? Thanks.

question on changing recovery model on DB

Hi,
I've got several production DBs that I want to change the recovery model
on from simple to full. Are there any caveats I need to be aware of in
making this change? Or is it just a matter of selecting the 'Full' recovery
model under the 'Options' tab of the DBs Properties and hitting the 'OK'
button? Thanks.Make sure you set up log backup jobs for the databases to prevent the log
file sizes getting out of hand.
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"mb" <mb@.discussions.microsoft.com> wrote in message
news:2547FAF9-8BB6-407C-AFCA-E5D2F9082EB0@.microsoft.com...
> Hi,
> I've got several production DBs that I want to change the recovery model
> on from simple to full. Are there any caveats I need to be aware of in
> making this change? Or is it just a matter of selecting the 'Full'
> recovery
> model under the 'Options' tab of the DBs Properties and hitting the 'OK'
> button? Thanks.|||mb wrote:
> Hi,
> I've got several production DBs that I want to change the recovery
> model on from simple to full. Are there any caveats I need to be
> aware of in making this change? Or is it just a matter of selecting
> the 'Full' recovery model under the 'Options' tab of the DBs
> Properties and hitting the 'OK' button? Thanks.
You must immediately perform a Full Backup or your t-logs will still get
truncated every checkpoint.
--
David Gugick
Quest Software
www.imceda.com
www.quest.com|||Hi,
Once you change your database from SIMPLE to FULL recovery model, you need
to recreate your backup chain by doing:-
1. A Full databaase backup
2. Schedule a transaction log backup frequently
In FULL recovery you need to perform the log backup, this will be helpful to
recover the database point-in-time as
well as help you to keep your LDF file size in control.
Have a look into Recovery model topic in books online for more detail.
Thanks
Hari
SQL SERVER MVP
"mb" <mb@.discussions.microsoft.com> wrote in message
news:2547FAF9-8BB6-407C-AFCA-E5D2F9082EB0@.microsoft.com...
> Hi,
> I've got several production DBs that I want to change the recovery model
> on from simple to full. Are there any caveats I need to be aware of in
> making this change? Or is it just a matter of selecting the 'Full'
> recovery
> model under the 'Options' tab of the DBs Properties and hitting the 'OK'
> button? Thanks.

question on changing recovery model on DB

Hi,
I've got several production DBs that I want to change the recovery model
on from simple to full. Are there any caveats I need to be aware of in
making this change? Or is it just a matter of selecting the 'Full' recovery
model under the 'Options' tab of the DBs Properties and hitting the 'OK'
button? Thanks.Make sure you set up log backup jobs for the databases to prevent the log
file sizes getting out of hand.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"mb" <mb@.discussions.microsoft.com> wrote in message
news:2547FAF9-8BB6-407C-AFCA-E5D2F9082EB0@.microsoft.com...
> Hi,
> I've got several production DBs that I want to change the recovery model
> on from simple to full. Are there any caveats I need to be aware of in
> making this change? Or is it just a matter of selecting the 'Full'
> recovery
> model under the 'Options' tab of the DBs Properties and hitting the 'OK'
> button? Thanks.|||mb wrote:
> Hi,
> I've got several production DBs that I want to change the recovery
> model on from simple to full. Are there any caveats I need to be
> aware of in making this change? Or is it just a matter of selecting
> the 'Full' recovery model under the 'Options' tab of the DBs
> Properties and hitting the 'OK' button? Thanks.
You must immediately perform a Full Backup or your t-logs will still get
truncated every checkpoint.
David Gugick
Quest Software
www.imceda.com
www.quest.com|||Hi,
Once you change your database from SIMPLE to FULL recovery model, you need
to recreate your backup chain by doing:-
1. A Full databaase backup
2. Schedule a transaction log backup frequently
In FULL recovery you need to perform the log backup, this will be helpful to
recover the database point-in-time as
well as help you to keep your LDF file size in control.
Have a look into Recovery model topic in books online for more detail.
Thanks
Hari
SQL SERVER MVP
"mb" <mb@.discussions.microsoft.com> wrote in message
news:2547FAF9-8BB6-407C-AFCA-E5D2F9082EB0@.microsoft.com...
> Hi,
> I've got several production DBs that I want to change the recovery model
> on from simple to full. Are there any caveats I need to be aware of in
> making this change? Or is it just a matter of selecting the 'Full'
> recovery
> model under the 'Options' tab of the DBs Properties and hitting the 'OK'
> button? Thanks.

Question on Backup/Restore

New to SQL Server. is it true, as it seems to be, that SQL Server
cannot do a point in time recovery to a point in time that would exceed
the time of the last transaction log backup?
That is, it cannot use the active log in conjunction with the archived
logs?
Second question, if the server fails and is rebooted, will the system
catalog tables 'remember' the times of the transaction log backups?
Thanks in advance.
Gerry
DataPro wrote:
> New to SQL Server. is it true, as it seems to be, that SQL Server
> cannot do a point in time recovery to a point in time that would exceed
> the time of the last transaction log backup?
> That is, it cannot use the active log in conjunction with the archived
> logs?
> Second question, if the server fails and is rebooted, will the system
> catalog tables 'remember' the times of the transaction log backups?
> Thanks in advance.
> Gerry
>
1. No, it cannot use the "active" log for this. You must take a final
transaction log backup, which will contain the data from the active log,
which you can then use in your point-in-time restore.
2. Yes, this information is retained between reboots.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||
> 1. No, it cannot use the "active" log for this. You must take a final
> transaction log backup, which will contain the data from the active log,
> which you can then use in your point-in-time restore.
> 2. Yes, this information is retained between reboots.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
Thanks Tracy
|||Thanks Tibor;;
OK after I do the restore of a user database...even though the restore
is marked complete on the percentage bar graph the database was marked
as 'Loading'
Baffled me...thought it was because it was being rolled forward
through transaction logs.
I ended up issuing a
RESTORE DATABASE <Database name> WITH RECOVERY and that cleared it up.
But that does not leave me with a warm and fuzzy.
Is this typical behavior in SQL Server?[vbcol=seagreen]
|||Tibor Karaszi wrote:
> When you do RESTORE, you specify NORECOVERY on all restores (db, log, log etc) but the last one.
> Until you've done restore using RECOVERY, the database is in "restoring" state (reported as
> "loading" by earlier tools). If you forgot to do RECOVERY on your last backup, you can handle the
> situation in just the way you did. If you have a case where you do, for instance:
> RESTORE DATABASE ... WITH NORECOVERY
> RESTORE LOG ... WITH NORECOVERY
> RESTORE LOG ... WITH NORECOVERY
> RESTORE LOG ... WITH RECOVERY
> And the database is still in "restoring" state (inaccessible, and not only a refresh problem in EM),
> you should report this as a bug to MS.
> Technical sidenote: The only difference between NORECOVERY and RECOVERY is whether the UNDO phase is
> performed by the restore process. The prior REDO phase is always performed.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Thanks Tibor

Question on Backup/Restore

New to SQL Server. is it true, as it seems to be, that SQL Server
cannot do a point in time recovery to a point in time that would exceed
the time of the last transaction log backup?
That is, it cannot use the active log in conjunction with the archived
logs?
Second question, if the server fails and is rebooted, will the system
catalog tables 'remember' the times of the transaction log backups?
Thanks in advance.
GerryDataPro wrote:
> New to SQL Server. is it true, as it seems to be, that SQL Server
> cannot do a point in time recovery to a point in time that would exceed
> the time of the last transaction log backup?
> That is, it cannot use the active log in conjunction with the archived
> logs?
> Second question, if the server fails and is rebooted, will the system
> catalog tables 'remember' the times of the transaction log backups?
> Thanks in advance.
> Gerry
>
1. No, it cannot use the "active" log for this. You must take a final
transaction log backup, which will contain the data from the active log,
which you can then use in your point-in-time restore.
2. Yes, this information is retained between reboots.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||
> 1. No, it cannot use the "active" log for this. You must take a final
> transaction log backup, which will contain the data from the active log,
> which you can then use in your point-in-time restore.
> 2. Yes, this information is retained between reboots.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
Thanks Tracy|||Note, though that even though you need to do a log backup (you cannot use th
e active log), you still
have plenty of options. What is required is that the log file exists. I'm su
re this is the same as
in other systems. If the database is inaccessible, you can still produce a l
og backup using the
NO_TRUNCATE option of the BACKUP LOG command. And even if you can't start th
e SQL Server, you can
handle this situation:
Create a database on some other SQL Server.
Stop that SQL Server.
Delete the database files.
Copy your "production" ldf file where the newly created log file used to be.
Start SQL Server.
Do a log backup using NO_TRUNCATE.
You have now produced that "last log backup".
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"DataPro" <datapro01@.yahoo.com> wrote in message
news:1165419474.732740.263160@.f1g2000cwa.googlegroups.com...
>
> Thanks Tracy
>|||Thanks Tibor;;
OK after I do the restore of a user database...even though the restore
is marked complete on the percentage bar graph the database was marked
as 'Loading'
Baffled me...thought it was because it was being rolled forward
through transaction logs.
I ended up issuing a
RESTORE DATABASE <Database name> WITH RECOVERY and that cleared it up.
But that does not leave me with a warm and fuzzy.
Is this typical behavior in SQL Server?[vbcol=seagreen]|||When you do RESTORE, you specify NORECOVERY on all restores (db, log, log et
c) but the last one.
Until you've done restore using RECOVERY, the database is in "restoring" sta
te (reported as
"loading" by earlier tools). If you forgot to do RECOVERY on your last backu
p, you can handle the
situation in just the way you did. If you have a case where you do, for inst
ance:
RESTORE DATABASE ... WITH NORECOVERY
RESTORE LOG ... WITH NORECOVERY
RESTORE LOG ... WITH NORECOVERY
RESTORE LOG ... WITH RECOVERY
And the database is still in "restoring" state (inaccessible, and not only a
refresh problem in EM),
you should report this as a bug to MS.
Technical sidenote: The only difference between NORECOVERY and RECOVERY is w
hether the UNDO phase is
performed by the restore process. The prior REDO phase is always performed.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"DataPro" <datapro01@.yahoo.com> wrote in message
news:1165424865.858239.168580@.73g2000cwn.googlegroups.com...
> Thanks Tibor;;
> OK after I do the restore of a user database...even though the restore
> is marked complete on the percentage bar graph the database was marked
> as 'Loading'
> Baffled me...thought it was because it was being rolled forward
> through transaction logs.
> I ended up issuing a
> RESTORE DATABASE <Database name> WITH RECOVERY and that cleared it up.
> But that does not leave me with a warm and fuzzy.
> Is this typical behavior in SQL Server?
>|||Tibor Karaszi wrote:
> When you do RESTORE, you specify NORECOVERY on all restores (db, log, log
etc) but the last one.
> Until you've done restore using RECOVERY, the database is in "restoring" s
tate (reported as
> "loading" by earlier tools). If you forgot to do RECOVERY on your last bac
kup, you can handle the
> situation in just the way you did. If you have a case where you do, for in
stance:
> RESTORE DATABASE ... WITH NORECOVERY
> RESTORE LOG ... WITH NORECOVERY
> RESTORE LOG ... WITH NORECOVERY
> RESTORE LOG ... WITH RECOVERY
> And the database is still in "restoring" state (inaccessible, and not only
a refresh problem in EM),
> you should report this as a bug to MS.
> Technical sidenote: The only difference between NORECOVERY and RECOVERY is
whether the UNDO phase is
> performed by the restore process. The prior REDO phase is always performed
.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Thanks Tibor

Question on Backup/Restore

New to SQL Server. is it true, as it seems to be, that SQL Server
cannot do a point in time recovery to a point in time that would exceed
the time of the last transaction log backup?
That is, it cannot use the active log in conjunction with the archived
logs?
Second question, if the server fails and is rebooted, will the system
catalog tables 'remember' the times of the transaction log backups?
Thanks in advance.
GerryDataPro wrote:
> New to SQL Server. is it true, as it seems to be, that SQL Server
> cannot do a point in time recovery to a point in time that would exceed
> the time of the last transaction log backup?
> That is, it cannot use the active log in conjunction with the archived
> logs?
> Second question, if the server fails and is rebooted, will the system
> catalog tables 'remember' the times of the transaction log backups?
> Thanks in advance.
> Gerry
>
1. No, it cannot use the "active" log for this. You must take a final
transaction log backup, which will contain the data from the active log,
which you can then use in your point-in-time restore.
2. Yes, this information is retained between reboots.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||> 1. No, it cannot use the "active" log for this. You must take a final
> transaction log backup, which will contain the data from the active log,
> which you can then use in your point-in-time restore.
> 2. Yes, this information is retained between reboots.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
Thanks Tracy|||Note, though that even though you need to do a log backup (you cannot use the active log), you still
have plenty of options. What is required is that the log file exists. I'm sure this is the same as
in other systems. If the database is inaccessible, you can still produce a log backup using the
NO_TRUNCATE option of the BACKUP LOG command. And even if you can't start the SQL Server, you can
handle this situation:
Create a database on some other SQL Server.
Stop that SQL Server.
Delete the database files.
Copy your "production" ldf file where the newly created log file used to be.
Start SQL Server.
Do a log backup using NO_TRUNCATE.
You have now produced that "last log backup".
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"DataPro" <datapro01@.yahoo.com> wrote in message
news:1165419474.732740.263160@.f1g2000cwa.googlegroups.com...
>> 1. No, it cannot use the "active" log for this. You must take a final
>> transaction log backup, which will contain the data from the active log,
>> which you can then use in your point-in-time restore.
>> 2. Yes, this information is retained between reboots.
>>
>> --
>> Tracy McKibben
>> MCDBA
>> http://www.realsqlguy.com
> Thanks Tracy
>|||Thanks Tibor;;
OK after I do the restore of a user database...even though the restore
is marked complete on the percentage bar graph the database was marked
as 'Loading'
Baffled me...thought it was because it was being rolled forward
through transaction logs.
I ended up issuing a
RESTORE DATABASE <Database name> WITH RECOVERY and that cleared it up.
But that does not leave me with a warm and fuzzy.
Is this typical behavior in SQL Server?
> >|||When you do RESTORE, you specify NORECOVERY on all restores (db, log, log etc) but the last one.
Until you've done restore using RECOVERY, the database is in "restoring" state (reported as
"loading" by earlier tools). If you forgot to do RECOVERY on your last backup, you can handle the
situation in just the way you did. If you have a case where you do, for instance:
RESTORE DATABASE ... WITH NORECOVERY
RESTORE LOG ... WITH NORECOVERY
RESTORE LOG ... WITH NORECOVERY
RESTORE LOG ... WITH RECOVERY
And the database is still in "restoring" state (inaccessible, and not only a refresh problem in EM),
you should report this as a bug to MS.
Technical sidenote: The only difference between NORECOVERY and RECOVERY is whether the UNDO phase is
performed by the restore process. The prior REDO phase is always performed.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"DataPro" <datapro01@.yahoo.com> wrote in message
news:1165424865.858239.168580@.73g2000cwn.googlegroups.com...
> Thanks Tibor;;
> OK after I do the restore of a user database...even though the restore
> is marked complete on the percentage bar graph the database was marked
> as 'Loading'
> Baffled me...thought it was because it was being rolled forward
> through transaction logs.
> I ended up issuing a
> RESTORE DATABASE <Database name> WITH RECOVERY and that cleared it up.
> But that does not leave me with a warm and fuzzy.
> Is this typical behavior in SQL Server?
>> >
>|||Tibor Karaszi wrote:
> When you do RESTORE, you specify NORECOVERY on all restores (db, log, log etc) but the last one.
> Until you've done restore using RECOVERY, the database is in "restoring" state (reported as
> "loading" by earlier tools). If you forgot to do RECOVERY on your last backup, you can handle the
> situation in just the way you did. If you have a case where you do, for instance:
> RESTORE DATABASE ... WITH NORECOVERY
> RESTORE LOG ... WITH NORECOVERY
> RESTORE LOG ... WITH NORECOVERY
> RESTORE LOG ... WITH RECOVERY
> And the database is still in "restoring" state (inaccessible, and not only a refresh problem in EM),
> you should report this as a bug to MS.
> Technical sidenote: The only difference between NORECOVERY and RECOVERY is whether the UNDO phase is
> performed by the restore process. The prior REDO phase is always performed.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Thanks Tibor