Log shipping Transactions Log backup on secondary server

Guys,
Right after I setup up log shipping, there are a few jobs created under
job on the secondary server called "Log Shipping Alert Job - Backup"
and "Transaction Log Backup Job for DB Maintenance Plan...".
Without doing anything I would get a red "X", meaning failed on the
"Log Shipping Alert Job -Backup". When I run execute the "Transaction
Log Backup Job for DB Maintenance Plan...", it would fail too. This
is under the secondary server.
Is this normal? If not, how do i fix this? Do people actually backup
the transaction log on the secondary server on a log shipping?
Thanks,
Tonyhttp://www.sql-server-performance.c...og_shipping.asp
<tractng@.gmail.com> wrote in message
news:1147763695.248207.126980@.j33g2000cwa.googlegroups.com...
> Guys,
> Right after I setup up log shipping, there are a few jobs created under
> job on the secondary server called "Log Shipping Alert Job - Backup"
> and "Transaction Log Backup Job for DB Maintenance Plan...".
>
> Without doing anything I would get a red "X", meaning failed on the
> "Log Shipping Alert Job -Backup". When I run execute the "Transaction
> Log Backup Job for DB Maintenance Plan...", it would fail too. This
> is under the secondary server.
> Is this normal? If not, how do i fix this? Do people actually backup
> the transaction log on the secondary server on a log shipping?
>
> Thanks,
> Tony
>|||You cannot do any type of backup of a database restored using either NORECOV
ERY or STANDBY. But you
should be prepared to do backups of that database the minute this becomes th
e production database
(when a fail over is performed).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<tractng@.gmail.com> wrote in message news:1147763695.248207.126980@.j33g2000cwa.googlegroups.
com...
> Guys,
> Right after I setup up log shipping, there are a few jobs created under
> job on the secondary server called "Log Shipping Alert Job - Backup"
> and "Transaction Log Backup Job for DB Maintenance Plan...".
>
> Without doing anything I would get a red "X", meaning failed on the
> "Log Shipping Alert Job -Backup". When I run execute the "Transaction
> Log Backup Job for DB Maintenance Plan...", it would fail too. This
> is under the secondary server.
> Is this normal? If not, how do i fix this? Do people actually backup
> the transaction log on the secondary server on a log shipping?
>
> Thanks,
> Tony
>|||Tibor,
Just to clarify. You are saying I won't be able to do a backup when it
is in the standby state. When the fail over is performed, I should be
able to?
Thanks a lot,
Tony|||Yes.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<tractng@.gmail.com> wrote in message news:1147979332.349123.49520@.j55g2000cwa.googlegroups.c
om...
> Tibor,
> Just to clarify. You are saying I won't be able to do a backup when it
> is in the standby state. When the fail over is performed, I should be
> able to?
>
> Thanks a lot,
> Tony
>

Log shipping Transactions Log backup on secondary server

