April 9, 2008 at 9:36 am
Hi all. Moved a dev server to VMWare and ESX server about 10 days ago (SQL2K, sp4 + a couple of hotfixes). We have several DTS packages on another server that exports data to the new server. They had been running fine when dev was on it's own physical server. Now these jobs fail sporadically with the dreaded "SQL Server Assertion" error. After rebooting the virtual server (sometimes two or three times in a row) the packages complete without issue. Ran DBCC CHECKDB on both source and target databases and they come back clean. Checked event logs on the virtual server but found nothing. Googled "SQL Server Assertion" and found a bunch of hits but nothing definitive - except a lot of them pointing to hardware. I'm not against rolling back to the old server but surely there must be a way to resolve this issue (thankfully, this is a dev environment!). Anyone experience this or have some suggestions on what more I can look at? Thanks.
-- You can't be late until you show up.
April 9, 2008 at 10:06 am
Call PSS. Sounds like something you'll need to dig into with them and I'd really want their blessing if there's a ahrdware issue.
April 9, 2008 at 11:46 am
That's probably what's going to happen. Question though: I've seen a lot about this while searching: max degree of parallelism. I've got to admit, as much as I've been reading about it, I just don't know. Should we set it to 1 and see if that helps? Within EM I only see one processor but I know we've spiked the CPU% upto nearly 100% at times.
-- You can't be late until you show up.
April 10, 2008 at 12:05 pm
Just a followup. This was on the freeware version of VMWare not ESX as I originally stated. We rolled a different server to ESX about two weeks ago without issue. I mistakenly assumed :blush: this was the same setup (thanks infrastructure team!). Anyway, it is a known-about issue (see link below) that has been around for at least 2 years but since it's freeware, there is no urgency to rectify the problem. Can't say as I can blame them but it would be a big relations-boost if they did. They did allow us to open a ticket but no promises of a quick resolution. Suggested purchasing another ESX license as this would be quicker. I'll post more if warranted.
http://communities.vmware.com/message/497671
-- You can't be late until you show up.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply