External Stored Procedure in SQL Server 2005(x64)

I have generated a DLL file in VC++ 2005 by a 'C' file. It works fine when I put in a 32bits machine(32bits Windows Server 2003 + 32 bits SQL Server 2005).

However, when I build it into 64 bits, it doesn't work in a 64 bits machine. I have checked by Dependenct Walker, the DLL generated is linked with KERNEL32.DLL / OPENDS60.DLL / MSVCR80D.DLL, all of these DLL files are on the 64 bits machines and linked correctly.

I used the command

sp_addextendedproc 'abc', 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\abc.dll'

to create a ext. stored procedure. When I run it, the error message shows that

Could not load the DLL C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\abc.dll, or one of the DLLs it references. Reason: 126(error not found).

I would like to ask what is cause of the problem? Do I need to use CLR instead?

Thank you very much!!~

BTW, it is because of your thread I posted the "32Bit Vs 64Bit" SQLCLR platform differences thread. If there are any definite differences this would be a great addition to my upcoming book. Have you experienced any other problems on 64bit platform for sqlclr?

thanks,

derek

external image not rendering when generated from aspx page

I'm having problems displaying images generated by aspx pages from a report. It works fine if I point the external value to a static image on the web. I can paste the url to the page into IE and it generates the image with no issues. What am I doing wrong? I used a textbox to verify that the correct url is being generated (= Parameters!MYPROJECT_URL.Value & Parameters!MYPROJECT_NO.Value).

Are there any issues with generating external images with reporting services?

I have installed SP1 for MS 2005...shouldn't I see some sort of visual confirmation in Management studio when I click the Help Menu->about? saying the version is MS SQL Server 2005? how do I verify that the upgrade was successful?

You can check if the upgrade is successful from the error logs, they contain the build number on the top.

|||Check if ASPX pase generate the image have anonymouse accesssql

Exporting to multiple sheets in Excel has limitations ?

guys, I am exporting a report in excel that generates in different
sheets.
It seems that only 3 tab or sheets can be generated.
If the report exceeds 3 sheets all the rest of the sheets combined in
the last sheet.
Can anyone confirm this? Does it have any work around or I am just
doing something wrong?
thanks in advanceHi, I am doing some testing on sending data to Excel myself. I just tested
this and was able to make 5 sheets when I made page brakes between rectagles
in the report. Have you used the device setting RemoveSpace when rendering
to Excel ?
"jhun_garma@.hotmail.com" wrote:
> guys, I am exporting a report in excel that generates in different
> sheets.
> It seems that only 3 tab or sheets can be generated.
> If the report exceeds 3 sheets all the rest of the sheets combined in
> the last sheet.
> Can anyone confirm this? Does it have any work around or I am just
> doing something wrong?
>
> thanks in advance
>

Exporting to Excel

We've noticed that reports exported to excel are much larger than they need to be. Example, report generated and exported (and saved in Excel) shows size of 14,111 KB. However, if same file is saved (using SaveAs in Excel) file is only 4,762KB. Any idea as to why there would be such a size difference? Does RS pass some overhead when exporting to Excel? We are hoping to eliminate any overhead since the time cost during export is rising.

(there are no images being passed, just ~33,000 rows of data)

Thanks.

What method are you using to create the excel files?

|||

We have an ASP front-end that handles some security (report access, restricting what data a user can pass in via parameters) and makes the actual call to the report server for the given report. For most reports, the report parameter is passed to force the report to be exported to Excel (instead of rendering in IE).

So, I run the report, Excel launches and displays the data, and I simply do File/SaveAs... (and rename the file)

Here are some tests I ran against other reports that auto-export to Excel:

ReportA

Test1

Original Spreadsheet: 852k

SaveAs with no changes: 390k

Test2

Original Spreadsheet: 99k

SaveAs with no changes: 52k

Test3

Original Spreadsheet: 365k

SaveAs with no changes: 169k

ReportB

Test1

Original Spreadsheet: 245k

SaveAs with no changes: 104k

Test2

Original Spreadsheet: 365k

SaveAs with no changes: 169k

ReportC

Test1

Original Spreadsheet: 35k

SaveAs with no changes: 34k

Other tests revealed similar results

ReportD

Test1

Original Spreadsheet: 53k

SaveAs with no changes: 49k

Other tests revealed similar results

ReportE

Test1

Original Spreadsheet: 432k

SaveAs with no changes: 293k

Test2

Original Spreadsheet: 14k

SaveAs with no changes: 17k

Test3

Original Spreadsheet: 15k

SaveAs with no changes: 18k

Test4

Original Spreadsheet: 42k

SaveAs with no changes: 38k

Test5

Original Spreadsheet: 51k

SaveAs with no changes: 44k

I find it interesting that the larger the report output size, the greater the difference in sizes when resaved. Also, for very small file sizes, resaved size is actually bigger. Any ideas?

|||

I did some additional research - looks like this is just how Report Server interacts with MS Excel. Report Server cannot take advantage of Excel's file compression process(es) when it exports. Work arounds include exporting first to CSV and then opening the file in Excel OR scheduling the report so that the users don't have to wait. (Another suggestion is to wait for SQL Server 2008 and hope the issue is addressed there.)

I will mark this issue as resolved, but if you have any additional information, please post it here. Thanks.