I will use these objects to see what I can capture on the SQL Server instance.ĪLTER DATABASE SET RECOVERY SIMPLE For the database, I used the below script that will create a database in simple recovery mode, add 1 single table and populate it then create a SQL Login. I installed it as a default instance only and made no configuration changes to SQL Server at this point. It is a default installation (click Next) of SQL Server. I took the default configuration that VMWare Player gave me, and then just installed the specified operating system on it. I have created a simple virtual server using VMWare Player (free) running Window Server 2003 R2 Enterprise Edition (圆4) and SQL Server 2005 SP4 Enterprise Edition (圆4). This will copy all outgoing and incoming packets from your production server to the port your secondary server is on. I would then work with your network engineer/team to have port mirroring configured on the production server's port, to your secondary server's port. If you want to do this in production environment then install Wireshark on a secondary server. So I would not suggest running this on a production server by any means. Please note that Wireshark uses memory to store packet information as it is capturing it. There are some other ones out there, but this is the most popular one, and fairly straight forward to setup and use on Windows operating systems. The network analyzers that are out there are fairly easy to use and obtain. In this tip I will go over what I used for the test, how I set it up, and what I used to test it. So don't expect to much detail on the network packet stuff. I will tell you up front that I am not a network engineer, I'm a DBA.
I decided to build a test lab to find out.
0 kommentar(er)
