Microsoft SQL DB Testing


We have a software provider that periodically provides updates to our server-side software. These updates make changes to the stored procedures in the database for that software. After we have tested the updates on our test server, we then send live traffic to the test server for a brief amount of time to test the performance.  Once we switch back to the primary server, the traffic that went  to the test server is unfortunately lost. While the database gets a lot of traffic the writes to the database haven't been particularly important so five minutes of lost data wasn't important. That has recently changed. I'm now looking for a way that we can switch between servers without losing data.

I initially looked into database mirroring which seemed to be what we were looking for. Problem is, the stored procedures are mirrored right along with the data. So that won't really work since the updates provided change the stored procedures as well.  So I'm now looking into database clustering but I'm not really sure if clustering will solve my problem either. I need a solution that will allow us to have different software and stored procedures on two servers but not lose the data sent to the test server. Is clustering what I'm looking for? If so, is there a specific way of setting it up to get the results I'm looking for? Or is there another way to do this?

Thanks in advance for your help!
Who is Participating?
Lara FConnect With a Mentor EACommented:
what we usually do in similar situation - we will record all trace on production server for some period of time 5 minutes or 5 hours  - then run those trace in updated test environment to test performance - then we update production to new software.
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.