OK, wait. Those are contradictory settings... just set the No Padding to 1.

Try setting the @query_result_width parameter to something like 511 or greater.

Also, definitely set @query_result_no_padding = 1

My suspicion would be that the lines are very long and that they are getting wrapped when they are put in the attachment.

This is a duplicate posting. Please do not cross-post. Replies should be directed to http://www.sqlservercentral.com/Forums/Topic589877-149-1.aspx

It should be in Management Studio. what edition are you running?

In my experience this is a synchronicity problem.

The queue size that you see is not supportable by the CPU% value, therefore one of them must be inaccurate. ...

AnzioBake (10/22/2008)

---

My solution is a bit long but executes in under three (3) minutes.

Here is s sample of the longer series and the results set. If Correct I will...

Powershell is definitely the way to do this in SQL Server 2008.

For reasons that have always mystified me, the SQL scripter has never been available from within SQL itself.

At my blog (in my signature, below) you will find my slide set and code examples of traps to avoid when setting up service Broker.

There should be an entry call "Database Engine Tuning Advisor" under the "Tools" menu?

The "State:" values in the error codes are usually only meaningful to the developers of the code that is issuing the error message. They may be usable for bug...

Here you go, this should cover it! http://msdn.microsoft.com/en-us/library/ms130214.aspx

😀

Yes, two inserts in one transaction is faster than chaining inserts through triggers.

I assume that you are using the system performance object in PerfMon, correct? What collection interval are you using?

Could you please post the table definitions, including the Keys and Indexes? Thanks.