VMWare Memory Issue with Heavy SQL Server queries

Scenario: We have 2 guest systems one is a file sharing server, and the other is a SQL server. Both systems, have memory allocated, and are attached to a SAN.



Problem: We are running intense queries to this SQL Server also we are importing information from files that are located on the File Server into a SQL database that is located on another ESX server.

Issue:
What we are seeing is the file that we are trying to import into our SQL database *(SQL Server is located on a Different ESX Server).
Is getting Information injected from the intense query.

NOTE: The only file with the injected information is the one that is being loaded into memory.

If we reboot the File Server we can go back and check the file in question and see that the file will no longer have the injected information.

We can also stop all queries and imports and only execute the queries. Once the memory block, for which the file that has the injected information gets over written, we can then open the file in question and see that the injected information will no longer be there.

Has anyone seen this before any help would be great?

Thanks
Phytech AdminAsked:
Who is Participating?
 
Phytech AdminConnect With a Mentor Author Commented:
Each port on the storage processor is considered a target.
 
For example  a0 and b0 are on 192.168.1.1 network
If  a1 and b1 are on the same 192.168.1.1 subnet then a1 target becomes an initiator
and tries to log into the a0 port now we have a loop that is ping ponging the port up and down .
 
Now if we have 2 subnets per pair
 
A0 and B0 are on 192.168.1.1
And A1 and B1 are on 192.168.2.1
Then we have no conflicts target versus initiator.
0
 
vmwarun - ArunCommented:
How have you configured your LUNs ? Is the LUN visible to both ESX Hosts ?
0
 
Phytech AdminAuthor Commented:
Yes, LUNs are configured for Both ESX servers, the imported flat-files are being read from the LUN on the files server. We are runing iSCSI with SATA Drives
0
Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
Phytech AdminAuthor Commented:
I failed to mention that the 2 Guest OS Systems are located on the same ESX Server.
The server, where we are running the import from is on another SQL Server, importing into a different database. This SQL server is located on another ESX Server.

So that theres no confusion, file means flat-files i.e. (row of data)

Please let me know if i need to put more information.
Thanks
0
 
za_mkhCommented:
I don't know what you are talking about specifically, but have you reindexed your DBs recently? That normally sorts out speed issues (well I'm a SQL noob) but it works for our SQL servers. We don't have issues like what you mention though.
Also have you followed best practices for configuring SQL in VM?
http://communities.vmware.com/docs/DOC-8964
http://technet.microsoft.com/en-gb/library/cc966534.aspx
Another thing is that I think you may be hitting an IO limit with your storage (ISCSI with SATA). SATA itself is not great for heavy loads, proven, though it works. It depends on how your underlying storage on which your VMFS volume is configured, ex how many spindles, etc.
Do you have dedicated NICs on your ESX Hosts for ISCSI traffic (with hopefully a dedicated switch for ISCSI traffic) or are all your guests and server sharing the same NIC ports, etc ... this could also be another area to look at.
0
 
Phytech AdminAuthor Commented:
We have dedicated NICs on the ESX hosts for ISCSI traffic and a dedicated switch,
all are guests are using one nic for the data network traffic they are not connected to the iSCSI network.
0
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.