64-bit Reporting Services 2005 single-threading?

We're running on an AMD 8-core Opteron, with Enterprise RS 2005 64-bit.
It seems that when we have multiple users running reports at the same time,
the mdx queries get executed in parallel to the AS database, but the
processing of the data by reporting services is done in a single-thread mode.
E.g. a report run by itself takes 15 seconds. Same report run by 5 people can
take 3:30 to return (with the w3wp taking up the equivalent of only 1 core).
My laptop running RS 2005 processes these simultaneous report faster than our
Opteron!!!
We played with setting the # of workers on the IIS Appl Pool, and it does
seem to cause multiple reports to be processed simultaneously, but I don't
think this is the best solution. I think we are running the equivalent of 8
copies of reporting services on the box in this configuration -- I see 8 RS
logs being generated.
Is there a setting in either IIS or RS 2005 to make it process requests in
parallel?
SteveHi Steve,
Me too, interested to know the answer to your question. If you find out -
please update.
Thanks,
Al
"SteveIrwin" wrote:
...
> Is there a setting in either IIS or RS 2005 to make it process requests in
> parallel?
> Steve|||It looks like the App Pool that gets created for RS has CPUAffinity assign to
it, I think. When you create another App Pool in IIS, and switch the
Reporting Services vdir to use the new pool, then it behaves like a regular
website -- one worker process that answers all requests that come to it,
spawning multiple threads if necessary.
So it comes down to how you want to have RS to work: do you want one worker
that spawns threads to handle requests, or have multiple workers that will
each take up only one cpu/core for each request, then move on to the next
request. It would be interested to see any whitepapers on this subject.
Steve
"TheTechie" wrote:
> Hi Steve,
> Me too, interested to know the answer to your question. If you find out -
> please update.
> Thanks,
> Al
> "SteveIrwin" wrote:
> ...
> > Is there a setting in either IIS or RS 2005 to make it process requests in
> > parallel?
> >
> > Steve

64-Bit Installation of SQL Server 2005 on AMD Server

I have an 8-Processor AMD CPU box with Windows Server 2003 Enterprise (x64) R2 with SP1 installed.

How do I verify that I am installing the 64-Bit version of SQL Server 2005? I don't see any installer 'options' and when I view the list of SQL Server 2005 components in the Add/Remove program list there is nothing mentioned.

The source of my SQL Server 2005 installation code is the 'Ready Set Launch' DVD that Microsoft handed out when SQL Server 2005 was launched in 11/2005.

I haven't found any documentation to specifically details 64-bit installations.

Thank you.

...cordell...

The media itself must be the 64-bit version of SQL 2005. Since your AMD box will support both 32-bit and 64-bit versions, it's tough to tell what you're installing. After installing, the 64-bit versions have a "(64-bit)" tag on the end of them in Add/Remove Programs. My guess is that you have a copy of the 32-bit version.

Thanks,
Sam Lester (MSFT)

|||

Sam...

From what I can see I am installing the 32-bit versions of the SQL Server 2005 software on the AMD box.

I apologize for being pedantic here.....but I wanted to confirm that I will need to follow back up with my software vendor and order a 64-bit version of SQL Server 2005. (This is what I am concluding from your statements.)

After searching around the SKU I have is 228-05237 for this version...but I couldn't find anything in the SQL Server section of the MS website to confirm it. While I realize you are not in sales...what would the URL be for confirming the SKU on the media.

Thank you.

...cordell...

|||

No problem at all. You will need to contact your software vendor and specifically request the 64-bit version. I don't fully understand the licensing options for every situation, but I think this page will help you find the SKU/item number you are looking for. I have linked the Enterprise SKU's, but you can search for the others as well.

http://www.microsoft.com/PRODUCTS/info/product.aspx?view=22&pcid=d635228e-6aed-404b-9af1-7c27819c24e4&crumb=srch&qu=sql+server&gpid=c419977d-7963-4c38-8caf-95d3f779bed1

Example (make sure you pick the one that applies to you):

Full Version
Microsoft? SQL Server Enterprise Edition 2005 x64 English CD/DVD 25 Client
Item: 810-05188

Let me know if this is what you're looking for.

Thanks,
Sam

|||

Thank you Sam for the confirmation and assistance. That is what I was looking for.

...cordell...

64 Bit OLE vs. 32 Bit OLE

I have a SSIS package that works on Windows Server 2003 32 Bit with SQL Server 2005 32 Bit when I move it to a Windows Server 2003 64 Bit (AMD) with SQL Server 2005 64 Bit it fails with error 80040154 on the connection to an Access 2000 database. The solution maybe Jet 4.0 SP8 however I can not find SP8 for Windows Server 2003 64 Bit AMD (I can find Jet 4.0 SP8 for Windows Server 2003 32 Bit, Windows Server 2003 64 Bit Itanium however).

Sorry, but there is no Jet support for 64 bit so you would have to run this package as 32 bit only.

HTH,

Matt

|||I understand that Access is 32 Bit and the system I am replacing is running on this server using 32 Access (2000), the is also SP8 for Itanium 64 Bit so are you saying that the only 64 Bit OLE connection to an Access database that is supported is the Itanium 64 Bit system?|||

It is my understanding that there is no jet support for 64 bits. However, since this is an SSIS forum there could be new releases of Jet that are addressing this. To find out for sure you should ask on that forum as they would know better than we do.

Matt

|||I posted it here because all other access to these databases work. In fact SSIS Import Wizard will build a project for this, testing the connection works, selecting the desired table works, it all works until I run it. NOTE: If I preview the connection the preview works however it will general a "system out of memory"......|||

The problem is that the wizard uses different access mechanisms to get the information than the actual package. The package uses OLEDB to access jet and that (to the best of my knowledge) does not support 64 bit unless it has changed recently. If it has then you should ask on the jet forum what that specific error code means coming from their OLEDB provider because that is usually the error for class not registered and that has always been the error we get due to non 64 bit support for jet (as the class isn't registered in the 64 bit registry since it doesn't support 64 bit).

Thanks,

Matt

|||Ok, where do I find the jet forum?|||Just to make sure you know this - you can run the package as 32-bit and use 32-bit OLEDB providers on 64-bit system. You need to use 32-bit dtexec.exe from c:\Program Files (x86)\Microsoft Sql Server\...|||Thanks Michael! Based on that I found that there is a property in Visual Studio for a project "Run64BitRuntime" which is set to true by default, I set it to false and the OLEDB connection works!