June 4, 2013 at 1:29 pm
I know it's a long shot, but I figured I'd ask.
I know with regular Database Snapshot SQL Server uses spatial data in order to preserve the snapshot, while the original incurs changes. I'm wondering if anyone figured out a round-about way to do the opposite - create a read-only base database, then create one or more a spatial database off this base database where users make changes to their respective spatial database as they please, without affecting the base database.
As of now, the only way it seems to achieve the same result is to actually restore full copies of the database for each user.
June 4, 2013 at 3:05 pm
Spatial data? There's no relation between spatial data types (geometry and geography) and database snapshots.
No, there's no way to create the database equivalent of VM's differencing disks. Restore the users each a copy, let them do as they like with the copy, delete and recreate it as needed.
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
June 4, 2013 at 3:17 pm
I got my Sp's mixed up. I was thinking of Sparse files.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply