do some errors more prone to SQL server on VMs?

From your experience, have you seen some errors repeat more so in the virtual environment more than
 SQL servers hosted in physical boxes?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

25112Author Commented:
for example, when we run the below, we get them only in the boxes that are virtual.. we have not seen this error in any of the physical servers so far:

EXEC master.dbo.xp_readerrorlog 0, 1, 'Error: 823'  
EXEC master.dbo.xp_readerrorlog 1, 1, 'Error: 823'
EXEC master.dbo.xp_readerrorlog 2, 1, 'Error: 823'
EXEC master.dbo.xp_readerrorlog 3, 1, 'Error: 823'
EXEC master.dbo.xp_readerrorlog 4, 1, 'Error: 823'
EXEC master.dbo.xp_readerrorlog 5, 1, 'Error: 823'
EXEC master.dbo.xp_readerrorlog 6, 1, 'Error: 823'
EXEC master.dbo.xp_readerrorlog 0, 1, 'Error: 824'  
EXEC master.dbo.xp_readerrorlog 1, 1, 'Error: 824'
EXEC master.dbo.xp_readerrorlog 2, 1, 'Error: 824'
EXEC master.dbo.xp_readerrorlog 3, 1, 'Error: 824'
EXEC master.dbo.xp_readerrorlog 4, 1, 'Error: 824'
EXEC master.dbo.xp_readerrorlog 5, 1, 'Error: 824'
EXEC master.dbo.xp_readerrorlog 6, 1, 'Error: 824'
 could you try this in your VM box vs physical box in non-peak hours to confirm/check/infer?
Kelvin SparksCommented:
I have tried this on both a physical server, and a vm - both work correctly.

Please note the following change

EXEC master.dbo.xp_readerrorlog 0, 1, N'Error: 823'  

Without the N (for nvarchar) it would not work in either.

25112Author Commented:

>>I have tried this on both a physical server, and a vm - both work correctly.
you mean you got zero entries back.. meaning no such errors at all? was it 2008?

>>Without the N (for nvarchar) it would not work in either.
It brings back records for me? I thought it won't work only if there are Unicode characters inside the quotes?
Ryan McCauleyData and Analytics ManagerCommented:
Any occurrence of those errors is a major concern, regardless of whether it's on a physical or virtual server. Both of those errors (823 and 824) are serious file consistency errors that indicate a massive concern at the storage layer (or at the OS layer as it communicates with storage). I'd immediately raise the issue with your OS and Storage Administrators (if that's not also you) to try and find the cause.

That said, there's nothing about a VM that would cause issues of any kind to occur more frequently than on a physical server - it should be transparent to the virtualized OS and applications, so they should be unaware of whether the host is physical or virtual. That said, virtualized environments have an additional layer of abstraction between the application and the hardware - instead of app -> OS -> hardware, it's app -> OS -> hypervisor -> hardware, which is an additional place that problems can arise. It will tend to exacerbate any latency or resource crowding issues you're already experiencing, so VMs tend to expose issues that already exist.

For these errors in particular, it's an indication that the VM can't save reliably to the shared storage. Since you don't see the issue on your physical servers, what's different about the VMs that would cause these storage issues to manifest? Some questions to ask:

 - Are other VMs on the server experiencing slow storage access times, or just the SQL Servers?
 - Are you using iSCSI or Fiber for your storage? iSCSI can be impaired by other network bandwidth issues, so check your switches - Fiber switches can also get crowded and lead to impairments, but they're significantly faster and tend to be dedicated to storage, but something to check.
 - Are all the VMs hosted by a single virtual host machine? If so, is there an issue with the HBA or storage access in that server?
 - Is the host machine(s) under these VMs crowded for resources, meaning the VMs can't get the resources they need in an acceptable amount of time?

I'd check the performance and resource load of the host underneath these VMs to see if it looks like there's a problem there. Though it could be related to the actual storage as well, but since you're only seeing it on the VMs and not the physical SQL Servers, I'd expect it's an issue present on the physical VM host machines rather than at the storage layer.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
25112Author Commented:
thank u for the detailed response and help-guidance!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.

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.