A doubt about this: "Could not find stored Procedure"

Hi Everybody!

I have a problem in my SQL Server 2000 SP1 Database Called "Embossamento". When I run the following comand in the Query Analyzer, I have this error message :

command: exec dbcc_all_dbreindex
message: Could not find stored procedure 'dbcc_all_dbreindex'.

Otherwise, in the same server, but in another Database called "Autorizacao" I execute this dbcc_all_dbreindex with no problems.
Does anybody know why this happens?
I will be waiting for some reply, ok?
Thanks,This must be a custom stored procedure that uses the dbcc dbreindex command - check out the database, Autorizacao, and look for your stored procedures under that database.|||Ok! Thanks!
It worked! I just realized that my database did not have the procedure dbcc_all_dbreindex.
Now it's ok...

64-Bit SQL Server 2005 (Enterprise), SQL Agent Notifications and Database Mail

We have database mail configured on our 64-Bit SQL Server Enterprise 2005 (SP1) and are able to send test messages from the context menu that appears when selecting database mail component.

However for some reason when a SQL Agent Job fails, no emails are sent to the 'operator' that has been defined for the job. I have confirmed that we have the operators correctly configured. We also have a small SQL Agent Job that just sends a test email via the sp_send_dbmail command and that works properly. However if I deliberately create a malformed parameter in the sp_send_dbmail command to 'break' it...no notification of a job failure message is sent.

I have verified that the service_broker component is enabled...and the status of database mail in the MSDB database is 'started.'

We have setup several other 32-bit SQL Server 2005 systems using database mail...and they all work flawlessly.

After reviewing existing message posts...I am unsure if there is a problem with database mail on a 64-bit SQL Server box. Some say 'yes' other say 'no'.

There are several MSDN notes about the problem...however these appeared prior to the release of SP1 of SQL Server 2005.

Thank you for your assistance.

...cordell...

SQL Database mail which relies on using your SMTP server instead of a mail client to send out email, so check whether that service is started as a first point of check.|||

yes..our Exchange server works properly and is running. I have several other 32-bit SQL Server 2005 system that are able to send email (using SQL Database Mail) without issue.

Maybe I have misunderstood your reply and missing something obvious...since this is a pretty basic question.

Thank you.

...cordell...

|||

As I read KB article 908360 it says that SQL Server 2005 (x64) is not integrated with Database Mail or with SQL Mail in Microsoft SQL Server 2005 64-bit editions.

But then there is a note that says, "Note In SQL Server 2005 Service Pack 1 (SP1), you can use SQL Server Agent to interact with Database Mail as the mailing system on 64-bit operating systems."

We have SP1 installed on our x64 SQL Servers but Database Mail still doesn't work with SQL Agent. The history for any job that fails says, " NOTE: Failed to notify 'DB_Engineering' via email."

QUESTIONS:

Is it correct to assume that there is one and only one SP1 package for SQL Server 2005? Our assumption is that the currently available SP1 is for both 32 bit and 64 bit SQL Server 2005 installations.

Does a separate 64 bit SP1 exist somewhere?

Are there special instructions required for setting up database Mail on SQL Server 2005 (x64) SP1 without using Outlook Express? If so, we haven't found them yet.

Does this article really mean that Outlook Express is currently the only workaround for using Email Notifications on a 64 bit SQL Server? (We do not activate Outlook Express -- or even SMTP -- on Production SQL Servers. SMTP exists on its own machine.)

Please advise,

Thanks,

Ernie

64bit Primary with 32bit Secondary SQL 2005

Currently I have a standby server which is kept in synch from the primary via
log-shipping. Both are running SQL 2005 Standard sp1, on Windows 2003 Server
w/sp1. My primary is 64bit capable, but my secondary is not. Are there any
concerns running the primary as x64bit with log-shipping to a 32-bit machine
(other than performance and memory differences). Occasionaly I have to
switch production apps between the two servers. The log-shipping is a simple
tlog backup/restore, not Microsoft's log-shipping.That should not be a problem.
--
Andrew J. Kelly SQL MVP
"Brandon" <Brandon@.discussions.microsoft.com> wrote in message
news:CD1113A6-4937-49E4-8963-B2B8FC392456@.microsoft.com...
> Currently I have a standby server which is kept in synch from the primary
> via
> log-shipping. Both are running SQL 2005 Standard sp1, on Windows 2003
> Server
> w/sp1. My primary is 64bit capable, but my secondary is not. Are there
> any
> concerns running the primary as x64bit with log-shipping to a 32-bit
> machine
> (other than performance and memory differences). Occasionaly I have to
> switch production apps between the two servers. The log-shipping is a
> simple
> tlog backup/restore, not Microsoft's log-shipping.
>

