<div>
I guess it really does it need to be current, actually. <br />
<br />
Yes we use some Red Gate tool for a weekly refresh to QA, so actually, that is probably fine.
</div>


<div>
<div class="content wysiwyg-content">
I need to upgrade one of our QA test sites to have the exact version of every service running in Production, and to have some form of mirrored database running on the QA site. I guess it's mainly that I would need a load on the system, which can be replicated by the flow of data.<br />
<br />
What are my options for data concurrency?<br />
<br />
I assume there is a setting on SQL Serve 2012 to clone any changes on the Production database back to our mirrored site. But with testing taking place on the QA site, and new data being generated, I see risks of data being rejected by the database.<br />
<br />
Even though the production database would have many more transactions than the QA database, I see the risk that data being mirrored from Production &nbsp;would be getting inserted into a different database. Different because there would be a small number of records being added by testing.<br />
<br />
How can I best accomplish my goal of a test environment that is near identical to Production?<br />
<br />
Thanks
</div>
</div>


I need to upgrade one of our QA test sites to have the exact version of every service running in Production, and to have some form of mirrored database running on the QA site. I guess it's mainly that I would need a load on the system, which can be replicated by the flow of data.

What are my options for data concurrency?

I assume there is a setting on SQL Serve 2012 to clone any changes on the Production database back to our mirrored site. But with testing taking place on the QA site, and new data being generated, I see risks of data being rejected by the database.

Even though the production database would have many more transactions than the QA database, I see the risk that data being mirrored from Production  would be getting inserted into a different database. Different because there would be a small number of records being added by testing.

How can I best accomplish my goal of a test environment that is near identical to Production?

Thanks

I guess it really does it need to be current, actually. 

Yes we use some Red Gate tool for a weekly refresh to QA, so actually, that is probably fine.

Need a mirrored QA test site

I need to upgrade one of our QA test sites to have the exact version of every service running in Production, and to have some form of mirrored database running on the QA site. I guess it&#39;s mainly that I would need a load on the system, which can be replicated by the flow of data.

What are my options for data concurrency?

I assume there is a setting on SQL Serve 2012 to clone any changes on the Production database back to our mirrored site. But with testing taking place on the QA site, and new data being generated, I see risks of data being rejected by the database.

Even though the production database would have many more transactions than the QA database, I see the risk that data being mirrored from Production  would be getting inserted into a different database. Different because there would be a small number of records being added by testing.

How can I best accomplish my goal of a test environment that is near identical to Production?

Thanks

The term "Backup" means the methods and processes involved to copy computer data (system data as well as application data) to media other than the ones where the data originally live (disk, tape, optical, cloud). "Restore" in turn means the methods and processes involved in data recovery, i. e., bringing back copied computer data to their original location. Backup/Restore primarily serves as a means of protection against data loss, be it due to disaster, corruption or sabotage. It can also be used for recovering data from an earlier point in time and even for cloning machines or applications. There is a wide variety of backup/restore software available, from expensive commercial products to free or open source tools.

Storage Software

Databases are organized collections of data, most commonly accessed through management systems including schemas, tables, queries and processes that allow users to enter and manipulate the information or utilize it in other fashions, such as with web applications or for reporting purposes.

Databases

Microsoft SQL Server 2008 is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning. Major improvements include the  Always On technologies and support for unstructured data types.

Microsoft SQL Server 2008

Cloud computing, also known as on-demand computing, is a kind of Internet-based computing where shared resources and information are provided to computers and other devices. It is a model for enabling ubiquitous, on-demand access to a shared pool of configurable computing resources. Cloud computing and storage solutions provide users and enterprises with various capabilities to store and process their data in third-party data centers, relying on sharing of resources to achieve coherence and economies of scale.

Cloud Computing

Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.