It isn't a PIVOT ... you are just assembling single values into the fields of a single row:

with q0 as (

select ...

Evil Kraig F (10/22/2012)

Eventually everything in a shipment/order would have to age past the 2 year mark, at which point I'd archive. Even though yes, they chain, at some...

2 days 2 years 2 millenia won't make any difference as they are all linked in a chain!

WaIIy (7/16/2011)

---

I came to pretty much the same conclusion late last night - Though I'll probably throw a GETDATE() in the BEGINTRAN call for the mark set so I...

this is working for me:

begin tran '20110716_1030' with mark 'NameOfDatabaseSet'

create table db01.dbo.SomeRubbish ( [field] int ); drop table db01.dbo.SomeRubbish;

create table db02.dbo.SomeRubbish ( [field] int ); drop table db02.dbo.SomeRubbish;

...

create table db11.dbo.SomeRubbish...

declare @stopat datetime

set @stopat = {ts'2011-01-01 12:50:00'}

restore database blah from disk = 'blah.bak' with replace, norecovery

restore database blah from disk = 'blah.diff' with norecovery

restore log blah from disk = 'blah1.trn'...

I would be worried if my SQL didn't use 100% of available memory

what is the point in buying the memory if you don't use it?

hopefully we can agree that transaction marks are required for successful restores of related databases

the problem is knowing which marks are in which log file

the solution I came up with...

Jayanth_Kurup (7/14/2011)

---

A Good DR plan has Clustering or DB mirroring to recover from OS level and network level failures , RAID and SAN to recovers from disk and data corruption...

GilaMonster (7/13/2011)

---

Basically I'm not clear why a marked transaction run at exactly 10am is going to give a more consistent restore than a restore stopat 10am when both are prone...

GilaMonster (7/13/2011)

---

If you were marking the transaction that spans the databases I'd agree.

Just having schedules transactions in each individual database every 10 min that mark the log and do nothing...

the difference is...

the link states in a big yellow box with the word "important":

"You can recover related databases only to a marked transaction, not to a specific point in time."

as for why:

why...

Microsoft explain it better than I can:

http://msdn.microsoft.com/en-us/library/ms187014.aspx

Jayanth_Kurup (7/12/2011)

---

I think replication or DB mirroring would be a good fit in the above scenario.

However I think you would suffer significant data loss in your current model because fail...