sql login permissions: shipping

Showing posts with label shipping. Show all posts

Friday, March 23, 2012

Logshipping steps

I need to set up Log shipping in my company.
Can any one tell me what are the prequisites and steps.
Since i am going to do it for the 1st time will require some simple /basic / easy to understand wordings.
Any site id will be ok.
Thanks in advance..Try these:

http://www.sql-server-performance.com/sql_server_log_shipping.asp

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_8elj.asp

http://www.microsoft.com/italy/technet/support/mvp/log.asp

http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/sql/deploy/prodspecs/logship2.asp

HTHsql

logshipping load failure

Hi Guys,
I implemented log shipping but if database is open during
load the restore is failing.
i think i selected "terminate users in database" option.
how i can confirm whether i selected this option? and if
not how can i change this.
THNKS
BIJU
Biju,
the easiest way to check and change this property is to edit the maintenance
plan, goto the logshipping tab and edit, on the initialize tab select
'Terminate Users in Database'.
HTH,
Paul Ibison

Logshipping Help Needed

I am setting up log shipping between a primary server and two secondaries.

The first (secondary ) is applying the logs fine but the second is generating the following error.

[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3154: [Microsoft][ODBC SQL Server Driver][SQL Server]The backup set holds a backup of a database other than the existing 'CDE2' database.
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating abnormally.

the logshipping monitor says it failes to apply first_file_0000000000...Trn

I have seen this listed on MS KB Base Article - 311801 .

and have followed all the suggestions to resolve this issue including seperate folders for each log ship but to no avail.

Any help would be greatly appreciated.

Thanks in advanceDIsable the LS and apply full backup on secondary server, then enable LS again.sql

Logshipping help

As part of my effort to create my own log shipping method, i'm reading
the
documentation people have suggested here. I'm not familiar with some
concepts, the following in particular. From the website
(http://www.sql-server-performance.co...g_shipping.asp
I do have a backup device called DEV_device and the complete path is
D:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\QMISDEV
The article contains the statement below which I am not sure I
completely understand...
RESTORE LOG database_name
FROM DISK = 'g:\mssql7\backup\log\database_name\database_name_ log_backup_device.bak'
The device name in the Authors scenario is
database_name_log_backup_device
My understanding is that a device encompasses the whole path not a
subset of the path(like above).Tested this with little success and my
hope is that there is some one out here with a better understanding
than myself to help out
TIA
TY
TY,
The two flavors of BACKUP/RESTORE concerning how to address your file/tape are:
BACKUP...
FROM DISK = 'C:\...'
BACKUP...
FROM logical_device_name
In the first example, you address the physical file. No backup devices are needed.
A backup device is like a pointer to a physical file. These are the ones you see in the backup
folder in Enterprise Manager. If you want to address the file using a backup device, use the second
alternative.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Tyler Smith Watu" <watuni2000@.yahoo.co.nz> wrote in message
news:2f3438a4.0410120431.386cd44f@.posting.google.c om...
> As part of my effort to create my own log shipping method, i'm reading
> the
> documentation people have suggested here. I'm not familiar with some
> concepts, the following in particular. From the website
> (http://www.sql-server-performance.co...g_shipping.asp
> I do have a backup device called DEV_device and the complete path is
> D:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\QMISDEV
>
> The article contains the statement below which I am not sure I
> completely understand...
> RESTORE LOG database_name
> FROM DISK = 'g:\mssql7\backup\log\database_name\database_name_ log_backup_device.bak'
> The device name in the Authors scenario is
> database_name_log_backup_device
>
> My understanding is that a device encompasses the whole path not a
> subset of the path(like above).Tested this with little success and my
> hope is that there is some one out here with a better understanding
> than myself to help out
>
> TIA
> TY

Logshipping help

As part of my effort to create my own log shipping method, i'm reading
the
documentation people have suggested here. I'm not familiar with some
concepts, the following in particular. From the website
(http://www.sql-server-performance.com/sql_server_log_shipping.asp
I do have a backup device called DEV_device and the complete path is
D:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\QMISDEV
The article contains the statement below which I am not sure I
completely understand...
RESTORE LOG database_name
FROM DISK = 'g:\mssql7\backup\log\database_name\database_name_log_backup_device.bak'
The device name in the Authors scenario is
database_name_log_backup_device
My understanding is that a device encompasses the whole path not a
subset of the path(like above).Tested this with little success and my
hope is that there is some one out here with a better understanding
than myself to help out
TIA
TYTY,
The two flavors of BACKUP/RESTORE concerning how to address your file/tape are:
BACKUP...
FROM DISK = 'C:\...'
BACKUP...
FROM logical_device_name
In the first example, you address the physical file. No backup devices are needed.
A backup device is like a pointer to a physical file. These are the ones you see in the backup
folder in Enterprise Manager. If you want to address the file using a backup device, use the second
alternative.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Tyler Smith Watu" <watuni2000@.yahoo.co.nz> wrote in message
news:2f3438a4.0410120431.386cd44f@.posting.google.com...
> As part of my effort to create my own log shipping method, i'm reading
> the
> documentation people have suggested here. I'm not familiar with some
> concepts, the following in particular. From the website
> (http://www.sql-server-performance.com/sql_server_log_shipping.asp
> I do have a backup device called DEV_device and the complete path is
> D:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\QMISDEV
>
> The article contains the statement below which I am not sure I
> completely understand...
> RESTORE LOG database_name
> FROM DISK = 'g:\mssql7\backup\log\database_name\database_name_log_backup_device.bak'
> The device name in the Authors scenario is
> database_name_log_backup_device
>
> My understanding is that a device encompasses the whole path not a
> subset of the path(like above).Tested this with little success and my
> hope is that there is some one out here with a better understanding
> than myself to help out
>
> TIA
> TY

Logshipping help

As part of my effort to create my own log shipping method, i'm reading
the
documentation people have suggested here. I'm not familiar with some
concepts, the following in particular. From the website
(http://www.sql-server-performance.c...og_shipping.asp
I do have a backup device called DEV_device and the complete path is
D:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\QMISDEV
The article contains the statement below which I am not sure I
completely understand...
RESTORE LOG database_name
FROM DISK = 'g:\mssql7\backup\log\database_name\data
base_name_log_backup_dev
ice.bak'
The device name in the Authors scenario is
database_name_log_backup_device
My understanding is that a device encompasses the whole path not a
subset of the path(like above).Tested this with little success and my
hope is that there is some one out here with a better understanding
than myself to help out
TIA
TYTY,
The two flavors of BACKUP/RESTORE concerning how to address your file/tape a
re:
BACKUP...
FROM DISK = 'C:\...'
BACKUP...
FROM logical_device_name
In the first example, you address the physical file. No backup devices are n
eeded.
A backup device is like a pointer to a physical file. These are the ones you
see in the backup
folder in Enterprise Manager. If you want to address the file using a backup
device, use the second
alternative.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Tyler Smith Watu" <watuni2000@.yahoo.co.nz> wrote in message
news:2f3438a4.0410120431.386cd44f@.posting.google.com...
> As part of my effort to create my own log shipping method, i'm reading
> the
> documentation people have suggested here. I'm not familiar with some
> concepts, the following in particular. From the website
> (http://www.sql-server-performance.c...og_shipping.asp
> I do have a backup device called DEV_device and the complete path is
> D:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\QMISDEV
>
> The article contains the statement below which I am not sure I
> completely understand...
> RESTORE LOG database_name
> FROM DISK = 'g:\mssql7\backup\log\database_name\data
base_name_log_backup_d
evice.bak'
> The device name in the Authors scenario is
> database_name_log_backup_device
>
> My understanding is that a device encompasses the whole path not a
> subset of the path(like above).Tested this with little success and my
> hope is that there is some one out here with a better understanding
> than myself to help out
>
> TIA
> TY

Logshipping ERROR(urgent)

Hi Guys,
I am facing following problem with MSSQL Server 2000.
I am using Microsoft sql server Log Shipping feature to have a standby
server for disaster recovery purposes.
in the logshipping Destination server while restoring the transaction log
the restore process is failling with following error.
"[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
PrevPageLSN: (8122:7374:3)."
Both servers, source and destination were running with SQL SERVER
ENTERPRISE EDITION SP3 .
after this failure i rebuilded the logshipping process but same error
happened again so after one week updated the destination server with sql sp4
and rebuilded the logshipping process . but the same error happened again.
During this error SQL Server is creating a dump file and text file
pls adviceAre you sure that your databases are consistent - run checkdb...
Bojidar Alexandrov
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> Hi Guys,
> I am facing following problem with MSSQL Server 2000.
> I am using Microsoft sql server Log Shipping feature to have a standby
> server for disaster recovery purposes.
> in the logshipping Destination server while restoring the transaction log
> the restore process is failling with following error.
> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC
SQL
> Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> PrevPageLSN: (8122:7374:3)."
> Both servers, source and destination were running with SQL SERVER
> ENTERPRISE EDITION SP3 .
> after this failure i rebuilded the logshipping process but same error
> happened again so after one week updated the destination server with sql
sp4
> and rebuilded the logshipping process . but the same error happened again.
> During this error SQL Server is creating a dump file and text file
> pls advice|||Hi Bojidar Alexandrov,
in source or destination?
source is consistent as i am doing dbcc every day and no errors found.
"Bojidar Alexandrov" wrote:
> Are you sure that your databases are consistent - run checkdb...
> Bojidar Alexandrov
> "bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
> message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> > Hi Guys,
> > I am facing following problem with MSSQL Server 2000.
> > I am using Microsoft sql server Log Shipping feature to have a standby
> > server for disaster recovery purposes.
> > in the logshipping Destination server while restoring the transaction log
> > the restore process is failling with following error.
> >
> > "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC
> SQL
> > Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> > transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> > Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> > PrevPageLSN: (8122:7374:3)."
> >
> > Both servers, source and destination were running with SQL SERVER
> > ENTERPRISE EDITION SP3 .
> > after this failure i rebuilded the logshipping process but same error
> > happened again so after one week updated the destination server with sql
> sp4
> > and rebuilded the logshipping process . but the same error happened again.
> > During this error SQL Server is creating a dump file and text file
> >
> > pls advice
>|||"bijupg@.hotmail.com" schrieb:
> Hi Guys,
> I am facing following problem with MSSQL Server 2000.
> I am using Microsoft sql server Log Shipping feature to have a standby
> server for disaster recovery purposes.
> in the logshipping Destination server while restoring the transaction log
> the restore process is failling with following error.
> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
> Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> PrevPageLSN: (8122:7374:3)."
> Both servers, source and destination were running with SQL SERVER
> ENTERPRISE EDITION SP3 .
> after this failure i rebuilded the logshipping process but same error
> happened again so after one week updated the destination server with sql sp4
> and rebuilded the logshipping process . but the same error happened again.
> During this error SQL Server is creating a dump file and text file
> pls advice
Did you do transaction log backups in between? Don't forget that they empty
the TA-Log and produce a new sequence number - then the logshipping (being
fully incremental) are missing some data and cannot work any more ...|||No i am not doing any transaction log backup in between
"Christian Donner" wrote:
> "bijupg@.hotmail.com" schrieb:
> > Hi Guys,
> > I am facing following problem with MSSQL Server 2000.
> > I am using Microsoft sql server Log Shipping feature to have a standby
> > server for disaster recovery purposes.
> > in the logshipping Destination server while restoring the transaction log
> > the restore process is failling with following error.
> >
> > "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
> > Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> > transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> > Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> > PrevPageLSN: (8122:7374:3)."
> >
> > Both servers, source and destination were running with SQL SERVER
> > ENTERPRISE EDITION SP3 .
> > after this failure i rebuilded the logshipping process but same error
> > happened again so after one week updated the destination server with sql sp4
> > and rebuilded the logshipping process . but the same error happened again.
> > During this error SQL Server is creating a dump file and text file
> >
> > pls advice
> Did you do transaction log backups in between? Don't forget that they empty
> the TA-Log and produce a new sequence number - then the logshipping (being
> fully incremental) are missing some data and cannot work any more ...|||The type of error you are seeing is most likely being caused by corruption
in your transaction logs. Review system event logs on both servers for ANY
hardware-related warnings and errors. Update all your firmware and drivers.
Adrian
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> Hi Guys,
> I am facing following problem with MSSQL Server 2000.
> I am using Microsoft sql server Log Shipping feature to have a standby
> server for disaster recovery purposes.
> in the logshipping Destination server while restoring the transaction log
> the restore process is failling with following error.
> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC
> SQL
> Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> PrevPageLSN: (8122:7374:3)."
> Both servers, source and destination were running with SQL SERVER
> ENTERPRISE EDITION SP3 .
> after this failure i rebuilded the logshipping process but same error
> happened again so after one week updated the destination server with sql
> sp4
> and rebuilded the logshipping process . but the same error happened again.
> During this error SQL Server is creating a dump file and text file
> pls advice|||Biju.
You have been having trouble with this DB many times in the past. You had
corruption, it showed as fixed, and now it is back. You do not have torn
page detection on. Turn ton page detect ion on.
If your corruption continues, you will soon have a database that all you can
do it delete.
It may be worth your while to open a case with Microsoft PSS.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
news:tsednVPPk5VQVjPfRVn-3Q@.rogers.com...
> The type of error you are seeing is most likely being caused by corruption
> in your transaction logs. Review system event logs on both servers for ANY
> hardware-related warnings and errors. Update all your firmware and
> drivers.
> Adrian
>
> "bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
> message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
>> Hi Guys,
>> I am facing following problem with MSSQL Server 2000.
>> I am using Microsoft sql server Log Shipping feature to have a standby
>> server for disaster recovery purposes.
>> in the logshipping Destination server while restoring the transaction log
>> the restore process is failling with following error.
>> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC
>> SQL
>> Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
>> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
>> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
>> PrevPageLSN: (8122:7374:3)."
>> Both servers, source and destination were running with SQL SERVER
>> ENTERPRISE EDITION SP3 .
>> after this failure i rebuilded the logshipping process but same error
>> happened again so after one week updated the destination server with sql
>> sp4
>> and rebuilded the logshipping process . but the same error happened
>> again.
>> During this error SQL Server is creating a dump file and text file
>> pls advice
>|||Hi Mike,
can you pls advice how to open case with Microsoft PSS.
"Mike Epprecht (SQL MVP)" wrote:
> Biju.
> You have been having trouble with this DB many times in the past. You had
> corruption, it showed as fixed, and now it is back. You do not have torn
> page detection on. Turn ton page detect ion on.
> If your corruption continues, you will soon have a database that all you can
> do it delete.
> It may be worth your while to open a case with Microsoft PSS.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
> news:tsednVPPk5VQVjPfRVn-3Q@.rogers.com...
> > The type of error you are seeing is most likely being caused by corruption
> > in your transaction logs. Review system event logs on both servers for ANY
> > hardware-related warnings and errors. Update all your firmware and
> > drivers.
> >
> > Adrian
> >
> >
> > "bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
> > message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> >> Hi Guys,
> >> I am facing following problem with MSSQL Server 2000.
> >> I am using Microsoft sql server Log Shipping feature to have a standby
> >> server for disaster recovery purposes.
> >> in the logshipping Destination server while restoring the transaction log
> >> the restore process is failling with following error.
> >>
> >> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC
> >> SQL
> >> Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> >> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> >> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> >> PrevPageLSN: (8122:7374:3)."
> >>
> >> Both servers, source and destination were running with SQL SERVER
> >> ENTERPRISE EDITION SP3 .
> >> after this failure i rebuilded the logshipping process but same error
> >> happened again so after one week updated the destination server with sql
> >> sp4
> >> and rebuilded the logshipping process . but the same error happened
> >> again.
> >> During this error SQL Server is creating a dump file and text file
> >>
> >> pls advice
> >
> >
>
>|||Hi guys,
DBCC CHECKDB is not giving any errors or warnings and database is
functioning normally.
there are no hardware related errors in event viewer.
and we are using compaq cluster with compaq smart array controller so is
there any chance to have a torn page?this type of diska should have mechanism
to ensure that data is completely written and also there are no power failure
at all.
i am using transactional replication for reporting and it is working fine if
there was any problem with source database then it should also fail like
logshipping.
what should be the ideal temperature in datacentres/server romms currently
we are keeping 20-22 degree celcius is it ok?
Pls advice.
"Mike Epprecht (SQL MVP)" wrote:
> Biju.
> You have been having trouble with this DB many times in the past. You had
> corruption, it showed as fixed, and now it is back. You do not have torn
> page detection on. Turn ton page detect ion on.
> If your corruption continues, you will soon have a database that all you can
> do it delete.
> It may be worth your while to open a case with Microsoft PSS.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
> news:tsednVPPk5VQVjPfRVn-3Q@.rogers.com...
> > The type of error you are seeing is most likely being caused by corruption
> > in your transaction logs. Review system event logs on both servers for ANY
> > hardware-related warnings and errors. Update all your firmware and
> > drivers.
> >
> > Adrian
> >
> >
> > "bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
> > message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> >> Hi Guys,
> >> I am facing following problem with MSSQL Server 2000.
> >> I am using Microsoft sql server Log Shipping feature to have a standby
> >> server for disaster recovery purposes.
> >> in the logshipping Destination server while restoring the transaction log
> >> the restore process is failling with following error.
> >>
> >> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC
> >> SQL
> >> Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> >> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> >> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> >> PrevPageLSN: (8122:7374:3)."
> >>
> >> Both servers, source and destination were running with SQL SERVER
> >> ENTERPRISE EDITION SP3 .
> >> after this failure i rebuilded the logshipping process but same error
> >> happened again so after one week updated the destination server with sql
> >> sp4
> >> and rebuilded the logshipping process . but the same error happened
> >> again.
> >> During this error SQL Server is creating a dump file and text file
> >>
> >> pls advice
> >
> >
>
>sql

logshipping error

Hi Guys,
i am using log shipping in sql server 2000(sp3) but in loading in the
destination it is giving following error
Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
transaction ID (0:90997930), on page (1:783096),
in the source database there are no problems now but there wsa one index
corruption and loss of data.
pLS AdviceThis is a multi-part message in MIME format.
--040104080107040407070908
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Sounds like the corruption on the primary DB has put the tlog syncs out
of whack (that's the technical term for it). I would resync from a
recent full DB backup (and subsequent log backups) that was done AFTER
the corruption was fixed. (This might mean a complete resync of the log
shipping pair for you using the DB maint wizard.)
--
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
bijupg@.hotmail.com wrote:
>Hi Guys,
>i am using log shipping in sql server 2000(sp3) but in loading in the
>destination it is giving following error
>Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
>Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
>transaction ID (0:90997930), on page (1:783096),
>in the source database there are no problems now but there wsa one index
>corruption and loss of data.
>pLS Advice
>
--040104080107040407070908
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>Sounds like the corruption on the primary DB has put the tlog syncs
out of whack (that's the technical term for it).Â I would resync from a
recent full DB backup (and subsequent log backups) that was done AFTER
the corruption was fixed.Â (This might mean a complete resync of the
log shipping pair for you using the DB maint wizard.)</tt> 
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
-- 
 mike
hodgson | database administrator
| mallesons stephen jaques 
T +61 (2) 9296 3668 | F +61
(2) 9296 3885 | M +61
(408) 675 907 
E
<a href="http://links.10026.com/?link=mailto:mike.hodgson@.mallesons.nospam.com">
mailto:mike.hodgson@.mallesons.nospam.com</a> | W <a href="http://links.10026.com/?link=/">http://www.mallesons.com">
http://www.mallesons.com</a> 
</div>
 
 
<a class="moz-txt-link-abbreviated" href="http://links.10026.com/?link=mailto:bijupg@.hotmail.com">bijupg@.hotmail.com</a> wrote:
<blockquote cite="midD73EA24F-DBEA-4E4F-9F4F-797DC31E31FF@.microsoft.com"
type="cite">
<pre wrap="">Hi Guys,
i am using log shipping in sql server 2000(sp3) but in loading in the
destination it is giving following error
Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
transaction ID (0:90997930), on page (1:783096),
in the source database there are no problems now but there wsa one index
corruption and loss of data.
pLS Advice
</pre>
</blockquote>
</body>
</html>
--040104080107040407070908--|||This is a multi-part message in MIME format.
--=_NextPart_000_000D_01C56A79.C4EDC0F0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
yes.
Sounds like you need to Re-Synch the DBs
Greg Jackson
PDX, Oregon
--=_NextPart_000_000D_01C56A79.C4EDC0F0
Content-Type: text/html;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

yes.
Sounds like you need to Re-Synch the DBs
Greg Jackson
PDX, Oregon

--=_NextPart_000_000D_01C56A79.C4EDC0F0--

logshipping error

Logshipping

All-
I have typical the log shipping enabled between a prod server and another
server.
If I restore the log sipping source[production] say with a 6 hours back
full
db backup + diff [1 hour], what will be effect of this on the log shippi
ng?
Looks like I will end up reconfiguring the LS in this case since the state
of the production source is changed, right?
TIA
-Bru
Manoj KumarManoj Kumar wrote:

> All-
> I have typical the log shipping enabled between a prod server and another
> server.
> If I restore the log sipping source[production] say with a 6 hours bac
k full
> db backup + diff [1 hour], what will be effect of this on the log ship
ping?
>
> Looks like I will end up reconfiguring the LS in this case since the state
> of the production source is changed, right?
>
> TIA
> -Bru
> --
> Manoj Kumar
Yes
Regards
Amish Shah

Wednesday, March 21, 2012

LogShipping

Hi all I have created a log shipping task in my SQL servers
This Is the server order
Ist Server (Win2003 , SQL 2000 sp3) is the data server let's say
2nd Server (win2003 , SQL 2000 sp3) Is the monitor server
3rd Server (win2000, SQL 2000 sp3) Is the server that accepts the data
(1st & 2nd server is a clucter system )
And the line Connecting 1st & 2nd Server with the 3rd server is 1MB
The problem now is that the SQL Help is awful about logshipping. It explains
nothing!!
I have Create the log shipping but i get en error that the databases are not
sync.
And the FileLoaded and file copped is stack on First_File...trn
And also my databades seemed to be in sync
What Is wrong'
What should I do'
Please HELP!!!
Thanks in advance
DimitrisHi,
I have to correct you on something...there is plenty of
documentation for log shipping!
Try looking at BOL and this link will help. You should
read before implementing.
http://support.microsoft.com/?id=323135
hth
DeeJay
>--Original Message--
>Hi all I have created a log shipping task in my SQL
servers
>This Is the server order
>Ist Server (Win2003 , SQL 2000 sp3) is the data server
let's say
>2nd Server (win2003 , SQL 2000 sp3) Is the monitor server
>3rd Server (win2000, SQL 2000 sp3) Is the server that
accepts the data
>(1st & 2nd server is a clucter system )
>And the line Connecting 1st & 2nd Server with the 3rd
server is 1MB
>The problem now is that the SQL Help is awful about
logshipping. It explains
>nothing!!
>I have Create the log shipping but i get en error that
the databases are not
>sync.
>And the FileLoaded and file copped is stack on
First_File...trn
>And also my databades seemed to be in sync
>What Is wrong'
>What should I do'
>Please HELP!!!
>Thanks in advance
>Dimitris
>
>
>.
>

Logshipping

All-
I have typical the log shipping enabled between a prod server and another
server.
If I restore the log sipping source[production] say with a 6 hours back full
db backup + diff [1 hour], what will be effect of this on the log shipping?
Looks like I will end up reconfiguring the LS in this case since the state
of the production source is changed, right?
TIA
-Bru
--
Manoj KumarManoj Kumar wrote:
> All-
> I have typical the log shipping enabled between a prod server and another
> server.
> If I restore the log sipping source[production] say with a 6 hours back full
> db backup + diff [1 hour], what will be effect of this on the log shipping?
>
> Looks like I will end up reconfiguring the LS in this case since the state
> of the production source is changed, right?
>
> TIA
> -Bru
> --
> Manoj Kumar
Yes
Regards
Amish Shah

Logshipping

Hi
I have a strange problem started happening in my log shipping. The database
went to suspect/loading/read-only mode in the middle of the night.
Can't see any particular reason in the sql srever errorlog.
One thing i noticed in th msdb..backupset. This table did not have an entry
for anyother transaction log that happened after the last transaction log
that got applid to the database. But the logshipping copy job is fine and it
copies all the logs. Something broken internally in the logshpping. I looked
online for anymore info. Apparently there was a hotfix before SP3. We already
have sp3 on this server.
Did anyone experience this problem?
Any idea?
Any kind of help is appreciated.
Thanks
UdayHi
Can you see how did the last LOG restore to the database? What happened?
"Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
> Hi
> I have a strange problem started happening in my log shipping. The
> database
> went to suspect/loading/read-only mode in the middle of the night.
> Can't see any particular reason in the sql srever errorlog.
> One thing i noticed in th msdb..backupset. This table did not have an
> entry
> for anyother transaction log that happened after the last transaction log
> that got applid to the database. But the logshipping copy job is fine and
> it
> copies all the logs. Something broken internally in the logshpping. I
> looked
> online for anymore info. Apparently there was a hotfix before SP3. We
> already
> have sp3 on this server.
> Did anyone experience this problem?
> Any idea?
> Any kind of help is appreciated.
> Thanks
> Uday|||The logshipping_plan_databases table says that the last file loaded was the
midbight file. The database didn't get recovered after that.
It doesn't tell me any reason why this happened.
It went to suspect. I reset the suspect bit and restarted the services.
That didn't help.
--Uday
"Uri Dimant" wrote:
> Hi
> Can you see how did the last LOG restore to the database? What happened?
> "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
> news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
> > Hi
> >
> > I have a strange problem started happening in my log shipping. The
> > database
> > went to suspect/loading/read-only mode in the middle of the night.
> > Can't see any particular reason in the sql srever errorlog.
> >
> > One thing i noticed in th msdb..backupset. This table did not have an
> > entry
> > for anyother transaction log that happened after the last transaction log
> > that got applid to the database. But the logshipping copy job is fine and
> > it
> > copies all the logs. Something broken internally in the logshpping. I
> > looked
> > online for anymore info. Apparently there was a hotfix before SP3. We
> > already
> > have sp3 on this server.
> >
> > Did anyone experience this problem?
> > Any idea?
> > Any kind of help is appreciated.
> >
> > Thanks
> > Uday
>
>|||Hi Uri
I also notice something strange.
The database that was doing the full backup job failed.
It actually did do the backup. But the job failed saying that it can't find
the network path name. The full backup job says that it ran for 1:26minutes
before it failed. But i see transaction log for every 15minutes in that 1:26
minutes. Usually when the ful backup starts, the transaction log back starts
but never does the transaction log backup until its completed. Right.
This is strange.
--Uday
"Uri Dimant" wrote:
> Hi
> Can you see how did the last LOG restore to the database? What happened?
> "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
> news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
> > Hi
> >
> > I have a strange problem started happening in my log shipping. The
> > database
> > went to suspect/loading/read-only mode in the middle of the night.
> > Can't see any particular reason in the sql srever errorlog.
> >
> > One thing i noticed in th msdb..backupset. This table did not have an
> > entry
> > for anyother transaction log that happened after the last transaction log
> > that got applid to the database. But the logshipping copy job is fine and
> > it
> > copies all the logs. Something broken internally in the logshpping. I
> > looked
> > online for anymore info. Apparently there was a hotfix before SP3. We
> > already
> > have sp3 on this server.
> >
> > Did anyone experience this problem?
> > Any idea?
> > Any kind of help is appreciated.
> >
> > Thanks
> > Uday
>
>|||Ignore this reply.
It did say that it waited for the hour that it took for the full backup to
fail.
I had the backup file. Bayut the job reported failure.
Back to square onw. I am not sure what happened.
Help please
Ud
"Udayasree" wrote:
> Hi Uri
> I also notice something strange.
> The database that was doing the full backup job failed.
> It actually did do the backup. But the job failed saying that it can't find
> the network path name. The full backup job says that it ran for 1:26minutes
> before it failed. But i see transaction log for every 15minutes in that 1:26
> minutes. Usually when the ful backup starts, the transaction log back starts
> but never does the transaction log backup until its completed. Right.
> This is strange.
> --Uday
> "Uri Dimant" wrote:
> > Hi
> > Can you see how did the last LOG restore to the database? What happened?
> >
> > "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
> > news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
> > > Hi
> > >
> > > I have a strange problem started happening in my log shipping. The
> > > database
> > > went to suspect/loading/read-only mode in the middle of the night.
> > > Can't see any particular reason in the sql srever errorlog.
> > >
> > > One thing i noticed in th msdb..backupset. This table did not have an
> > > entry
> > > for anyother transaction log that happened after the last transaction log
> > > that got applid to the database. But the logshipping copy job is fine and
> > > it
> > > copies all the logs. Something broken internally in the logshpping. I
> > > looked
> > > online for anymore info. Apparently there was a hotfix before SP3. We
> > > already
> > > have sp3 on this server.
> > >
> > > Did anyone experience this problem?
> > > Any idea?
> > > Any kind of help is appreciated.
> > >
> > > Thanks
> > > Uday
> >
> >
> >|||Well, try restore a last good full backup.
"Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
news:B119E88C-4856-4C0F-B481-1CA7656C0266@.microsoft.com...
> Ignore this reply.
> It did say that it waited for the hour that it took for the full backup to
> fail.
> I had the backup file. Bayut the job reported failure.
> Back to square onw. I am not sure what happened.
> Help please
> Ud
> "Udayasree" wrote:
>> Hi Uri
>> I also notice something strange.
>> The database that was doing the full backup job failed.
>> It actually did do the backup. But the job failed saying that it can't
>> find
>> the network path name. The full backup job says that it ran for
>> 1:26minutes
>> before it failed. But i see transaction log for every 15minutes in that
>> 1:26
>> minutes. Usually when the ful backup starts, the transaction log back
>> starts
>> but never does the transaction log backup until its completed. Right.
>> This is strange.
>> --Uday
>> "Uri Dimant" wrote:
>> > Hi
>> > Can you see how did the last LOG restore to the database? What
>> > happened?
>> >
>> > "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
>> > news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
>> > > Hi
>> > >
>> > > I have a strange problem started happening in my log shipping. The
>> > > database
>> > > went to suspect/loading/read-only mode in the middle of the night.
>> > > Can't see any particular reason in the sql srever errorlog.
>> > >
>> > > One thing i noticed in th msdb..backupset. This table did not have an
>> > > entry
>> > > for anyother transaction log that happened after the last transaction
>> > > log
>> > > that got applid to the database. But the logshipping copy job is fine
>> > > and
>> > > it
>> > > copies all the logs. Something broken internally in the logshpping. I
>> > > looked
>> > > online for anymore info. Apparently there was a hotfix before SP3. We
>> > > already
>> > > have sp3 on this server.
>> > >
>> > > Did anyone experience this problem?
>> > > Any idea?
>> > > Any kind of help is appreciated.
>> > >
>> > > Thanks
>> > > Uday
>> >
>> >
>> >|||I did.
This has been happening lately. Thats how i reestablish the logshipping.
But if this happens on a big database, it will take me a day or 2 to bring
the standby database.
You think i should call Microsoft.
You guys never encountered this issue.
Uday
"Uri Dimant" wrote:
> Well, try restore a last good full backup.
>
>
> "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
> news:B119E88C-4856-4C0F-B481-1CA7656C0266@.microsoft.com...
> > Ignore this reply.
> > It did say that it waited for the hour that it took for the full backup to
> > fail.
> > I had the backup file. Bayut the job reported failure.
> >
> > Back to square onw. I am not sure what happened.
> > Help please
> > Ud
> >
> > "Udayasree" wrote:
> >
> >> Hi Uri
> >>
> >> I also notice something strange.
> >> The database that was doing the full backup job failed.
> >> It actually did do the backup. But the job failed saying that it can't
> >> find
> >> the network path name. The full backup job says that it ran for
> >> 1:26minutes
> >> before it failed. But i see transaction log for every 15minutes in that
> >> 1:26
> >> minutes. Usually when the ful backup starts, the transaction log back
> >> starts
> >> but never does the transaction log backup until its completed. Right.
> >> This is strange.
> >>
> >> --Uday
> >>
> >> "Uri Dimant" wrote:
> >>
> >> > Hi
> >> > Can you see how did the last LOG restore to the database? What
> >> > happened?
> >> >
> >> > "Udayasree" <Udayasree@.discussions.microsoft.com> wrote in message
> >> > news:27D5BE75-8F73-44CE-8614-EEE00372D2C6@.microsoft.com...
> >> > > Hi
> >> > >
> >> > > I have a strange problem started happening in my log shipping. The
> >> > > database
> >> > > went to suspect/loading/read-only mode in the middle of the night.
> >> > > Can't see any particular reason in the sql srever errorlog.
> >> > >
> >> > > One thing i noticed in th msdb..backupset. This table did not have an
> >> > > entry
> >> > > for anyother transaction log that happened after the last transaction
> >> > > log
> >> > > that got applid to the database. But the logshipping copy job is fine
> >> > > and
> >> > > it
> >> > > copies all the logs. Something broken internally in the logshpping. I
> >> > > looked
> >> > > online for anymore info. Apparently there was a hotfix before SP3. We
> >> > > already
> >> > > have sp3 on this server.
> >> > >
> >> > > Did anyone experience this problem?
> >> > > Any idea?
> >> > > Any kind of help is appreciated.
> >> > >
> >> > > Thanks
> >> > > Uday
> >> >
> >> >
> >> >
>
>sql

Logs Shipping ReInit - how to?

We have setup Log Shipping in SQL 2005. Working flawlessly. It appears that
only tran log backup will occur forever unless we intervene. I do want a full
backup to happen, you know, eventually...
What is best way to automate this? Ideally, a full backup nightly would be
great. How to do in script, or is there anything in gui?
tia,
chrisYou want a full backup of the primary? Just do Backup database...
You cannot backup the secondary as far as I know.
If you want to re-init log shipping and start clean on a system that LS is
working flawlessly on, you aer simply wasting bandwidth and cpu. :)
--
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:2E07F579-4A8A-47B6-B457-D7B543F00086@.microsoft.com...
> We have setup Log Shipping in SQL 2005. Working flawlessly. It appears
> that
> only tran log backup will occur forever unless we intervene. I do want a
> full
> backup to happen, you know, eventually...
> What is best way to automate this? Ideally, a full backup nightly would be
> great. How to do in script, or is there anything in gui?
> tia,
> chris|||I can't "just do backup database..." this will break log shipping. Correct?
I'm concerned w/ primary - to start log shipping you do a full backup to
init, then tran log backups thereafter w/ each log shipped to secondary. I DO
NOT want to do tran log backups forever... I eventually would like to do a
full backup.
Am I missing somehting...?
cb
"Kevin3NF" wrote:
> You want a full backup of the primary? Just do Backup database...
> You cannot backup the secondary as far as I know.
> If you want to re-init log shipping and start clean on a system that LS is
> working flawlessly on, you aer simply wasting bandwidth and cpu. :)
> --
> Kevin3NF
> SQL Server dude
> You want fries with that?
> http://kevin3nf.blogspot.com/
> I only check the newsgroups during work hours, M-F.
> Hit my blog and the contact links if necessary...I may be available.
>
> "Chris" <Chris@.discussions.microsoft.com> wrote in message
> news:2E07F579-4A8A-47B6-B457-D7B543F00086@.microsoft.com...
> >
> > We have setup Log Shipping in SQL 2005. Working flawlessly. It appears
> > that
> > only tran log backup will occur forever unless we intervene. I do want a
> > full
> > backup to happen, you know, eventually...
> >
> > What is best way to automate this? Ideally, a full backup nightly would be
> > great. How to do in script, or is there anything in gui?
> >
> > tia,
> > chris
>
>|||Full backups do NOT break the log chain sequence so you can do a FULL backup
at any time. The next log backup after a FULL backup will still capture any
transactions since the previous Log backup, regardless of if there was a
FULL in between or not.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:D69D6BFF-3674-4894-92DF-35EB8261E9DA@.microsoft.com...
> I can't "just do backup database..." this will break log shipping.
> Correct?
> I'm concerned w/ primary - to start log shipping you do a full backup to
> init, then tran log backups thereafter w/ each log shipped to secondary. I
> DO
> NOT want to do tran log backups forever... I eventually would like to do a
> full backup.
> Am I missing somehting...?
> cb
> "Kevin3NF" wrote:
>> You want a full backup of the primary? Just do Backup database...
>> You cannot backup the secondary as far as I know.
>> If you want to re-init log shipping and start clean on a system that LS
>> is
>> working flawlessly on, you aer simply wasting bandwidth and cpu. :)
>> --
>> Kevin3NF
>> SQL Server dude
>> You want fries with that?
>> http://kevin3nf.blogspot.com/
>> I only check the newsgroups during work hours, M-F.
>> Hit my blog and the contact links if necessary...I may be available.
>>
>> "Chris" <Chris@.discussions.microsoft.com> wrote in message
>> news:2E07F579-4A8A-47B6-B457-D7B543F00086@.microsoft.com...
>> >
>> > We have setup Log Shipping in SQL 2005. Working flawlessly. It appears
>> > that
>> > only tran log backup will occur forever unless we intervene. I do want
>> > a
>> > full
>> > backup to happen, you know, eventually...
>> >
>> > What is best way to automate this? Ideally, a full backup nightly would
>> > be
>> > great. How to do in script, or is there anything in gui?
>> >
>> > tia,
>> > chris
>>|||Also, taking DIFFERENTIAL BACKUP would NOT break the log sequence.
However taking TRANSACTION LOG backup (other than the automated jobs of Log
Shipping itself) would break the chain.
--
Ekrem Ã?nsoy
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:D69D6BFF-3674-4894-92DF-35EB8261E9DA@.microsoft.com...
> I can't "just do backup database..." this will break log shipping.
> Correct?
> I'm concerned w/ primary - to start log shipping you do a full backup to
> init, then tran log backups thereafter w/ each log shipped to secondary. I
> DO
> NOT want to do tran log backups forever... I eventually would like to do a
> full backup.
> Am I missing somehting...?
> cb
> "Kevin3NF" wrote:
>> You want a full backup of the primary? Just do Backup database...
>> You cannot backup the secondary as far as I know.
>> If you want to re-init log shipping and start clean on a system that LS
>> is
>> working flawlessly on, you aer simply wasting bandwidth and cpu. :)
>> --
>> Kevin3NF
>> SQL Server dude
>> You want fries with that?
>> http://kevin3nf.blogspot.com/
>> I only check the newsgroups during work hours, M-F.
>> Hit my blog and the contact links if necessary...I may be available.
>>
>> "Chris" <Chris@.discussions.microsoft.com> wrote in message
>> news:2E07F579-4A8A-47B6-B457-D7B543F00086@.microsoft.com...
>> >
>> > We have setup Log Shipping in SQL 2005. Working flawlessly. It appears
>> > that
>> > only tran log backup will occur forever unless we intervene. I do want
>> > a
>> > full
>> > backup to happen, you know, eventually...
>> >
>> > What is best way to automate this? Ideally, a full backup nightly would
>> > be
>> > great. How to do in script, or is there anything in gui?
>> >
>> > tia,
>> > chris
>>

Monday, March 12, 2012

Logins with Log shipping

We are planning on using our secondary database as a reporting server with
log shipping. The problem is that log shipping puts the db in read only mode
and occasionally we need to add user permissions to the secondary only. The
only option I see is everytime permissions are needed we would have to take
the database out of read only mode, grant the permissions and then put the db
back to read only. Does anyone have any other ideas that might work? Thanks!
this won't work - by making the change you will break the log shipping
chain.
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
"Anita" <Anita@.discussions.microsoft.com> wrote in message
news:6C1A0C65-2281-45A8-9A9C-5762DA7D9E6D@.microsoft.com...
> We are planning on using our secondary database as a reporting server with
> log shipping. The problem is that log shipping puts the db in read only
mode
> and occasionally we need to add user permissions to the secondary only.
The
> only option I see is everytime permissions are needed we would have to
take
> the database out of read only mode, grant the permissions and then put the
db
> back to read only. Does anyone have any other ideas that might work?
Thanks!
|||Anita,
you could add a separate role to the primary server and assign all the
necessary permissions there. Also, add a login to this role. As long as you
have the same login on the secondary server (same SID) the permissions will
be applicable there.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Friday, March 23, 2012

Logshipping steps

logshipping load failure

Logshipping Help Needed

Logshipping help

Logshipping help

Logshipping help

Logshipping ERROR(urgent)

Logshipping ERROR(urgent)

Logshipping ERROR(urgent)

logshipping error

logshipping error

logshipping error

Logshipping

Logshipping

Logshipping

Wednesday, March 21, 2012

LogShipping

Logshipping

Logshipping

Logs Shipping ReInit - how to?

Monday, March 12, 2012

Logins with Log shipping

sql login permissions

Blog Archive

About Me