make an investment and purchase a developer edition of SQL and just play around with SSRS.

use this site, the stairways and your fave search engine to find more on ssrs.

carthik has provided you with a solution, just change it to suit your needs

Then just select that 1 column instead of using * then add in either a distinct or a group by clause with a subquery to filter out 102.

Good luck then, unless you have something constantly poling the system tables capturing SPIDs and users who have access to issue ALTER DATABASE then your not going to find out...

Ehat do you want to see, just EncounterKey or every column in the table where there is no encounterkey which has a type key of 2

So Just 1 column with...

Use a where clause, http://msdn.microsoft.com/en-US/library/ms188047%28v=sql.105%29

Can you post the full DDL and sample data.

The table references other tables in foreign key constrains but you have not provided them.

Also the query references a view which you...

Hi, Welcome to SSC.

Please follow the second link in my signature on posting code so that we can help you out further.

query the default trace (you might get lucky), or create a custom DDL trigger to capture the information you want.

BIDS is no more in 2012.

SQL2012 has changed BIDS to SSDT (SQL Server Data Tools)

Old style joins will not function in 2012 as already said there is no level 80 any more in 2012.

To upgrade 2000 to 2012, first upgrade to 2005, sort out...

Are you familiar with the WHERE clause?

I would start by looking this up and then posting the query you have written and then if still stuck providing the expected outcome...

One thing I would do to test that nothing is going dodgy anywhere else is

Create a credential for your account, use that credential in a proxy under the CmdExec folder,...

Did you save them to the file system or to MSDB?

If MSDB, then the powershell script attached will loop through your MSDB and copy out the dtsx packages to a...

Number options,

1 - Move 500GB worth of data from the 2.5TB file to the 1TB, then shrink the 2.5B file down to 2TB, so you end up with a 2TB...