64bit Primary with 32bit Secondary SQL 2005

Currently I have a standby server which is kept in synch from the primary vi
a
log-shipping. Both are running SQL 2005 Standard sp1, on Windows 2003 Serve
r
w/sp1. My primary is 64bit capable, but my secondary is not. Are there any
concerns running the primary as x64bit with log-shipping to a 32-bit machine
(other than performance and memory differences). Occasionaly I have to
switch production apps between the two servers. The log-shipping is a simpl
e
tlog backup/restore, not Microsoft's log-shipping.That should not be a problem.
Andrew J. Kelly SQL MVP
"Brandon" <Brandon@.discussions.microsoft.com> wrote in message
news:CD1113A6-4937-49E4-8963-B2B8FC392456@.microsoft.com...
> Currently I have a standby server which is kept in synch from the primary
> via
> log-shipping. Both are running SQL 2005 Standard sp1, on Windows 2003
> Server
> w/sp1. My primary is 64bit capable, but my secondary is not. Are there
> any
> concerns running the primary as x64bit with log-shipping to a 32-bit
> machine
> (other than performance and memory differences). Occasionaly I have to
> switch production apps between the two servers. The log-shipping is a
> simple
> tlog backup/restore, not Microsoft's log-shipping.
>

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 60 gb db with RAID 10 4 VOLUME

I am working with SQL 2005 64 bit sp1 , i am facing problem continues in
error log file mentioned below, can you please help me
SQL Server has encountered 1 occurrence(s) of I/O requests taking longer
than 15 seconds to complete on file
[E:\ITS247DBFiles\ItSupport247DB1.mdf:MSSQL_DBCC11 ] in database
[ItSupport247DB] (11). The OS file handle is 0x0000000000007F5C. The offset
of the latest long I/O is: 0x0000032dac0000
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
"Jay" <Jay@.discussions.microsoft.com> wrote in message
news:926CD051-B1BF-481A-AA4D-BA06AB7DBA72@.microsoft.com...
>I am working with SQL 2005 64 bit sp1 , i am facing problem continues in
> error log file mentioned below, can you please help me
> SQL Server has encountered 1 occurrence(s) of I/O requests taking longer
> than 15 seconds to complete on file
> [E:\ITS247DBFiles\ItSupport247DB1.mdf:MSSQL_DBCC11 ] in database
> [ItSupport247DB] (11). The OS file handle is 0x0000000000007F5C. The
> offset
> of the latest long I/O is: 0x0000032dac0000
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
I'd look at the disk array first, make sure you have the latest drivers,
that there's no hardware issues, etc.
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com
|||Generally indicates a HW problem.
Had this recently, first line of defense is to power-cycle the server,
second is to refresh RAID controller microcode and power-cycle. Doing
this seems to have "fixed" two of our servers where we were getting
this message - except at much, much higher volumes!
J.
On Tue, 27 Feb 2007 19:59:05 -0800, Jay
<Jay@.discussions.microsoft.com> wrote:

>I am working with SQL 2005 64 bit sp1 , i am facing problem continues in
>error log file mentioned below, can you please help me
>SQL Server has encountered 1 occurrence(s) of I/O requests taking longer
>than 15 seconds to complete on file
>[E:\ITS247DBFiles\ItSupport247DB1.mdf:MSSQL_DBCC1 1] in database
>[ItSupport247DB] (11). The OS file handle is 0x0000000000007F5C. The offset
>of the latest long I/O is: 0x0000032dac0000
>For more information, see Help and Support Center at
>http://go.microsoft.com/fwlink/events.asp.
|||very very Thanks to Greg and JXStern,
can you provide some links related this issues, so that i can show to my
boss.it will be more helpfull to me.
waiting for you alls reply.
regards
Jay
"JXStern" wrote:

> Generally indicates a HW problem.
> Had this recently, first line of defense is to power-cycle the server,
> second is to refresh RAID controller microcode and power-cycle. Doing
> this seems to have "fixed" two of our servers where we were getting
> this message - except at much, much higher volumes!
> J.
>
> On Tue, 27 Feb 2007 19:59:05 -0800, Jay
> <Jay@.discussions.microsoft.com> wrote:
>
>
|||Me, I don't have anything, just called the sysadmin guys (emailed,
actually), and they told me this story, then did it, and it worked!
Twice!
These are only fairly current HP servers, so the problem is probably
very, very, very common.
J.
On Wed, 28 Feb 2007 06:55:52 -0800, Jay
<Jay@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>very very Thanks to Greg and JXStern,
>can you provide some links related this issues, so that i can show to my
>boss.it will be more helpfull to me.
>waiting for you alls reply.
>regards
>Jay
>
>"JXStern" wrote:
|||thanks JXStern,
i am trying for a link to this issues, so that i can tell to my BOSS
thanks thanks very much
jay
"JXStern" wrote:

> Me, I don't have anything, just called the sysadmin guys (emailed,
> actually), and they told me this story, then did it, and it worked!
> Twice!
> These are only fairly current HP servers, so the problem is probably
> very, very, very common.
> J.
>
> On Wed, 28 Feb 2007 06:55:52 -0800, Jay
> <Jay@.discussions.microsoft.com> wrote:
>
>

64 bit 60 gb db with RAID 10 4 VOLUME

I am working with SQL 2005 64 bit sp1 , i am facing problem continues in
error log file mentioned below, can you please help me
SQL Server has encountered 1 occurrence(s) of I/O requests taking longer
than 15 seconds to complete on file
[E:\ITS247DBFiles\ItSupport247DB1.mdf:MSSQL_DBCC11] in database
[ItSupport247DB] (11). The OS file handle is 0x0000000000007F5C. The o
ffset
of the latest long I/O is: 0x0000032dac0000
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp."Jay" <Jay@.discussions.microsoft.com> wrote in message
news:926CD051-B1BF-481A-AA4D-BA06AB7DBA72@.microsoft.com...
>I am working with SQL 2005 64 bit sp1 , i am facing problem continues in
> error log file mentioned below, can you please help me
> SQL Server has encountered 1 occurrence(s) of I/O requests taking longer
> than 15 seconds to complete on file
> [E:\ITS247DBFiles\ItSupport247DB1.mdf:MSSQL_DBCC11] in database
> [ItSupport247DB] (11). The OS file handle is 0x0000000000007F5C. The
> offset
> of the latest long I/O is: 0x0000032dac0000
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
I'd look at the disk array first, make sure you have the latest drivers,
that there's no hardware issues, etc.
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com|||Generally indicates a HW problem.
Had this recently, first line of defense is to power-cycle the server,
second is to refresh RAID controller microcode and power-cycle. Doing
this seems to have "fixed" two of our servers where we were getting
this message - except at much, much higher volumes!
J.
On Tue, 27 Feb 2007 19:59:05 -0800, Jay
<Jay@.discussions.microsoft.com> wrote:

>I am working with SQL 2005 64 bit sp1 , i am facing problem continues in
>error log file mentioned below, can you please help me
>SQL Server has encountered 1 occurrence(s) of I/O requests taking longer
>than 15 seconds to complete on file
>[E:\ITS247DBFiles\ItSupport247DB1.mdf:MSSQL_DBCC11] in database
>[ItSupport247DB] (11). The OS file handle is 0x0000000000007F5C. The
offset
>of the latest long I/O is: 0x0000032dac0000
>For more information, see Help and Support Center at
>http://go.microsoft.com/fwlink/events.asp.|||very very Thanks to Greg and JXStern,
can you provide some links related this issues, so that i can show to my
boss.it will be more helpfull to me.
waiting for you alls reply.
regards
Jay
"JXStern" wrote:

> Generally indicates a HW problem.
> Had this recently, first line of defense is to power-cycle the server,
> second is to refresh RAID controller microcode and power-cycle. Doing
> this seems to have "fixed" two of our servers where we were getting
> this message - except at much, much higher volumes!
> J.
>
> On Tue, 27 Feb 2007 19:59:05 -0800, Jay
> <Jay@.discussions.microsoft.com> wrote:
>
>|||Me, I don't have anything, just called the sysadmin guys (emailed,
actually), and they told me this story, then did it, and it worked!
Twice!
These are only fairly current HP servers, so the problem is probably
very, very, very common.
J.
On Wed, 28 Feb 2007 06:55:52 -0800, Jay
<Jay@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>very very Thanks to Greg and JXStern,
>can you provide some links related this issues, so that i can show to my
>boss.it will be more helpfull to me.
>waiting for you alls reply.
>regards
>Jay
>
>"JXStern" wrote:
>|||thanks JXStern,
i am trying for a link to this issues, so that i can tell to my BOSS
thanks thanks very much
jay
"JXStern" wrote:

