SQL Server (Driver?) Issues

Hello...

Parallels Build 1884 RC running on a Mac Pro, with a WIndows XP guest OS

I'm doing .NET development in VIsual Studio 2005; my application hits a SQL Server 2000 database on another machine in my local network.

I'm having weird (but very reproducible) time-out issues on certain SQL queries - it seems to be related to the size of the dataset returned.

Small queries that return a single result with only a couple of fields work fine.

Other queries which return many rows or a single row with many fields go into limbo, until the System.Data.SqlClient operation times out.

It's not the queries that are the problem, they've been running fine in production on pure Windows systems, and have been for ages.

I've started looking at the server side of the issue to see what's happening, but no major clues yet.

Anyone seeing similar behavior? (probably not...)

Anyone have any ideas?

Anyone from Parallels got any ideas?

Thanks!

Edit:

here's the stack trace..

at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32 bytesExpected)
at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
at System.Data.SqlClient.TdsParserStateObject.ReadByte()
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior)
at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable)
at Mandy.ado_plumbing.GetDataSet(String sql, String CallingFunction, String CallingClass) in C:\Documents and Settings\[redacted]\classes\data\ado_plumbing.vb:line 268

 

Does it work on release version - build 1848?

 

i'm on a mac pro, so that build gives me an instant kernel panic.

 

woo!

the "latest internal build - 1896.2" as mentioned in this thread cured my problem nicely. many thanks!