This project is read-only.

why does the 'create objects' for TCP-E test take over 24 hours to load?

Mar 25, 2011 at 2:46 PM

Hi,

I am running the job for a TCP-E benchmark test against a SQL 2008 R2 64-bit server running on Windows 2008 64-bit server with 32gb RAM and 8 CPU cores. 

It's been running over 24 hours and is only at 75gb in size.   Why does this take so long?  Also, why does it tell me I'm using ODBC when my DSN is using the Native SQL client?  

Any help you can offer would be greatly appreciated. 

 

 

 

Mar 29, 2011 at 5:59 PM

Is this related to the use of SQL Nexus? If yes, please elaborate on the same?

Mar 29, 2011 at 6:49 PM
Hi, I am so sorry I posted this to the wrong forum. This was intended for Quest Software, not SQLNexus.
However I am having issues with the xml file that I downloaded from the codeplex site for SQLNexus 3.0. It works on my local (32-bit) server but not against my 64-bit server. The xml file lists ssver="10". Both of my servers are SQL 2008 R2 RTM so I'm not sure why I'm getting 'There are no instances of version 10 on this computer'.
Is it possible it's got to do with the bits ?
TIA for your reply.
Colleen

From: amitban [email removed]
Sent: Tuesday, March 29, 2011 11:59 AM
To: Rossman, Colleen M
Subject: Re: why does the 'create objects' for TCP-E test take over 24 hours to load? [sqlnexus:251203]

From: amitban

Is this related to the use of SQL Nexus? If yes, please elaborate on the same?


This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.
Mar 29, 2011 at 6:50 PM

No issues. You have to use a x64 version of SQLDIAG to collect the data for a 64-bit instance.

Mar 29, 2011 at 7:08 PM
thank you !


From: amitban [email removed]
Sent: Tuesday, March 29, 2011 12:51 PM
To: Rossman, Colleen M
Subject: Re: why does the 'create objects' for TCP-E test take over 24 hours to load? [sqlnexus:251203]

From: amitban

No issues. You have to use a x64 version of SQLDIAG to collect the data for a 64-bit instance.


This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.
Mar 29, 2011 at 7:43 PM
Sorry to be a pest but I made sure I'm using 64-bit vesion of SQLDiag and I still get the error. I attached the renamed command file for reference.
Colleen

From: Rossman, Colleen M
Sent: Tuesday, March 29, 2011 1:08 PM
To: 'sqlnexus@discussions.codeplex.com'
Subject: RE: why does the 'create objects' for TCP-E test take over 24 hours to load? [sqlnexus:251203]

thank you !


From: amitban [email removed]
Sent: Tuesday, March 29, 2011 12:51 PM
To: Rossman, Colleen M
Subject: Re: why does the 'create objects' for TCP-E test take over 24 hours to load? [sqlnexus:251203]

From: amitban

No issues. You have to use a x64 version of SQLDIAG to collect the data for a 64-bit instance.


This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.
Mar 29, 2011 at 8:09 PM

Just documented some workarounds for the same issue here: http://sqlnexus.codeplex.com/discussions/250274