> Me, I don't have anything, just called the sysadmin guys (emailed,
> actually), and they told me this story, then did it, and it worked!
> Twice!
> These are only fairly current HP servers, so the problem is probably
> very, very, very common.
> J.
>
> On Wed, 28 Feb 2007 06:55:52 -0800, Jay
> <Jay@.discussions.microsoft.com> wrote:
>
>

64 bit 60 gb db with RAID 10 4 VOLUME

I am working with SQL 2005 64 bit sp1 , i am facing problem continues in
error log file mentioned below, can you please help me
SQL Server has encountered 1 occurrence(s) of I/O requests taking longer
than 15 seconds to complete on file
[E:\ITS247DBFiles\ItSupport247DB1.mdf:MSSQL_DBCC11] in database
[ItSupport247DB] (11). The OS file handle is 0x0000000000007F5C. The offset
of the latest long I/O is: 0x0000032dac0000
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp."Jay" <Jay@.discussions.microsoft.com> wrote in message
news:926CD051-B1BF-481A-AA4D-BA06AB7DBA72@.microsoft.com...
>I am working with SQL 2005 64 bit sp1 , i am facing problem continues in
> error log file mentioned below, can you please help me
> SQL Server has encountered 1 occurrence(s) of I/O requests taking longer
> than 15 seconds to complete on file
> [E:\ITS247DBFiles\ItSupport247DB1.mdf:MSSQL_DBCC11] in database
> [ItSupport247DB] (11). The OS file handle is 0x0000000000007F5C. The
> offset
> of the latest long I/O is: 0x0000032dac0000
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
I'd look at the disk array first, make sure you have the latest drivers,
that there's no hardware issues, etc.
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com|||Generally indicates a HW problem.
Had this recently, first line of defense is to power-cycle the server,
second is to refresh RAID controller microcode and power-cycle. Doing
this seems to have "fixed" two of our servers where we were getting
this message - except at much, much higher volumes!
J.
On Tue, 27 Feb 2007 19:59:05 -0800, Jay
<Jay@.discussions.microsoft.com> wrote:
>I am working with SQL 2005 64 bit sp1 , i am facing problem continues in
>error log file mentioned below, can you please help me
>SQL Server has encountered 1 occurrence(s) of I/O requests taking longer
>than 15 seconds to complete on file
>[E:\ITS247DBFiles\ItSupport247DB1.mdf:MSSQL_DBCC11] in database
>[ItSupport247DB] (11). The OS file handle is 0x0000000000007F5C. The offset
>of the latest long I/O is: 0x0000032dac0000
>For more information, see Help and Support Center at
>http://go.microsoft.com/fwlink/events.asp.|||very very Thanks to Greg and JXStern,
can you provide some links related this issues, so that i can show to my
boss.it will be more helpfull to me.
waiting for you alls reply.
regards
Jay
"JXStern" wrote:
> Generally indicates a HW problem.
> Had this recently, first line of defense is to power-cycle the server,
> second is to refresh RAID controller microcode and power-cycle. Doing
> this seems to have "fixed" two of our servers where we were getting
> this message - except at much, much higher volumes!
> J.
>
> On Tue, 27 Feb 2007 19:59:05 -0800, Jay
> <Jay@.discussions.microsoft.com> wrote:
> >I am working with SQL 2005 64 bit sp1 , i am facing problem continues in
> >error log file mentioned below, can you please help me
> >
> >SQL Server has encountered 1 occurrence(s) of I/O requests taking longer
> >than 15 seconds to complete on file
> >[E:\ITS247DBFiles\ItSupport247DB1.mdf:MSSQL_DBCC11] in database
> >[ItSupport247DB] (11). The OS file handle is 0x0000000000007F5C. The offset
> >of the latest long I/O is: 0x0000032dac0000
> >
> >For more information, see Help and Support Center at
> >http://go.microsoft.com/fwlink/events.asp.
>|||Me, I don't have anything, just called the sysadmin guys (emailed,
actually), and they told me this story, then did it, and it worked!
Twice!
These are only fairly current HP servers, so the problem is probably
very, very, very common.
J.
On Wed, 28 Feb 2007 06:55:52 -0800, Jay
<Jay@.discussions.microsoft.com> wrote:
>very very Thanks to Greg and JXStern,
>can you provide some links related this issues, so that i can show to my
>boss.it will be more helpfull to me.
>waiting for you alls reply.
>regards
>Jay
>
>"JXStern" wrote:
>> Generally indicates a HW problem.
>> Had this recently, first line of defense is to power-cycle the server,
>> second is to refresh RAID controller microcode and power-cycle. Doing
>> this seems to have "fixed" two of our servers where we were getting
>> this message - except at much, much higher volumes!
>> J.
>>
>> On Tue, 27 Feb 2007 19:59:05 -0800, Jay
>> <Jay@.discussions.microsoft.com> wrote:
>> >I am working with SQL 2005 64 bit sp1 , i am facing problem continues in
>> >error log file mentioned below, can you please help me
>> >
>> >SQL Server has encountered 1 occurrence(s) of I/O requests taking longer
>> >than 15 seconds to complete on file
>> >[E:\ITS247DBFiles\ItSupport247DB1.mdf:MSSQL_DBCC11] in database
>> >[ItSupport247DB] (11). The OS file handle is 0x0000000000007F5C. The offset
>> >of the latest long I/O is: 0x0000032dac0000
>> >
>> >For more information, see Help and Support Center at
>> >http://go.microsoft.com/fwlink/events.asp.
>>|||thanks JXStern,
i am trying for a link to this issues, so that i can tell to my BOSS
thanks thanks very much
jay
"JXStern" wrote:
> Me, I don't have anything, just called the sysadmin guys (emailed,
> actually), and they told me this story, then did it, and it worked!
> Twice!
> These are only fairly current HP servers, so the problem is probably
> very, very, very common.
> J.
>
> On Wed, 28 Feb 2007 06:55:52 -0800, Jay
> <Jay@.discussions.microsoft.com> wrote:
> >very very Thanks to Greg and JXStern,
> >
> >can you provide some links related this issues, so that i can show to my
> >boss.it will be more helpfull to me.
> >
> >waiting for you alls reply.
> >
> >regards
> >
> >Jay
> >
> >
> >
> >"JXStern" wrote:
> >
> >> Generally indicates a HW problem.
> >>
> >> Had this recently, first line of defense is to power-cycle the server,
> >> second is to refresh RAID controller microcode and power-cycle. Doing
> >> this seems to have "fixed" two of our servers where we were getting
> >> this message - except at much, much higher volumes!
> >>
> >> J.
> >>
> >>
> >> On Tue, 27 Feb 2007 19:59:05 -0800, Jay
> >> <Jay@.discussions.microsoft.com> wrote:
> >>
> >> >I am working with SQL 2005 64 bit sp1 , i am facing problem continues in
> >> >error log file mentioned below, can you please help me
> >> >
> >> >SQL Server has encountered 1 occurrence(s) of I/O requests taking longer
> >> >than 15 seconds to complete on file
> >> >[E:\ITS247DBFiles\ItSupport247DB1.mdf:MSSQL_DBCC11] in database
> >> >[ItSupport247DB] (11). The OS file handle is 0x0000000000007F5C. The offset
> >> >of the latest long I/O is: 0x0000032dac0000
> >> >
> >> >For more information, see Help and Support Center at
> >> >http://go.microsoft.com/fwlink/events.asp.
> >>
> >>
>

