Check out the permissions section in the BOL entry for sys.columns. BOL is a great resource and can answer most of your questions.

What you can do does depend on your permissions as well. In addition to Profiler you can also do something like this immediately after running the reports:

SELECT

...

fn_trace_getinfo will give you the information, but querying sys.traces actually gives you more information in a more readable format (you don't have to know what the property numbers mean because...

How are you populating the Reporting Database? If through a daily load you could make it a read only database and then I believe the hints will be ignored.

I'm going to venture a guess it is an ANSI_PADDING issue. Try this query on th 2008 box:

SELECT

DATABASEPROPERTYEX('Personnel', 'IsAnsiPaddingEnabled ') AS DB_ANSI_PADDING,

...

The best way to handle this is to split the parameter passed in and put the values into a table or use a table-valued function and then join on the...

jcrawf02 (11/23/2009)

---

Is that all you ate? I notice no side...

Finally caught up on the food talk. Love steak, always ask for it medium in a restaurant because I usually get closer to medium rare. You can't beat...

YSLGuru (11/20/2009)

---

Jack Corbett (11/20/2009)

---

There is a role, DatabaseMailUser, in msdb that you can put users in.

I'm a fan of option 1 in your case, even though Database Mail is asynchronous,...

I have written a couple of blog posts about problems with database mail that may help. You can read them here and here.

All the above answers are correct. This is a failing in database mail in my opinion. I have a blog post about this issue here.

There is a role, DatabaseMailUser, in msdb that you can put users in.

I'm a fan of option 1 in your case, even though Database Mail is asynchronous, I just don't...

You have a couple of options:

1. Use an expression in the query editor to ignore the parameter if empty string. Something like this:

="Select columns from table" & IF(Parameters!PostCode.Value...

Sure, you need 2 foreign keys and you add them like this:

ALTER TABLE dbo.docfol

ADD

CONSTRAINT FK_docfol_document FOREIGN KEY (docid) REFERENCES dbo.document (docid),

CONSTRAINT...

What is the error you get?