Guys,
Right after I setup up log shipping, there are a few jobs created under
job on the secondary server called "Log Shipping Alert Job - Backup"
and "Transaction Log Backup Job for DB Maintenance Plan...".
Without doing anything I would get a red "X", meaning failed on the
"Log Shipping Alert Job -Backup". When I run execute the "Transaction
Log Backup Job for DB Maintenance Plan...", it would fail too. This
is under the secondary server.
Is this normal? If not, how do i fix this? Do people actually backup
the transaction log on the secondary server on a log shipping?
Thanks,
TonyYou cannot do any type of backup of a database restored using either NORECOVERY or STANDBY. But you
should be prepared to do backups of that database the minute this becomes the production database
(when a fail over is performed).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<tractng@.gmail.com> wrote in message news:1147763695.248207.126980@.j33g2000cwa.googlegroups.com...
> Guys,
> Right after I setup up log shipping, there are a few jobs created under
> job on the secondary server called "Log Shipping Alert Job - Backup"
> and "Transaction Log Backup Job for DB Maintenance Plan...".
>
> Without doing anything I would get a red "X", meaning failed on the
> "Log Shipping Alert Job -Backup". When I run execute the "Transaction
> Log Backup Job for DB Maintenance Plan...", it would fail too. This
> is under the secondary server.
> Is this normal? If not, how do i fix this? Do people actually backup
> the transaction log on the secondary server on a log shipping?
>
> Thanks,
> Tony
>|||http://www.sql-server-performance.com/sql_server_log_shipping.asp
<tractng@.gmail.com> wrote in message
news:1147763695.248207.126980@.j33g2000cwa.googlegroups.com...
> Guys,
> Right after I setup up log shipping, there are a few jobs created under
> job on the secondary server called "Log Shipping Alert Job - Backup"
> and "Transaction Log Backup Job for DB Maintenance Plan...".
>
> Without doing anything I would get a red "X", meaning failed on the
> "Log Shipping Alert Job -Backup". When I run execute the "Transaction
> Log Backup Job for DB Maintenance Plan...", it would fail too. This
> is under the secondary server.
> Is this normal? If not, how do i fix this? Do people actually backup
> the transaction log on the secondary server on a log shipping?
>
> Thanks,
> Tony
>|||Tibor,
Just to clarify. You are saying I won't be able to do a backup when it
is in the standby state. When the fail over is performed, I should be
able to?
Thanks a lot,
Tony|||Yes.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<tractng@.gmail.com> wrote in message news:1147979332.349123.49520@.j55g2000cwa.googlegroups.com...
> Tibor,
> Just to clarify. You are saying I won't be able to do a backup when it
> is in the standby state. When the fail over is performed, I should be
> able to?
>
> Thanks a lot,
> Tony
>

log shipping question on two databases

Hi,
I created 2 log shipping plans at the same time, for database dbA and dbB
respectively, to ship logs to antother database server.
All the log transaction schedule and location are the same.
However, only log shipping plan for dbA succeed.
Is there any restriction on log shipping for 2 databases at the same time?
Thanks for help.
Jason
No, there is no such restriction. You can can configure two databases from
the same instance for log shipping.
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Jason Huang" wrote:

> Hi,
> I created 2 log shipping plans at the same time, for database dbA and dbB
> respectively, to ship logs to antother database server.
> All the log transaction schedule and location are the same.
> However, only log shipping plan for dbA succeed.
> Is there any restriction on log shipping for 2 databases at the same time?
> Thanks for help.
>
> Jason
>
>

log shipping question on two databases

Hi,
I created 2 log shipping plans at the same time, for database dbA and dbB
respectively, to ship logs to antother database server.
All the log transaction schedule and location are the same.
However, only log shipping plan for dbA succeed.
Is there any restriction on log shipping for 2 databases at the same time?
Thanks for help.
JasonNo, there is no such restriction. You can can configure two databases from
the same instance for log shipping.
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Jason Huang" wrote:

> Hi,
> I created 2 log shipping plans at the same time, for database dbA and dbB
> respectively, to ship logs to antother database server.
> All the log transaction schedule and location are the same.
> However, only log shipping plan for dbA succeed.
> Is there any restriction on log shipping for 2 databases at the same time?
> Thanks for help.
>
> Jason
>
>

log shipping question on two databases

Hi,
I created 2 log shipping plans at the same time, for database dbA and dbB
respectively, to ship logs to antother database server.
All the log transaction schedule and location are the same.
However, only log shipping plan for dbA succeed.
Is there any restriction on log shipping for 2 databases at the same time?
Thanks for help.
JasonNo, there is no such restriction. You can can configure two databases from
the same instance for log shipping.
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Jason Huang" wrote:
> Hi,
> I created 2 log shipping plans at the same time, for database dbA and dbB
> respectively, to ship logs to antother database server.
> All the log transaction schedule and location are the same.
> However, only log shipping plan for dbA succeed.
> Is there any restriction on log shipping for 2 databases at the same time?
> Thanks for help.
>
> Jason
>
>

Log Shipping Problem

