A Challenge: Check Layout

I have a questions for those familiar with the tools and work-arounds of SSRS 2005. My task is to produce a report that has page(s) consisting of three parts that are equal divided vertically amoung the 11 inches of the report height. The first section on the top section has a a check on it. The second and third sections have two seperate yet identical tables.

The trick for this is that each table (in sections part two and three) must not leak into each other's section. Essentially each section has X amount of rows that are shown on each page with the next X amount of rows on seperate pages after that. The problem, as you can most likely guess, is that you cannot force a table to continue only into it's appriopriate section on the next page. I've tried many, many combinations of tricks to try and trick SSRS into working. I know that SSRS most likely doesn't support this directly, but I'm looking for a genius or just anybody who might have a work-around. I'll update this as I find out more. Please feel free to ask for more of an explaination if needed. Thanks!

Mguvu,

I can think of only one way to accomplish this. You'll need to limit the number of row returned by the data set by using a Top (X) clause in the select statement to return only the first few rows. To display the remaining row on a following page will require a filter of some sort on another data set. Not knowing your data, I can't say for sure how to do it, but I'm assuming you are sorting the data set by date.You might try creating the data set with enumerated rows then filtering out the rows displayed in the first table.

64bit problem?

I run SQL Server 2005 on a Windows 2003 64-bit server. I have created a package where I run an execute t-sql statement task. In the t-sql I have the following:

select * from
OpenDataSource('Microsoft.Jet.OLEDB.4.0','Data Source="c:\test.mdb";User ID=Admin;Password=').pubs.dbo.data

and I get the following error:

The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered.

There is only 32-bit version of Jet provider.

You access it on 64-bit machine, if you run SSIS packages in 32-bit mode (using 32-bit dtexec from Program Files (x86) or setting appropriate option in project), and access Jet database directly (not through SQL server).|||I am a newbie with SSIS and I am not yet in the post-deployment stage. I am running the package from Visual Studio 2005.
How to choose to run it in 32 bit mode?
And how to run the Jet datbase directly and not through SQL server?

Thanks again!

|||To run package in 32-bit mode in Visual Studio, right click SSIS project and select properties. Set the property Debugging > Run64BitRuntime to false.
To access Jet database (e.g. as a source) without SQL Server:
1) create OLE DB Connection Manager, select "Native OLEDB\Microsoft Jet 4.0" provider in the top drop down box, configure path to database.
2) from Toolbox drop OLE DB Source to the data flow, configure it to use this connection manager.|||

execute the package with the dtsrun.exe found in

c:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn

regards

JG

|||DtsRun is for DTS 2000, it would not be able to run SSIS package.
To run SSIS use DTEXEC from
c:\Program Files\Microsoft SQL Server\90\Dts\Binn or
c:\Program Files (x86)\Microsoft SQL Server\90\Dts\Binn|||

precondition >> I run SQL Server 2005 on a Windows 2003 64-bit server<<

further ssis dosnt run on 2000 but on 2005.

if you on 2005 run a ssis package it will use the 32bit jet driver and your import will work fine

regards

G.

|||But opening an OLEDB source for MS Access will not allow me to use OpenDatasource from SQL, right?

Therefore there is no way to use OpenDataSource from SQL 2005 64 bit?

The idea is that I would like to run a complex stored procedure in the package, and that the stored procedure needs the data in Access as well.

4 CPU Utilization Imbalance

Got a strange thing happening, any comments are appreciated:

1) 4 CPU server
2) CPU's 0 & 2 are usually below 15% or so utilization (Perfmon, Task Manager)
3) CPU's 1 & 3 are usually nearly maxed out above 90%
4) Two SQL threads of over 80 threads in Perfmon show almost constant 90% Processor Time
5) Processor affinity in Server Properties is checked to use all four processors
6) Hyper-threading is not enabled
7) SQL Server priority is checked on HIGH
8) Dedicated SQL Server

Anybody know how to track down what those specific threads are executing? Any ideas, anybody? Thanks for the help!

SteveRefer to this link (http://www.sql-server-performance.com/dbcc_commands.asp) for useful DBCC commands and capture the events.|||Satya, thanks for the reply, and the link to the highly useful web site. I was able to trace the thread activity using Perfmon and sysprocesses; successfully killed a couple non-responsive threads and things returned to normal. I appreciate the help!

Steve|||True, keep in touch with the link provided for the tips and tricks on the performance.