Best practice fro 'snapshots'

I am throwing this out for ideas...

I need to run a query against up to 4 tables/views and grab then put the results into a database - kind of like a snapshot but not sure if this is the best way to phrase it.

I need to store the results in a format where they do not change and label the new table with datestamp?

Ideas? Pro's/Con's
Who is Participating?
Marten RuneConnect With a Mentor SQL Expert/Infrastructure ArchitectCommented:
Shouldn't you run one transaction in READ COMMITTED SNAPSHOT isolation mode, i e begin transaction, read and then commit transaction. This will ensure you get all rows from all tables in transactionally sync.

Write the lot to a new table that you create in the above transaction (given a special name)

If you don't need many tables, I would choose to write to one table, and set extended properties for that table and in that store date and time for last batch load.

Regards Marten
edrz01Author Commented:
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.