I have a warm standby 2003 Server and am trying to set up log shipping. I am
working with SQL Server 2005 and have created the log shipping jobs using the
wizard. Initially as suggested in the documentation, I backed up the primary
database using norecover options. I resored the database on the secondary to
overwrite the existing database with recovery and standby options which has
left the secondary database in Standby/Read-Only mode. All the the log
shipping job history on the primary and secondary servers show success (even
the restore on the secondary). When I insert records into tables on the
primary I do not see them appear in the secondary database after the restore
job executes. I don't have much experience with log shipping or partial
restores from log files for that matter, I have always done full restores
with no recovery. Why don't I see the new records in the secondary database
after a successful restore (according to job history). I can see the .trn
files in the shipped log file directory, how does this process work, does it
take a restore with norecovery before you can see them in the secondary
database? There is nothing in the documentation that indicates this, I'm
missing something here ... I guess it has something to do with partial
restores. What am I doing wrong.
Fran Morabito wrote:
> I have a warm standby 2003 Server and am trying to set up log shipping. I am
> working with SQL Server 2005 and have created the log shipping jobs using the
> wizard. Initially as suggested in the documentation, I backed up the primary
> database using norecover options. I resored the database on the secondary to
> overwrite the existing database with recovery and standby options which has
> left the secondary database in Standby/Read-Only mode. All the the log
> shipping job history on the primary and secondary servers show success (even
> the restore on the secondary). When I insert records into tables on the
> primary I do not see them appear in the secondary database after the restore
> job executes. I don't have much experience with log shipping or partial
> restores from log files for that matter, I have always done full restores
> with no recovery. Why don't I see the new records in the secondary database
> after a successful restore (according to job history). I can see the .trn
> files in the shipped log file directory, how does this process work, does it
> take a restore with norecovery before you can see them in the secondary
> database? There is nothing in the documentation that indicates this, I'm
> missing something here ... I guess it has something to do with partial
> restores. What am I doing wrong.
>
I don't know anything about the log shipping wizard, I've always rolled
my own log shipping routines. It's a pretty simple process:
1. Start with a full backup of the live database
2. Restore full backup to standby using WITH NORECOVERY option
3. Schedule frequent transaction log backups of the live database,
preferrably writing each backup to a seperate file
4. Monitor for new transaction log backups, when found, restore to
standby using WITH NORECOVERY option.
I would start by making sure your transaction log backups are occurring
on the live server, and that they are being restored on the standby server.
Tracy McKibben
MCDBA
http://www.realsqlguy.com

Log Shipping Problem

I have a warm standby 2003 Server and am trying to set up log shipping. I am
working with SQL Server 2005 and have created the log shipping jobs using th
e
wizard. Initially as suggested in the documentation, I backed up the primary
database using norecover options. I resored the database on the secondary to
overwrite the existing database with recovery and standby options which has
left the secondary database in Standby/Read-Only mode. All the the log
shipping job history on the primary and secondary servers show success (even
the restore on the secondary). When I insert records into tables on the
primary I do not see them appear in the secondary database after the restore
job executes. I don't have much experience with log shipping or partial
restores from log files for that matter, I have always done full restores
with no recovery. Why don't I see the new records in the secondary database
after a successful restore (according to job history). I can see the .trn
files in the shipped log file directory, how does this process work, does it
take a restore with norecovery before you can see them in the secondary
database? There is nothing in the documentation that indicates this, I'm
missing something here ... I guess it has something to do with partial
restores. What am I doing wrong.Fran Morabito wrote:
> I have a warm standby 2003 Server and am trying to set up log shipping. I
am
> working with SQL Server 2005 and have created the log shipping jobs using
the
> wizard. Initially as suggested in the documentation, I backed up the prima
ry
> database using norecover options. I resored the database on the secondary
to
> overwrite the existing database with recovery and standby options which ha
s
> left the secondary database in Standby/Read-Only mode. All the the log
> shipping job history on the primary and secondary servers show success (ev
en
> the restore on the secondary). When I insert records into tables on the
> primary I do not see them appear in the secondary database after the resto
re
> job executes. I don't have much experience with log shipping or partial
> restores from log files for that matter, I have always done full restores
> with no recovery. Why don't I see the new records in the secondary databas
e
> after a successful restore (according to job history). I can see the .trn
> files in the shipped log file directory, how does this process work, does
it
> take a restore with norecovery before you can see them in the secondary
> database? There is nothing in the documentation that indicates this, I'm
> missing something here ... I guess it has something to do with partial
> restores. What am I doing wrong.
>
I don't know anything about the log shipping wizard, I've always rolled
my own log shipping routines. It's a pretty simple process:
1. Start with a full backup of the live database
2. Restore full backup to standby using WITH NORECOVERY option
3. Schedule frequent transaction log backups of the live database,
preferrably writing each backup to a seperate file
4. Monitor for new transaction log backups, when found, restore to
standby using WITH NORECOVERY option.
I would start by making sure your transaction log backups are occurring
on the live server, and that they are being restored on the standby server.
Tracy McKibben
MCDBA
http://www.realsqlguy.com

