@Erik Good luck with the sale and the move!

@Erik You're welcome, and thanks for voting and commenting. And, yes, good look with the sale and the move.

Best part is last paragraph in Burki's answer.

> As a result, all programmers of earth will almost imediately after that discovery migrate to the new planet, and will forever be happy coders that don't have to deal with time zone handling any more.

You're such a gentleman

@PaulWhite the parameters were there from the beginning. But the code was not in a code block and the [tablename](data.Location,'/') was marked as a link by markdown.

@ypercubeᵀᴹ Oh I see. Ok.

Comment updated.

I have a question, and feel free to let me know if it should be a main-site question: is there an easy way (aka how) can I create a shadow copy of a database on the same server in SQL Server 2012? Aka, I have a DB MainDB that I want to grant users the ability to read data on, but I don't want any chance of them being able to do any changes to structure/data.

So I want MainDB and MainDB_Shadow to be a copy of the source DB.

@EBrown Have you looked into Database Snapshots?

@EBrown These can have an impact on IO intensive processes.

@wBob IO reads or writes?

It only writes data for about 5 minutes at 00:00UTC+00:00, then there are no more writes until the next day.

@EBrown Both really. Writes because data has to be written to the snapshot when changed in the source, reads because potentially you would have to read pages from original source database and snapshot in same query, I think.

@EBrown Google this: "Database Snapshot Performance Considerations under I/O-Intensive Workloads"

@wBob That's an interesting document.

@EBrown Possibly a bit out-of-date but still worth a look.

@EBrown If your process is not that I/O intensive then it's less of a concern.

@wBob The writes are, but not overly intensive.

Actually, it's really not intensive at all. It only inserts/updates ~2500 records in the 2.5-3 minute span.

~16 inserts/updates a second