log shipping will NOT work

I am trying to set up log shipping between some servers. They are in different domain, but there is a two way trust. And I couldn't get it to run inside one domain as well. The SQL agent and SQL server services are running under a domain account that has access to the shares. The jobs actually run but the "last run outcome" remains unknown and the "last run" says never. The error log for these jobs have nothing logged.

Am I missing something here? I have setup and torn this down a million times, and the same thing every time...nothing.

I can also manually backup a log to the Backup share across domains.

Does anyone have a clue what the heck is going on here?

All server are on 9.0.2047.

Thanks,
jason
do you mean to say theres no information in job history ? ? ?.....if the job has run then the sql server agent in either primary or secondary might have been in hanged state........just try to restart the sql server agent and try........anywasys you cud verify if it has run or not by manually logging into the shared folder in primary and see if the tran logs are present........and similarly in secondary check if the tran log files are copied in the secondary servers folder..........else you can check the same in the monitor server which states the recently restored log files in the secondary and the ones which were copied recently and last log file to be backed up in primary|||oh jeez, just a simple restart of the agent did the trick. Thanks for your time.
sql

log shipping status

We have set up log shipping in standby mode so users can run some reports.
Every once in while, the restores long runner and our users would like to
know how much more time before its done.
Is there any query they could run to see what files its restoring or the
last file it has restored so they can get a feel of what Tlog file is being
processed.
It may not be perfect, but its a lot better if they know that the last Tlog
file restored or the current file its restoring is just 10 mins ago vs 10
hrs ago.
Thanks
Hassan
Take a look at DBCC LOGINFO(dbid) command
"Hassan" <hassan@.test.com> wrote in message
news:OIv5slyKIHA.3848@.TK2MSFTNGP05.phx.gbl...
> We have set up log shipping in standby mode so users can run some reports.
> Every once in while, the restores long runner and our users would like to
> know how much more time before its done.
> Is there any query they could run to see what files its restoring or the
> last file it has restored so they can get a feel of what Tlog file is
> being processed.
> It may not be perfect, but its a lot better if they know that the last
> Tlog file restored or the current file its restoring is just 10 mins ago
> vs 10 hrs ago.
> Thanks
>

log shipping status

We have set up log shipping in standby mode so users can run some reports.
Every once in while, the restores long runner and our users would like to
know how much more time before its done.
Is there any query they could run to see what files its restoring or the
last file it has restored so they can get a feel of what Tlog file is being
processed.
It may not be perfect, but its a lot better if they know that the last Tlog
file restored or the current file its restoring is just 10 mins ago vs 10
hrs ago.
ThanksHassan
Take a look at DBCC LOGINFO(dbid) command
"Hassan" <hassan@.test.com> wrote in message
news:OIv5slyKIHA.3848@.TK2MSFTNGP05.phx.gbl...
> We have set up log shipping in standby mode so users can run some reports.
> Every once in while, the restores long runner and our users would like to
> know how much more time before its done.
> Is there any query they could run to see what files its restoring or the
> last file it has restored so they can get a feel of what Tlog file is
> being processed.
> It may not be perfect, but its a lot better if they know that the last
> Tlog file restored or the current file its restoring is just 10 mins ago
> vs 10 hrs ago.
> Thanks
>

log shipping status

We have set up log shipping in standby mode so users can run some reports.
Every once in while, the restores long runner and our users would like to
know how much more time before its done.
Is there any query they could run to see what files its restoring or the
last file it has restored so they can get a feel of what Tlog file is being
processed.
It may not be perfect, but its a lot better if they know that the last Tlog
file restored or the current file its restoring is just 10 mins ago vs 10
hrs ago.
ThanksHassan
Take a look at DBCC LOGINFO(dbid) command
"Hassan" <hassan@.test.com> wrote in message
news:OIv5slyKIHA.3848@.TK2MSFTNGP05.phx.gbl...
> We have set up log shipping in standby mode so users can run some reports.
> Every once in while, the restores long runner and our users would like to
> know how much more time before its done.
> Is there any query they could run to see what files its restoring or the
> last file it has restored so they can get a feel of what Tlog file is
> being processed.
> It may not be perfect, but its a lot better if they know that the last
> Tlog file restored or the current file its restoring is just 10 mins ago
> vs 10 hrs ago.
> Thanks
>

Log Shipping Role Reversal

We're implementing log shipping and have run into problems
when we attempt to reverse server roles.
The error occurs when we run the sp_change_secondary_role.
We receive a "sqlmaint.exe" error. If the stored procedure
is run 3 or 4 times it will occasionally succeed but the
role reversal is not successful even then.
Has anyone had any experience with this?
Thanks,
JohnKen,
See the KB article 294397 BUG: sp_change_secondary_role Fails with Error
3101 if There Are Outstanding Transaction Log Backups
http://support.microsoft.com/defaul...7&Product=sql2k
This is similar, though not identical, to the error you are getting. The
upshot is that you need to make sure that all the transaction logs have been
restored if you set the @.terminate parameter to 1.
Hope this helps,
Ron
--
Ron Talmage
SQL Server MVP
"kmkrause2" <kmkrause2@.discussions.microsoft.com> wrote in message
news:733456B1-BC99-43B2-B6BD-4030A08DB6EC@.microsoft.com...
> I have log shipping configured on a pair of test SQL 2000 servers, both
are
> at SP3. The log shipping is working fine, but the problem occurs when I
try
> to reverse roles. I run this SQL statement on the primary server:
> USE master
> GO
> EXEC msdb.dbo.sp_change_primary_role
> @.db_name = 'ModelCopy',
> @.backup_log = 1,
> @.terminate = 1,
> @.final_state = 3,
> @.access_level = 1
> This places the primary database into read-only mode. I then run this SQL
> statement on the secondary server.
> USE master
> GO
> EXEC msdb.dbo.sp_change_secondary_role
> @.db_name = 'ModelCopy',
> @.do_load = 1,
> @.force_load = 1,
> @.final_state = 1,
> @.access_level = 1,
> @.terminate = 1,
> @.keep_replication = 0,
> @.stopat = null
> At which time I get this error:
> Server: Msg 927, Level 14, State 2, Line 1
> Database 'ModelCopy' cannot be opened. It is in the middle of a restore.
> Server: Msg 5069, Level 16, State 1, Line 1
> ALTER DATABASE statement failed.
> Server: Msg 14440, Level 16, State 1, Procedure sp_change_secondary_role,
> Line 49
> Could not set single user mode.
> In each case, I am runnig the statements in Query Analyzer with the
> Enterprise Manager window closed. I understand that these statements cause
> the primary to make a final copy and the secondary to do a final restore,
but
> the database I'm using is very small (a copy of the Model databae) and
> shouldn't take but a few seconds, which is all the time it took to create
and
> initialize the database on the secondary to begin with. Is this process
hung,
> or am I just being impatient? It's been over 20 minutes.
> TIA,
> Ken|||Thanks for the info Ron. It pointed me in the right direction. I still neede
d
to to a detach/attach sequesnce on the database before running the secondary
stored procedure, but at least it is working in a predictable manner now.
"Ron Talmage" wrote:

> Ken,
> See the KB article 294397 BUG: sp_change_secondary_role Fails with Error
> 3101 if There Are Outstanding Transaction Log Backups
> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;294397&Product=sql2k[/ur
l]
> This is similar, though not identical, to the error you are getting. The
> upshot is that you need to make sure that all the transaction logs have be
en
> restored if you set the @.terminate parameter to 1.
> Hope this helps,
> Ron
> --
> Ron Talmage
> SQL Server MVP
> "kmkrause2" <kmkrause2@.discussions.microsoft.com> wrote in message
> news:733456B1-BC99-43B2-B6BD-4030A08DB6EC@.microsoft.com...
> are
> try
> but
> and
> hung,
>
>|||OK, I spoke too soon. Occasionally, the sp_change_secondary_role procedure
will end with a "sqlmaint.exe failed. [SQLSTATE 42000][Error 22029].
The step
failed." message. I haven't been able to find any helpful information on thi
s
message yet. Can you shed some more light on what is happening during this
procedure? Same scripts as posted previously in this thread, and include the
manual running of the restore job and a database detach/attach sequence in
Enterprise Manager immediately prior to running the secondary role change
stpred procedure.
Thanks Again,
Ken
"kmkrause2" wrote:
[vbcol=seagreen]
> Thanks for the info Ron. It pointed me in the right direction. I still nee
ded
> to to a detach/attach sequesnce on the database before running the seconda
ry
> stored procedure, but at least it is working in a predictable manner now.
> "Ron Talmage" wrote:
>

Log Shipping Question

Hello,
I want to setup SQL Log Shipping btwn two servers.
- Do the servers have to run same version of Windows? Can one be Win2003 and
the other Win2K Server? Or one Win2k Advanced and one Win2k Standard Server?
- Do I have to run the same version/build/ServicePack of SQL Server?
many thanks
christos
If you are using the Enterprise Edition of SQL Server's Log Shipping
functions both SQL Server's have to be Enterprise Edition. If you are
rolling your own version of Log Shipping, there are no SQL Server version
requirements or OS requirements (other than NT workstation/server, XP
professional, Win2k server/professional, Windows 2003).
"Christos Kritikos" <ChristosKritikos@.discussions.microsoft.com> wrote in
message news:D025AB19-599D-4806-9817-2804C182F38A@.microsoft.com...
> Hello,
> I want to setup SQL Log Shipping btwn two servers.
> - Do the servers have to run same version of Windows? Can one be Win2003
and
> the other Win2K Server? Or one Win2k Advanced and one Win2k Standard
Server?
> - Do I have to run the same version/build/ServicePack of SQL Server?
> many thanks
> christos
>

Log Shipping Monitor Reqs

Greetings:
Does anyone know if I can install/run the Log Shipping Monitor Utility on
SQL 2000 Standard Edition, or do I need to actually have THREE copies of SQL
Enterprise Edition in order to configure Log Shipping?
I realize the recommendation is to NOT install the monitor utility on the
source server, but can it be installed on the Destination server?
Thanks!
Keith C. Jakobs, MCP
Hello mate,
You DON'T need to have Enterprise Edition to host the log shipping monitor -
I have and use exactly the model your trying to work towards in my
organisation.
Regards
Paul.
"Keith Jakobs, MCP" wrote:

> Greetings:
> Does anyone know if I can install/run the Log Shipping Monitor Utility on
> SQL 2000 Standard Edition, or do I need to actually have THREE copies of SQL
> Enterprise Edition in order to configure Log Shipping?
> I realize the recommendation is to NOT install the monitor utility on the
> source server, but can it be installed on the Destination server?
> Thanks!
> Keith C. Jakobs, MCP
>
>

Log Shipping Issue

I had log shipping set up from serverA to serverB. One day, I start getting the automated SQL Server job failure messages.

JOB RUN: 'Log Shipping Restore for ServerA.db_nm_logshipping' was run on 10/19/2007 at 10:15:46 AM
DURATION: 0 hours, 0 minutes, 0 seconds
STATUS: Failed
MESSAGES: The job failed. Unable to retrieve steps for job Log Shipping Restore for ServerA.db_nm_logshipping.

After a few troubleshooting steps, I eventually removed and remade the maintenance plan and all associated log shipping jobs (or so I thought). For some reason, even though the new log shipping job is working properly, I'm still getting error messages from an old job.

I've ran a number of queries trying to find rogue entries still in system tables that could possibly still be trying to execute this job:

select * from dbo.log_shipping_databases where database_name = 'db_nm'
select * from dbo.log_shipping_monitor
select * from dbo.log_shipping_plan_databases where source_database = 'db_nm'
select * from dbo.log_shipping_plan_history where source_database = 'db_nm'
select * from dbo.log_shipping_plans where plan_name like '%db_nm%'
select * from dbo.log_shipping_primaries where primary_database_name = 'db_nm'
select * from dbo.log_shipping_secondaries where secondary_database_name = 'db_nm'
select * from dbo.sysdbmaintplan_databases where database_name = 'db_nm'
select * from dbo.sysdbmaintplan_jobs
select * from dbo.sysdbmaintplans where plan_name like '%db_nm%'
select * from dbo.sysjobs where name like '%db_nm%'

I couldn't find anything!

Does anyone have any idea what could be transpiring here? Any assistance would be GREATLY appreciated.

Thanks in advance!

-JoeAs a follow-up:

I ended up restarting SQL Agent. That somehow cleared out the issue.

Log Shipping Gap in Log Chain

Log Shipping on SQL 2005 is failing because of a gap in the log chain. The schedule is every 15 minutes, the backup and copy jobs run without issue. The failure occurs early in the morning when there are no users, maintenance activities, or scheduled jobs - this has happened twice since we applied SP2. The database that is participating in the log shipping is approximately 20Gb, and recovery takes several hours.

Are there any known issues with log shipping on SP2? Any ideas why this might be happening? Is there any other information I can provide to help debug this issue?

This seems to be a duplicate of another message. Please see following URL for replies to this question: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1567987&SiteID=1

Log Shipping Gap in Log Chain

Log Shipping on SQL 2005 is failing because of a gap in the log chain. The schedule is every 15 minutes, the backup and copy jobs run without issue. The failure occurs early in the morning when there are no users, maintenance activities, or scheduled jobs - this has happened twice since we applied SP2. The database that is participating in the log shipping is approximately 20Gb, and recovery takes several hours.

Are there any known issues with log shipping on SP2? Any ideas why this might be happening? Is there any other information I can provide to help debug this issue?

This seems to be a duplicate of another message. Please see following URL for replies to this question: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1567987&SiteID=1

log shipping failover to stand by server

Hi Guys
in logshipping to fail over to stand by server do i have
to do any role change
as far as i know i have to run following script at the
stand by server. am i right?
RESTORE DATABASE database_name WITH RECOVERY
EXEC SP_DBOPTION 'database_name', 'read
only', 'false'
EXEC SP_DBOPTION 'database_name', 'dbo use
only', 'false'
pls advice me
Thanks
Biju
Biju,
have a look at 'log shipping, role changes' in BOL. You don't need to run
your script manually, but run
sp_change_primary_role
sp_change_secondary_role
sp_change_monitor_role
Usually the logins have already been transferred so there's nothing else to
do. These sprocs are useful because they'll try to get the last log (the
live one) if at all possible.
HTH,
Paul Ibison
|||BUT I DONT want to change roles.
>--Original Message--
>Biju,
>have a look at 'log shipping, role changes' in BOL. You
don't need to run
>your script manually, but run
>sp_change_primary_role
>sp_change_secondary_role
>sp_change_monitor_role
>Usually the logins have already been transferred so
there's nothing else to
>do. These sprocs are useful because they'll try to get
the last log (the
>live one) if at all possible.
>HTH,
>Paul Ibison
>
>.
>
|||Biju,
the name is perhaps slightly unintuitive. sp_change_secondary_role:
(a) Copies the final production database transaction log backup to the
standby server along with any additional transaction log backups that were
not previously copied.
(b) Disables the log-shipping transaction copy job on the standby server.
(c) Restores all transaction log backups not previously restored to the
standby database and initiates the recovery of the standby database.
(d) Terminates and rolls back all pending transactions.
(e) Sets the access level of the standby database after completion of the
system stored procedure to multiuser mode.
(f) Creates a log-shipping database maintenance plan on the new primary
server for the new production database. The SQL Server Agent job defined in
this plan backs up the transaction log of the new production database to the
folder location you specified when you set up log shipping.
HTH,
Paul Ibison

Log Shipping Error - Failing to save Secondary Server Configurations Err # 14262

I set up Log Shipping with just 2 servers primary and secondary. When I run from the Wizard for the very first time keeps failing at the stage of saving Secondary Server Configuration info. When i instead run the generated script this problem disappears but then restoring of transactions fails - the process can backup transactions from the Primary server , copy them accross to the secondary and fails on the restore. Any ideas why.

Hi Jonathan

When you use the SSMS UI to configure log shipping and it fails, can you give me the error message that should be available in the error dialog?

When you use the generated script to configure log shipping, but the restore fails, have you had a look at the log_shipping_monitor_error_detail tables on both the primary and seconary servers? These tables are in msdb (see BOL for more information) and should provide detailed error information.

Thanks, Mark

|||

Also its good to check whether both the instances have the same MDAC level & service pack, as this will happen if there is such mismatch.

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

|||

Hi Satya

Greetings to you. I managed to resolve the problem of failing to save Secondary Server configuration. I reinstalled SQL Server and the problem disappeared. My next challenge is I want to automate my backup strategy where I have Log Shipping between 6am to 8pm backing up transactions at 20 minute interval. Then Log Shipping between 8pm to 10pm at 1 hour interval then Full database backup daily , once a week , once a month etc. in which case I need to disable Log Shipping .

|||

Hi there Mark!

Thanks for your interest in my problem. I managed to go over the problem. I reinstalled SQL Server and the problem disappeared. However I have a new challenge. I need to automatically setup Log Shipping between 6am to 8pm backing up transactions at 20 minute intervals then Log shipping between 8pm to 10pm at 1hr intervals then automatically disable Log shipping and do Full Database backup at night like midnight per day ,week etc

|||

Hi Jonathan

Glad the problem disappeared.

Do you really need to have two different interval periods for the backups? It is obviously simpler if you only have the one configuration. If you do need the two schedules, then you should be able add a schedule to the backup job that is created. Using the log shipping UI, go to the "Transaction Log Backup Settings" dialog then the "Edit Job" button to pull up the job properties.

Regarding the full backup you do not need to disable log shipping for you to be able to do a full backup. See the topic in BOL titled "Creating Transaction Log Backups" for a description of the log sequence and how transaction log backups are independent of the full backup.

Log Shipping and Backup Jobs = Conflict?

Can we run log shipping alongside our backup plan?
The concern is that the full backup runs overnight and
then diff backups run during the day and at the same time
log shipping occurs every 30 mins - don't both jobs
require the resetting of the archive bit specifying when
the last trn backup took place?
Many thanks in advance for the help, Rgds, Simon.As long as the ONLY log backups are done through log shipping you should be
fine...Whole and differential backups do NOT affect the transaction log...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Simon" <anonymous@.discussions.microsoft.com> wrote in message
news:2494501c46018$ae3cd380$a601280a@.phx
.gbl...
> Can we run log shipping alongside our backup plan?
> The concern is that the full backup runs overnight and
> then diff backups run during the day and at the same time
> log shipping occurs every 30 mins - don't both jobs
> require the resetting of the archive bit specifying when
> the last trn backup took place?
> Many thanks in advance for the help, Rgds, Simon.

Log Shipping and Backup Jobs = Conflict?

Can we run log shipping alongside our backup plan?
The concern is that the full backup runs overnight and
then diff backups run during the day and at the same time
log shipping occurs every 30 mins - don't both jobs
require the resetting of the archive bit specifying when
the last trn backup took place?
Many thanks in advance for the help, Rgds, Simon.
As long as the ONLY log backups are done through log shipping you should be
fine...Whole and differential backups do NOT affect the transaction log...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Simon" <anonymous@.discussions.microsoft.com> wrote in message
news:2494501c46018$ae3cd380$a601280a@.phx.gbl...
> Can we run log shipping alongside our backup plan?
> The concern is that the full backup runs overnight and
> then diff backups run during the day and at the same time
> log shipping occurs every 30 mins - don't both jobs
> require the resetting of the archive bit specifying when
> the last trn backup took place?
> Many thanks in advance for the help, Rgds, Simon.

Log Shipping and Backup Jobs = Conflict?

