Replicate SQL activity from production to pre-production server
Posted on 2007-07-19
Production DB: 15GB
ServerA: Windows Server 2000 Standard, SQL 2000 Standard, Quad Xeon MP 1.8ghz, 4 GB RAM
ServerB: Windows Server 2003 Enterprise 64bit, SQL 2005 Standard 64bit, Quad Xeon MP 3.16ghz, 8 GB RAM
How can I replicate the activity on ServerA to ServerB (transaction by transaction) so we can observe, over a time, the performance differences from ServerA compared to ServerB?
Our production DB is running on ServerA. Given the RAM limitations of ServerA's OS/SQL software, we cannot use the entire 4 GB of ram. The DB is about 15 GB and we need to have as much in RAM as possible. This leads to significant performance problems, locking, blocking, headaches and user complaints.
Segway to ServerB.
We want to migrate to ServerB as soon as possible; however, we want to test ServerB's capabilities to determine the amount of performance improvements this will give us before actually migrating. It is configured with the same drives, RAID, just updated software and MUCH faster hardware.
There is a monitoring workstation running Idera SQL Diagnostic Manager so we can look at a side-by-side comparison.
Upgrading ServerA to Windows Server 2003 Enterprise, SQL 2005 Stanard (32-bit). The idea is to better leverage the hardware and create a mirror instance and another instance for development staff to use.
We are not married to this plan and open to suggestions if there is a better one which can be suggested.