Log Shipping Problem

I have a warm standby 2003 Server and am trying to set up log shipping. I am
working with SQL Server 2005 and have created the log shipping jobs using the
wizard. Initially as suggested in the documentation, I backed up the primary
database using norecover options. I resored the database on the secondary to
overwrite the existing database with recovery and standby options which has
left the secondary database in Standby/Read-Only mode. All the the log
shipping job history on the primary and secondary servers show success (even
the restore on the secondary). When I insert records into tables on the
primary I do not see them appear in the secondary database after the restore
job executes. I don't have much experience with log shipping or partial
restores from log files for that matter, I have always done full restores
with no recovery. Why don't I see the new records in the secondary database
after a successful restore (according to job history). I can see the .trn
files in the shipped log file directory, how does this process work, does it
take a restore with norecovery before you can see them in the secondary
database? There is nothing in the documentation that indicates this, I'm
missing something here ... I guess it has something to do with partial
restores. What am I doing wrong.Fran Morabito wrote:
> I have a warm standby 2003 Server and am trying to set up log shipping. I am
> working with SQL Server 2005 and have created the log shipping jobs using the
> wizard. Initially as suggested in the documentation, I backed up the primary
> database using norecover options. I resored the database on the secondary to
> overwrite the existing database with recovery and standby options which has
> left the secondary database in Standby/Read-Only mode. All the the log
> shipping job history on the primary and secondary servers show success (even
> the restore on the secondary). When I insert records into tables on the
> primary I do not see them appear in the secondary database after the restore
> job executes. I don't have much experience with log shipping or partial
> restores from log files for that matter, I have always done full restores
> with no recovery. Why don't I see the new records in the secondary database
> after a successful restore (according to job history). I can see the .trn
> files in the shipped log file directory, how does this process work, does it
> take a restore with norecovery before you can see them in the secondary
> database? There is nothing in the documentation that indicates this, I'm
> missing something here ... I guess it has something to do with partial
> restores. What am I doing wrong.
>
I don't know anything about the log shipping wizard, I've always rolled
my own log shipping routines. It's a pretty simple process:
1. Start with a full backup of the live database
2. Restore full backup to standby using WITH NORECOVERY option
3. Schedule frequent transaction log backups of the live database,
preferrably writing each backup to a seperate file
4. Monitor for new transaction log backups, when found, restore to
standby using WITH NORECOVERY option.
I would start by making sure your transaction log backups are occurring
on the live server, and that they are being restored on the standby server.
Tracy McKibben
MCDBA
http://www.realsqlguy.comsql

Log shipping not work, but jobs say successful

I have a pretty standard log shipping arrangement created with the Log
Shipping wizard against an existing database on the standby server. All the
jobs were created successfully and run on the correct schedule. However,
the copy job on the standby server doesn't work. It shows that it ran
successfully, but the files just aren't copied to the standby server's
directory, and so are not restored. After manually copying the transaction
log files to the standby server, the restore job will work. However, the
next log in sequence will not copy over.
The maintenance plan history shows no errors.
Both servers are running Windows 2000 servers and SQL Server 2000 Enterprise
SP3a. The link is a 45 Mbit leased line.
What could be the problem?
Thanks,
RS
RS,
usually this is a problem with the paths - the wizard is not very intuitive
and it's quite easy to set them incorrectly. On the screen that says
'Specify the Transaction Log Share', you must identify the file share on the
primary server and when setting up the destination, the name is a local
pathname, not a file share. If this is incorrect, there will be no errors
and the monitor will show continually the first setup file as being
transferred. So, initially check that you have a share on the primary server
and the logs are getting there.
HTH,
Paul Ibison
sql

log shipping login sync

Hi,