Can we run log shipping alongside our backup plan?
The concern is that the full backup runs overnight and
then diff backups run during the day and at the same time
log shipping occurs every 30 mins - don't both jobs
require the resetting of the archive bit specifying when
the last trn backup took place?
Many thanks in advance for the help, Rgds, Simon.As long as the ONLY log backups are done through log shipping you should be
fine...Whole and differential backups do NOT affect the transaction log...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Simon" <anonymous@.discussions.microsoft.com> wrote in message
news:2494501c46018$ae3cd380$a601280a@.phx.gbl...
> Can we run log shipping alongside our backup plan?
> The concern is that the full backup runs overnight and
> then diff backups run during the day and at the same time
> log shipping occurs every 30 mins - don't both jobs
> require the resetting of the archive bit specifying when
> the last trn backup took place?
> Many thanks in advance for the help, Rgds, Simon.

Log Shipping (can't "auto_fix" user after db restore)

Anyone,
I've implmented log shipping and it's working fine for the most part, but
since it's in a "read only" state,
I can't run a sp_change_users_login to remap my reports_readonly user to the
login on the secondary server.
Thus, this user can not access the read only database at all.
Anyone else seen this, or have a fix for it.
Thank you,
Wayne
Note the SID of that user in sysusers table within that database.
After that, drop the login and recreate it using sp_addlogin and the most
important being to use the SID noted from the sysusers table above
Look at sp_addlogin in Books Online along with @.sid parameter.. Good luck
!!!
"Wayne" <wgadberry@.comcast.net> wrote in message
news:%23x$ixsqbEHA.368@.TK2MSFTNGP10.phx.gbl...
> Anyone,
> I've implmented log shipping and it's working fine for the most part, but
> since it's in a "read only" state,
> I can't run a sp_change_users_login to remap my reports_readonly user to
the
> login on the secondary server.
> Thus, this user can not access the read only database at all.
> Anyone else seen this, or have a fix for it.
> Thank you,
> Wayne
>
|||i'll give it a shot... thanks..
Wayne
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:ekyMEmubEHA.3636@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Note the SID of that user in sysusers table within that database.
> After that, drop the login and recreate it using sp_addlogin and the most
> important being to use the SID noted from the sysusers table above
> Look at sp_addlogin in Books Online along with @.sid parameter.. Good luck
> !!!
>
> "Wayne" <wgadberry@.comcast.net> wrote in message
> news:%23x$ixsqbEHA.368@.TK2MSFTNGP10.phx.gbl...
but
> the
>
|||Worked like a champ Hassan.. you the man..
Wayne
"Wayne" <wgadberry@.comcast.net> wrote in message
news:%23wqQ3RzbEHA.2816@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> i'll give it a shot... thanks..
> Wayne
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:ekyMEmubEHA.3636@.TK2MSFTNGP10.phx.gbl...
most[vbcol=seagreen]
luck[vbcol=seagreen]
> but
to
>

Log Shipping (can't "auto_fix" user after db restore)

Anyone,
I've implmented log shipping and it's working fine for the most part, but
since it's in a "read only" state,
I can't run a sp_change_users_login to remap my reports_readonly user to the
login on the secondary server.
Thus, this user can not access the read only database at all.
Anyone else seen this, or have a fix for it.
Thank you,
WayneNote the SID of that user in sysusers table within that database.
After that, drop the login and recreate it using sp_addlogin and the most
important being to use the SID noted from the sysusers table above
Look at sp_addlogin in Books Online along with @.sid parameter.. Good luck
!!!
"Wayne" <wgadberry@.comcast.net> wrote in message
news:%23x$ixsqbEHA.368@.TK2MSFTNGP10.phx.gbl...
> Anyone,
> I've implmented log shipping and it's working fine for the most part, but
> since it's in a "read only" state,
> I can't run a sp_change_users_login to remap my reports_readonly user to
the
> login on the secondary server.
> Thus, this user can not access the read only database at all.
> Anyone else seen this, or have a fix for it.
> Thank you,
> Wayne
>|||i'll give it a shot... thanks..
Wayne
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:ekyMEmubEHA.3636@.TK2MSFTNGP10.phx.gbl...
> Note the SID of that user in sysusers table within that database.
> After that, drop the login and recreate it using sp_addlogin and the most
> important being to use the SID noted from the sysusers table above
> Look at sp_addlogin in Books Online along with @.sid parameter.. Good luck
> !!!
>
> "Wayne" <wgadberry@.comcast.net> wrote in message
> news:%23x$ixsqbEHA.368@.TK2MSFTNGP10.phx.gbl...
but[vbcol=seagreen]
> the
>|||Worked like a champ Hassan.. you the man..
Wayne
"Wayne" <wgadberry@.comcast.net> wrote in message
news:%23wqQ3RzbEHA.2816@.TK2MSFTNGP11.phx.gbl...
> i'll give it a shot... thanks..
> Wayne
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:ekyMEmubEHA.3636@.TK2MSFTNGP10.phx.gbl...
most[vbcol=seagreen]
luck[vbcol=seagreen]
> but
to[vbcol=seagreen]
>

Log Shipping (can't "auto_fix" user after db restore)

Anyone,
I've implmented log shipping and it's working fine for the most part, but
since it's in a "read only" state,
I can't run a sp_change_users_login to remap my reports_readonly user to the
login on the secondary server.
Thus, this user can not access the read only database at all.
Anyone else seen this, or have a fix for it.
Thank you,
WayneNote the SID of that user in sysusers table within that database.
After that, drop the login and recreate it using sp_addlogin and the most
important being to use the SID noted from the sysusers table above
Look at sp_addlogin in Books Online along with @.sid parameter.. Good luck
!!!
"Wayne" <wgadberry@.comcast.net> wrote in message
news:%23x$ixsqbEHA.368@.TK2MSFTNGP10.phx.gbl...
> Anyone,
> I've implmented log shipping and it's working fine for the most part, but
> since it's in a "read only" state,
> I can't run a sp_change_users_login to remap my reports_readonly user to
the
> login on the secondary server.
> Thus, this user can not access the read only database at all.
> Anyone else seen this, or have a fix for it.
> Thank you,
> Wayne
>|||i'll give it a shot... thanks..
Wayne
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:ekyMEmubEHA.3636@.TK2MSFTNGP10.phx.gbl...
> Note the SID of that user in sysusers table within that database.
> After that, drop the login and recreate it using sp_addlogin and the most
> important being to use the SID noted from the sysusers table above
> Look at sp_addlogin in Books Online along with @.sid parameter.. Good luck
> !!!
>
> "Wayne" <wgadberry@.comcast.net> wrote in message
> news:%23x$ixsqbEHA.368@.TK2MSFTNGP10.phx.gbl...
> > Anyone,
> >
> > I've implmented log shipping and it's working fine for the most part,
but
> > since it's in a "read only" state,
> > I can't run a sp_change_users_login to remap my reports_readonly user to
> the
> > login on the secondary server.
> > Thus, this user can not access the read only database at all.
> > Anyone else seen this, or have a fix for it.
> >
> > Thank you,
> > Wayne
> >
> >
>|||Worked like a champ Hassan.. you the man..
Wayne
"Wayne" <wgadberry@.comcast.net> wrote in message
news:%23wqQ3RzbEHA.2816@.TK2MSFTNGP11.phx.gbl...
> i'll give it a shot... thanks..
> Wayne
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:ekyMEmubEHA.3636@.TK2MSFTNGP10.phx.gbl...
> > Note the SID of that user in sysusers table within that database.
> >
> > After that, drop the login and recreate it using sp_addlogin and the
most
> > important being to use the SID noted from the sysusers table above
> >
> > Look at sp_addlogin in Books Online along with @.sid parameter.. Good
luck
> > !!!
> >
> >
> > "Wayne" <wgadberry@.comcast.net> wrote in message
> > news:%23x$ixsqbEHA.368@.TK2MSFTNGP10.phx.gbl...
> > > Anyone,
> > >
> > > I've implmented log shipping and it's working fine for the most part,
> but
> > > since it's in a "read only" state,
> > > I can't run a sp_change_users_login to remap my reports_readonly user
to
> > the
> > > login on the secondary server.
> > > Thus, this user can not access the read only database at all.
> > > Anyone else seen this, or have a fix for it.
> > >
> > > Thank you,
> > > Wayne
> > >
> > >
> >
> >
>