Notice you can pick out my server's hostname SHAGGY and then the database I'm connecting to "SeeMyData". I highlighted a few sections of interest. My test connection is shown below that I did from my local desktop to the VM server, along with what Wireshark captured using the filter we set above: ![]() I found a quick method that can be used to do a quick database connection on a user's computers is to create a UDL file (Universal Data Link). I want to do a quick test to make sure my filter is going to actually capture the traffic for my SQL Server instance. If your instance is not configured to use the default port for SQL Server you will need to enter the port your instance is configured to use. This is to capture only the packets that pertain to SQL Server. The only setting I added was typing "port 1433" into the Capture Filter box. Wireshark should list each NIC it detected at startup. If you have more than one NIC on your server (backup network, production network, etc.) you can select the NIC by clicking the drop down arrow beside the 'Interface' box. This is the options window you should see, with my settings shown. The next few screenshots will walk you through how I setup a session in Wireshark. ![]() I have installed Wireshark on the same server SQL Server is running, strictly because this is my test environment. I'm not going to go through the installation, you can go here if you need help with it (pretty much just click 'Next' throughout). Now we need to setup Wireshark to capture our activity. INSERT INTO dbo.UserData VALUES ('Kringer', 'Greyskull', 'TN')ĬREATE LOGIN WITH PASSWORD=N' 'ĬREATE USER FOR LOGIN ĮXEC sp_addrolemember N'db_datareader', N'WhatISee' INSERT INTO dbo.UserData VALUES ('He-Man', 'Greyskull', 'TN') INSERT INTO dbo.UserData VALUES ('Scooby Doo', 'Ghost Town', 'TX') INSERT INTO dbo.UserData VALUES ('Shawn Melton','Montgomery','AL') Populate the table with a few rows of data 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |