The correct use for dynamic SQL is Option 1: DON'T, especially if you're a noob.

If you understand the repercussions of code that can't be optimized, and SQL injection attacks, etc,...

Sounds like mirroring will work. The mirror would be used as the report server. It would stay in standby mode, but that does not mean you cannot query...

put them in a rectangle that comes after all the other items in the report?

textbox would have as it's source

=Parameters!ParameterName.Value

You could also put a single row table there, if...

See the second example in this article:

http://access.mvps.org/access/general/gen0008.htm

then once the data is in Access, you can do whatever... (Probably export back out... and go through SSIS as planned.)

One option might be to use Access (shudder, I know) to create a linked table that only links to the data you want and then export that back to Excel...

Yes, a Matrix is essentially a crosstab (well, except you don't have to do the PIVOT in T-SQL... SSRS does the pivot part for you).

So, yes, you could choose a...

Young Jedi,

Read these:

http://www.sqlservercentral.com/articles/Security/sqlinjection/1269/

http://www.sqlservercentral.com/articles/Editorial/77168/

http://www.sqlservercentral.com/articles/sql+injection/65129/

I would consider dynamic SQL as an absolute last resort. Not a tool to be used by ex-Access programmers (I am...

Just say NO to dynamic SQL!!! That opens doors to all kinds of REALLY bad things! I should probably go find Kevin Kline's "SQL Server Low-Hanging Fruit" presentation...

The line in there that would worry me is this one:

Scalar UDFs are generally accepted as one of the worst things you can do performance-wise in T-SQL. However, they may...

you could add a calculated value to your dataset that did the calculation "row-wise" and then use that calculated value in your SUM / aggregate expression

you could add a calculated value to your dataset that did the calculation "row-wise" and then use that calculated value in your SUM / aggregate expression

FWIW, I started with Brian Larson's book on SSRS 2008. It was okay. He walks you through setup, which helps. Also, his instructions are usually really easy to...

I think you can use it. The best way to find out is to use a "sandbox" database (or something you can mess up and it won't matter), and...

Since the SQL to return the records you want is really simple, I would just join this...

SELECT r.jobnumber

re.code

FROM repheader r

INNER JOIN repairtype re ON re.code = r.code

to your other query....

use a cartesian product. (two tables in the query, no join). One has People, one has Events. No join means the tables get multiplied. Filter as...