February 5, 2008 at 5:37 am
Hi guys i have a SQL 2005 ent edition server (RTM) for which i have configured logshipping.The timestamp for the transaction logs created is like the foll
DB_20080205123016.trn at time 6:00 PM.Is this a bug.Can this be corrected.
thanks
February 6, 2008 at 1:27 am
Could it be using universal time for the timestamp? What timezone are you in - GMT+/- how much? My guess is you're in India (IST) which is GMT + 5h30.
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
February 6, 2008 at 1:39 am
Hi,
i am in the India time zone GMT+ 5:30
February 6, 2008 at 1:46 am
ok - that's the issue then. I don't know off the top of my head - I don't believe that you can control it without rolling your own log shipping. Hmm - try looking in the log shipping jobs themselves maybe?
Why do you care anyway? As long as they're sequential you're fine.
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
February 6, 2008 at 1:51 am
Ya i guess it's not much of a problem as the log shipping is in sync.I was just thinking whether its a bug or something.
thanks anyways..
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply