October 1, 2013 at 12:49 pm
Hi, All
This is my project which i am going to work on.
-- have to install and configure test/dev/prod databases using SQL 2008 and the database have the potential to grow 1t+ (need suggestions and best practices on hardware and software) environment is vmware
-- have to keep the prod and dev and test databases in sync all the time
-- the test data gets new data weekly through SSIS packages.
updated the requirement
issue one ---in the diagram the idea is to keep the load db and reporting databases 1 and 2 in sync.
issue two --- we get request from front end to make a change in reporting 1 and it has to take place in 30min its just a time frame.
issue three--- can we keep the reporting db1 and load db in sync even if there are changes done.
Thank you for every one for looking at my post
October 1, 2013 at 2:09 pm
Just a suggestion...
Keeping a reporting database in sync with production is a fine idea. Keeping a development database in sync with production is going to be a very painful thing especially for the developers.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 1, 2013 at 5:10 pm
I'm with Jeff. Keeping dev in sync with prod is a bit of a problem.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
October 2, 2013 at 6:15 am
I too will tell you that keeping them in sync is going to be a hard task.
Do you have SAN drives on these VMs? If so, you might look at a nightly job to sync the data up, so you get a fresh copy daily rather than continously syncing.
Jason Carter
Tampa, Florida
"Anyone who stops learning is old, whether at twenty or eighty. Anyone who keeps learning stays young. The greatest thing in life is to keep your mind young" - Henry Ford
October 2, 2013 at 9:22 am
yes we do have SAN
October 2, 2013 at 9:23 am
thank you ALL and there is slightly change in the requirement
October 2, 2013 at 9:26 am
On a couple of our QA servers, we have daily jobs that will detach the database, copy a drive via SAN specific commands, then reattach the newly copied database. SAN copies are much faster than copying via windows.
We also run a few other processes after wards to get our QA users permissioned.
Basically automated data refreshes for DEV and QA. Hope the idea helps.
Jason Carter
Tampa, Florida
"Anyone who stops learning is old, whether at twenty or eighty. Anyone who keeps learning stays young. The greatest thing in life is to keep your mind young" - Henry Ford
October 2, 2013 at 9:32 am
thanks and how to put databases in sync when the date is changing in both at different timings?
October 2, 2013 at 9:36 am
My suggestion is for a once a day sync, not continuous.
Using my suggestion you would have a fresh copy of production every morning. Anything you did in DEV/QA yesterday is gone.
Jason Carter
Tampa, Florida
"Anyone who stops learning is old, whether at twenty or eighty. Anyone who keeps learning stays young. The greatest thing in life is to keep your mind young" - Henry Ford
October 2, 2013 at 10:19 am
harita (10/2/2013)
thanks and how to put databases in sync when the date is changing in both at different timings?
Why would you want to have the dev database perfectly in sync with your production database?
This a nightmare to manage, and a nightmare for the developers who must continually deal with the constant changes. Not to mention regulatory requirements of scrubbing production data when used in a QA or dev type of environment.
Do the once a day method. You will save you and your boss plenty of hair that way.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply