March 4, 2014 at 8:05 am
Hi All,
You would think that it would be easy to find this information but I guess my googling skills are rusty. I've never had to run a recovery from a t-logs (which is a good thing), and apart from it being good to know, I need some info regarding Transaction Logs. I am working on a DR plan and we need to run log shipping to the DR server. Unfortunately, we are stuck with SQL Server Standard, so I settled on log-shipping as the technique to move data. My question is regarding to what is stored in the T-Log. I know inserts, updates, and deletes are stored but I also wanted to ask about new stored procs, functions, views, roles, logins, password changes, etc. Are all of these stored in the T-Logs as well? I need this information because if any of these are not, I'm going to have to do updates to both the DR site and the production site at the same time.
Thanks again
March 4, 2014 at 8:27 am
Log Shipping takes care of stored procedures, et al. The thing it does not (at least how we use it) do is to keep the jobs and security synchronized.
March 4, 2014 at 8:31 am
Yep, it includes all the changes made within a database, both structure and data, so no worries.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 4, 2014 at 8:32 am
djj (3/4/2014)
Log Shipping takes care of stored procedures, et al. The thing it does not (at least how we use it) do is to keep the jobs and security synchronized.
Say I have a SQL Login titled "SQLAccount_John_Smith" at the global security level on both servers. I also have three new databases, db1, db2, and db3, all of which are being log-shipped to the DR server. If I add RW rights to db1, db2, and db3 for SQLAccount_John_Smith on the production server, will those rights be added on the DR server? My guess is that it will.
March 4, 2014 at 8:34 am
JoshDBGuy (3/4/2014)
djj (3/4/2014)
Log Shipping takes care of stored procedures, et al. The thing it does not (at least how we use it) do is to keep the jobs and security synchronized.Say I have a SQL Login titled "SQLAccount_John_Smith" at the global security level on both servers. I also have three new databases, db1, db2, and db3, all of which are being log-shipped to the DR server. If I add RW rights to db1, db2, and db3 for SQLAccount_John_Smith on the production server, will those rights be added on the DR server? My guess is that it will.
Yes, only DB-level rights will be copied over, but not Server level rights ..
--
SQLBuddy
March 4, 2014 at 8:34 am
Yep, it should be replicated.
March 4, 2014 at 8:48 am
Great, thanks so much!
March 4, 2014 at 10:12 am
If it's a SQL login you have to make sure that the SID for the login is the same on both servers, otherwise the database user won't reference the login and won't be able to access the DB.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply