This error is indicating that there isn't enough memory for the SSIS process to handle the number of rows that are being returned. If the SSIS package is being...

I can't remember the exact syntax in SSIS but you need to do a replace using the ASCII code for tab which you can find at http://www.asciitable.com/. You can...

Check out the Scripts library here on SSC. There are several scripts there that do this. You can do a search on security and then limit it to...

What is your connection to the SAN? Are you connecting using iSCSI, or fibre channel. I've seen iSCSI saturated very easily.

I would definitely look into the index because of the number lock escalation attempts. This means that SQL Server is having to take so many row or page locks...

Duplicate post. Please post answers in this post

As far as I am aware this is expected behavior and upgrading the app server to use the latest SQL Connectivity tools should solve the problem.

Here are a some links to scripts in the SSC scripts library that should at least get you started:

http://www.sqlservercentral.com/scripts/75191/

http://www.sqlservercentral.com/scripts/64793/

http://www.sqlservercentral.com/scripts/Permissions/76450/

I have to ask. Why do you need to reduce the size of this file? If it is using 55GB and growing, eventually you will need the space...

Jason,

It's not like we all haven't been there before. Just glad you got the issue sorted out.

-Jack

Without seeing the code, it's hard to say what is really happening.

What are you doing to mitigate against the risk of SQL Injection in the dynamic SQL?

Okay. I'm not used to using the report viewer client and rdlc files. Do report executions from rdlc files get logged in the ReportServer Database? If so,...

f you are running a slipstreamed install then you are going to get whatever SP's or CU's are included in the slipstream.

Glad you figured it out. Doesn't really seem to make sense that report builder would be case-sensitive when BIDS isn't :crazy:

Sorry...