50% BLOAT in the Excel files created by Reporting Services.

First, I have SP1.
Microsoft SQL Server Reporting Services Version 8.00.878.00
I created a snapshot - to ensure the db query is not the cause.
I am working on the production hardware (beefy) - and I am the only
one on it.
The HTML version is quite fast off the snapshot (maybe 20 second).
The resulting table is 11k rows spread over 17 pages in HTML.
When I click export to Excel, it's a good 4-7 minutes before it
prompts me to OPEN or SAVE and then another minute or more to SAVE.
The resulting file is 7.8MB. The resulting file takes a good 3 minutes
to load in Excel.
Here's the problem.
The original spreadsheet (created by Business Objects) I am replacing
with RS is only 3.xMB and it has MORE tabs than the one I am creating!
It opens much faster - and is basically the same on the inside.
When I try SAVE AS and select Office 95 - it is still 5.5MB - the same
size I get when I SAVE AS to 2003 but with a different file name. **
This alone tells me there is 50% BLOAT in the Excel files created by
Reporting Services. **
Someone help me.
Why is it so slow?
Why is it so large?
What can I do to make this better? (and don't say SP2, ;))
Thanks in advance, JerryFirst, you can't compare the first page in HTML to the Excel output. You
could compare the MHTML output as it is also a single stream. I'm not sure
how BO's export works so you might not be comparing apples to apples if the
feature set (formatting, etc.) isn't the same. There are also style
duplication optimizations that we can't really do because of our current
flexibility. You might see what happens if you format your entire report as
a single style.
That being said, we are always looking to improve the size and speed of the
exports. If you can isolate what you think might be the root cause, we will
take a look.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jerry Nixon" <jerrynixon@.gmail.com> wrote in message
news:36f558cf.0410151234.1b184eb0@.posting.google.com...
> First, I have SP1.
> Microsoft SQL Server Reporting Services Version 8.00.878.00
> I created a snapshot - to ensure the db query is not the cause.
> I am working on the production hardware (beefy) - and I am the only
> one on it.
> The HTML version is quite fast off the snapshot (maybe 20 second).
> The resulting table is 11k rows spread over 17 pages in HTML.
> When I click export to Excel, it's a good 4-7 minutes before it
> prompts me to OPEN or SAVE and then another minute or more to SAVE.
> The resulting file is 7.8MB. The resulting file takes a good 3 minutes
> to load in Excel.
> Here's the problem.
> The original spreadsheet (created by Business Objects) I am replacing
> with RS is only 3.xMB and it has MORE tabs than the one I am creating!
> It opens much faster - and is basically the same on the inside.
> When I try SAVE AS and select Office 95 - it is still 5.5MB - the same
> size I get when I SAVE AS to 2003 but with a different file name. **
> This alone tells me there is 50% BLOAT in the Excel files created by
> Reporting Services. **
> Someone help me.
> Why is it so slow?
> Why is it so large?
> What can I do to make this better? (and don't say SP2, ;))
> Thanks in advance, Jerry|||I am comparing apples to apples. I am not comparing to HTML.
My solution, finally, was to export as CSV and use Excel's Web Query -
that saves tons of space and time as the export is WAY faster than to
Excel. Thanks for your response, I have abandoned the Excel export
function as it was too slow.
This line from Books Online sealed the dealf for me:
"Excel / Renders a report in Microsoft Excel. / This format is useful
for report data that you want to manipulate offline or in Microsoft
Excel. Avoid this format for large reports."
BR//Jerry

3753 Provider is not specified and there is no designated default provider.

i just bought a brand new server and put windows server 2003 x64 sp1 on it then put sql server 2000 sp4 on that and set up a trusted odbc connection. however, it gave me the following error:
SQLSTATE:IM002, diagnosis:[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
so i made a vbs file (adodb.connection) to see if that could connect to it and it came out with this on the err.number err.description
err.number = 3753
err.description = Provider is not specified and there is no designated default provider.
this even happened when i tried to use a dsnless connection to the old server machine so i dont know if its a problem with whatever is trying to use the connection or odbc or what. please can someone tell me what can i do to fix this problem?
i dont know if this is just a missing driver or something, odbc only has "SQL Server" in the list (C:\WINDOWS\System32\SQLSRV32.dll i think) wheras all my other machines have something like 25 or 30 drivers in the list, but "SQL Server" is the one im trying to use anyway..
edit: iis is not installed on this new server. other machines (with iis and vbs) can connect using dsnless or dsn with uid and pwd. also i think asp might have a different err.number for this problem than vbs' 3753

Due to the length of time since this issue was posted, I'm marking it as resolved. If you're still in need of help, please respond here.

Paul

3753 Provider is not specified and there is no designated default provider.

i just bought a brand new server and put windows server 2003 x64 sp1 on it then put sql server 2000 sp4 on that and set up a trusted odbc connection. however, it gave me the following error:
SQLSTATE:IM002, diagnosis:[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
so i made a vbs file (adodb.connection) to see if that could connect to it and it came out with this on the err.number err.description
err.number = 3753
err.description = Provider is not specified and there is no designated default provider.
this even happened when i tried to use a dsnless connection to the old server machine so i dont know if its a problem with whatever is trying to use the connection or odbc or what. please can someone tell me what can i do to fix this problem?
i dont know if this is just a missing driver or something, odbc only has "SQL Server" in the list (C:\WINDOWS\System32\SQLSRV32.dll i think) wheras all my other machines have something like 25 or 30 drivers in the list, but "SQL Server" is the one im trying to use anyway..
edit: iis is not installed on this new server. other machines (with iis and vbs) can connect using dsnless or dsn with uid and pwd. also i think asp might have a different err.number for this problem than vbs' 3753

Due to the length of time since this issue was posted, I'm marking it as resolved. If you're still in need of help, please respond here.

Paul