Vista - Virtualisation

Hi,

We recently Virtualised our servers. Basically we had two physical
servers and now we have a vertual server.
We run a couple of Web applications on the VM server. We had
everything running fine for a while - until we got a timeout problem
with a search function. Basically a page does a search call to SQL
server and that kind of tookl more than the default SQL Command
Execution timeout which is set to 30 secs my MS.

To resolve that problem, we set CommandTimeout property of the
SQLCommand object as well as the
SQLConnection object - to 0 - this makes the timeout to be unlimited.

The code snippet below shows what we did:
Note: that the CommandTimeout is set at both the SQLConnection and
SQLCommand levels !!

....

aConnection = New SqlConnection(tmpString &
";Database=myDB;Trusted_Connection=True;Connection Timeout = 0;")
mCommand = New SqlCommand(strStoredProcedureName, aConnection)
mCommand.CommandType = CommandType.StoredProcedure
mCommand.CommandTimeout = 0
....

The question is: can this stuff up the Virtual Server setup in anyway?

We are not sure what is causing the problem - but we are having a
network blockage and memory degradation which is of course resulting
in Client Connection being everlasting... i.e frozen screen.

We are suspecting the above code snippet.

Will someone please respond ASAP ---

Thanks.

I don't suspect that this code is causing you problems, but have you tried
removing the code to see if the problem improves?

Also, you mention that you have converted the physical servers to virtual.
If running Virtual Server and you fail to install the Virtual Server
Additions or Integration Components if running Hyper-V, this can lead to less
than desirable functionality and performance.

"billion.mohammed@newsgroup" wrote:

<billion.mohammed@newsgroup> wrote in message
news:763803f0-b9f9-4d51-86d8-97d96747b995@newsgroup
Where is the SQL server? How is it connected to the vm? What
virtualization product are you using?