I have log shipping setup working fine. I created new login (jskow) on primary server and he is a valid user in the database which is configure for log shipping, My secondary server is read-only. I want to give jskow read access on secondary, I added jskow to secondary server, log shipping copied that database user to secondary database , but when I try to login to secondary server and use the read-only database , I get error not a valid user?,

any help?

thanks in advance.

Ram.Run SP_CHANGE_USERS_LOGIN with REPORT clause and see whether the login reported as orphaned user, if so use AUTO_FIX to fix the login.

Refer to BOOKS ONLINE for more information.

log shipping barfing

sql2k sp2
Log Shipping gets set up successfully. The db gets created
on the secondary box. All the TLog backups get transferred
to the secondary box. But then after some time it gets out
of sync. In the reporting file there is the message:
(snippet)
(SQL Server does not exist or access is denied)
How could this be since it was able to intialize the new
db? If it never did that and I got this message it would
make more sense than creating the db but not baing able to
connect after that.
TIA, ChrisChris,
Which job is failing? Sounds like the restore job on the secondary. Are you
sure SQL Agent on the secondary can connect to the secondary SQL Server?
Ron
--
Ron Talmage
SQL Server MVP
"chris" <anonymous@.discussions.microsoft.com> wrote in message
news:05e001c3a4ca$1a848f70$a301280a@.phx.gbl...
> sql2k sp2
> Log Shipping gets set up successfully. The db gets created
> on the secondary box. All the TLog backups get transferred
> to the secondary box. But then after some time it gets out
> of sync. In the reporting file there is the message:
> (snippet)
> (SQL Server does not exist or access is denied)
> How could this be since it was able to intialize the new
> db? If it never did that and I got this message it would
> make more sense than creating the db but not baing able to
> connect after that.
> TIA, Chris
>|||Are you
>sure SQL Agent on the secondary can connect to the
secondary SQL Server?
Not sure Im following on this one.
>--Original Message--
>Chris,
>Which job is failing? Sounds like the restore job on the
secondary. Are you
>sure SQL Agent on the secondary can connect to the
secondary SQL Server?
>Ron
>--
>Ron Talmage
>SQL Server MVP
>"chris" <anonymous@.discussions.microsoft.com> wrote in
message
>news:05e001c3a4ca$1a848f70$a301280a@.phx.gbl...
>> sql2k sp2
>> Log Shipping gets set up successfully. The db gets
created
>> on the secondary box. All the TLog backups get
transferred
>> to the secondary box. But then after some time it gets
out
>> of sync. In the reporting file there is the message:
>> (snippet)
>> (SQL Server does not exist or access is denied)
>> How could this be since it was able to intialize the new
>> db? If it never did that and I got this message it would
>> make more sense than creating the db but not baing able
to
>> connect after that.
>> TIA, Chris
>
>.
>

Log Shipping and Recovery

I have just created a pair of log shipping SQL Servers.
Both are running SQL Server 2000 sp3 on Win2k sp3.
I've read the documentation on how to change roles between
the servers, but it assumes that both servers are
available for a controlled change. What if the primary
server is destroyed? How can I make the secondary server
the primary in an emergency situation? I know I can't just
change the database on the secondary from Read-Only to
Normal. What has to happen in order for this secondary
server to become active?
TIA,
Ken> I know I can't just
> change the database on the secondary from Read-Only to
> Normal.
Why do you say that? All you should need to do is:
RESTORE DATABASE dbname WITH RECOVERY
Above assumes that EM's log shipping doesn't do anything strange.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Ken Krause" <kenkrause@.promaxautonews.com> wrote in message
news:005601c3aba4$e6b6c5f0$a401280a@.phx.gbl...
> I have just created a pair of log shipping SQL Servers.
> Both are running SQL Server 2000 sp3 on Win2k sp3.
> I've read the documentation on how to change roles between
> the servers, but it assumes that both servers are
> available for a controlled change. What if the primary
> server is destroyed? How can I make the secondary server
> the primary in an emergency situation? I know I can't just
> change the database on the secondary from Read-Only to
> Normal. What has to happen in order for this secondary
> server to become active?
> TIA,
> Ken|||I have documentation for this, send me an email
and I will reply with the information.
>--Original Message--
>I have just created a pair of log shipping SQL Servers.
>Both are running SQL Server 2000 sp3 on Win2k sp3.
>I've read the documentation on how to change roles
between
>the servers, but it assumes that both servers are
>available for a controlled change. What if the primary
>server is destroyed? How can I make the secondary server
>the primary in an emergency situation? I know I can't
just
>change the database on the secondary from Read-Only to
>Normal. What has to happen in order for this secondary
>server to become active?
>TIA,
>Ken
>.
>|||The book Microsoft SQL Server 2000 High Availability
covers this in the Log Shipping chapter. Making a role
change has nothing to do with whether the primary is
available ... you can make it, but you may possibly lose
the last transactions if you can't get the tail of the
log. You're only as good as your last tran log you have
access to.
If you have the DB in read-only mode, this is incorrect.
I assume it is in STANDBY, which shows the DB as read-only.
>--Original Message--
>I have just created a pair of log shipping SQL Servers.
>Both are running SQL Server 2000 sp3 on Win2k sp3.
>I've read the documentation on how to change roles
between
>the servers, but it assumes that both servers are
>available for a controlled change. What if the primary
>server is destroyed? How can I make the secondary server
>the primary in an emergency situation? I know I can't
just
>change the database on the secondary from Read-Only to
>Normal. What has to happen in order for this secondary
>server to become active?
>TIA,
>Ken
>.
>

Log shipping and Full Text

I setup log shipping on my production server which is a part of Replication
and went ahead and created a report server using log Shipping however my
Report server is missing Full Text and it don't allow me to create it saying
it is read only database.
I am running SQL server 2000 with service Pack 2
Is there any way I can also bring Full text on Report Server my databasde is
huge and full text takes couple of days to create so I was exploring a
solution that can take full txet catalog from my production server and copy
it to Reprot Server.
Thanks
Tanweer
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Tanweer" <Tanweer@.discussions.microsoft.com> wrote in message
news:820818D0-7F18-45F0-8B82-9ACBF539F8BE@.microsoft.com...
> I setup log shipping on my production server which is a part of
Replication
> and went ahead and created a report server using log Shipping however my
> Report server is missing Full Text and it don't allow me to create it
saying
> it is read only database.
> I am running SQL server 2000 with service Pack 2
> Is there any way I can also bring Full text on Report Server my databasde
is
> huge and full text takes couple of days to create so I was exploring a
> solution that can take full txet catalog from my production server and
copy
> it to Reprot Server.
> Thanks
> Tanweer
|||oops, that went out prematurely. You could follow these steps every time you
want your database synchronized -
http://support.microsoft.com/default...b;en-us;240867
Or you could use replication. If you use replication you will have to build
your tables and full-text indexes in advance on the subscriber. Then in your
article properties make sure you select the delete all data option.
SQL 2005 replication will support this directly.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:u$9GFtsaFHA.3488@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
>
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Tanweer" <Tanweer@.discussions.microsoft.com> wrote in message
> news:820818D0-7F18-45F0-8B82-9ACBF539F8BE@.microsoft.com...
> Replication
> saying
databasde
> is
> copy
>
|||However I want this to be automatic every 3 hours the report server need to
have the same catalog as the Production Server.
What I can do to automate this process.
Thanks
Tanweer
"Hilary Cotter" wrote:

> oops, that went out prematurely. You could follow these steps every time you
> want your database synchronized -
> http://support.microsoft.com/default...b;en-us;240867
> Or you could use replication. If you use replication you will have to build
> your tables and full-text indexes in advance on the subscriber. Then in your
> article properties make sure you select the delete all data option.
> SQL 2005 replication will support this directly.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:u$9GFtsaFHA.3488@.tk2msftngp13.phx.gbl...
> databasde
>
>
|||This can be automated.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Tanweer" <Tanweer@.discussions.microsoft.com> wrote in message
news:0E2E76B8-B1FE-4A1E-BE73-D1C949A2AB6A@.microsoft.com...
> However I want this to be automatic every 3 hours the report server need
to[vbcol=seagreen]
> have the same catalog as the Production Server.
> What I can do to automate this process.
> Thanks
> Tanweer
> "Hilary Cotter" wrote:
you[vbcol=seagreen]
build[vbcol=seagreen]
your[vbcol=seagreen]
however my[vbcol=seagreen]
it[vbcol=seagreen]
exploring a[vbcol=seagreen]
and[vbcol=seagreen]

Log shipping and database snapshots

SQL Server 2005
Can a database snapshot be created on a log ship target standby database so
that read-only reports and/or datamarts be ran' I know this is fully
supported when using Database Mirroring but Microsoft isn't supporting this
in production environments yet Didn't know what the limitations were with a
database in standby and snapshots.
Thanks"Kevin Jackson" <kjackson@.powerwayinc.com> wrote in message
news:u1gEwo3YGHA.1348@.TK2MSFTNGP05.phx.gbl...
> SQL Server 2005
> Can a database snapshot be created on a log ship target standby database
so
> that read-only reports and/or datamarts be ran'
Sort of.
If you use RESTORE with STANDBY (check BOL for exact syntax) you can turn
the DB into a read-only mode.
Then later logs can be applied to it.
However, note that when those logs apply there can't be any users in the
database or else they will fail to be restored.
In addition, while they are being restored, you won't be able to read from
the database.
These limitations may or may not be a problem. A typical scenario is to do
something like from 5:00 PM -9:00 AM apply log files as normal. At 9:00 AM
stop applying log files and allow reports to be run. At 5:00 PM kick all
users from the database and start applying logs again.

> I know this is fully
> supported when using Database Mirroring but Microsoft isn't supporting
this
> in production environments yet Didn't know what the limitations were with
a
> database in standby and snapshots.
> Thanks
>|||A Database Snapshot can be created against a Mirror or against a source
database. It can NOT be created against a database that is the target for
Log Shipping. The database has to either be online and accessible or in a
mirroring role to have a Database Snapshot created against it.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Kevin Jackson" <kjackson@.powerwayinc.com> wrote in message
news:u1gEwo3YGHA.1348@.TK2MSFTNGP05.phx.gbl...
> SQL Server 2005
> Can a database snapshot be created on a log ship target standby database
> so that read-only reports and/or datamarts be ran' I know this is
> fully supported when using Database Mirroring but Microsoft isn't
> supporting this in production environments yet Didn't know what the
> limitations were with a database in standby and snapshots.
> Thanks
>

Log shipping and database snapshots

SQL Server 2005
Can a database snapshot be created on a log ship target standby database so
that read-only reports and/or datamarts be ran' I know this is fully
supported when using Database Mirroring but Microsoft isn't supporting this
in production environments yet Didn't know what the limitations were with a
database in standby and snapshots.
Thanks"Kevin Jackson" <kjackson@.powerwayinc.com> wrote in message
news:u1gEwo3YGHA.1348@.TK2MSFTNGP05.phx.gbl...
> SQL Server 2005
> Can a database snapshot be created on a log ship target standby database
so
> that read-only reports and/or datamarts be ran'
Sort of.
If you use RESTORE with STANDBY (check BOL for exact syntax) you can turn
the DB into a read-only mode.
Then later logs can be applied to it.
However, note that when those logs apply there can't be any users in the
database or else they will fail to be restored.
In addition, while they are being restored, you won't be able to read from
the database.
These limitations may or may not be a problem. A typical scenario is to do
something like from 5:00 PM -9:00 AM apply log files as normal. At 9:00 AM
stop applying log files and allow reports to be run. At 5:00 PM kick all
users from the database and start applying logs again.
> I know this is fully
> supported when using Database Mirroring but Microsoft isn't supporting
this
> in production environments yet Didn't know what the limitations were with
a
> database in standby and snapshots.
> Thanks
>|||A Database Snapshot can be created against a Mirror or against a source
database. It can NOT be created against a database that is the target for
Log Shipping. The database has to either be online and accessible or in a
mirroring role to have a Database Snapshot created against it.
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Kevin Jackson" <kjackson@.powerwayinc.com> wrote in message
news:u1gEwo3YGHA.1348@.TK2MSFTNGP05.phx.gbl...
> SQL Server 2005
> Can a database snapshot be created on a log ship target standby database
> so that read-only reports and/or datamarts be ran' I know this is
> fully supported when using Database Mirroring but Microsoft isn't
> supporting this in production environments yet Didn't know what the
> limitations were with a database in standby and snapshots.
> Thanks
>