statsics look real bad in two of the queries (200K+ rows estimated, actual = 0

and pretty bad for the rest;

running this, with no other changes, will at least help a...

also, my rule of thumb is that any @TableVariable with more than a few hundred rows should be a temp table instead, to allow the system to automatically do things...

if you don't have a customized trace, CDC, SQL Audit, or some other set of tracking in place prior to the query being executed, there's no way to find...

it's not stored anywhere , i think; I believe you'll have to find a year old backup and compare that to todays backup.

since the proc would create the same tables all the time, it seems to me a stored proc which simply restores a backup as a new database name might be...

when you read the same report in gmail, if you "View Source" for the rendered report, can you confirm that it has now been manipulated/changed from what you actually created...

i thought it was clear: i read it as howard saying there is no need to mark an calculated column as persisted in order to index it...it's not a requirement.

simple...

you want to use the system view sys.synonyms, instead, which has everything you need:

select * from sys.synonyms

--rebuilding the command:

select

'CREATE SYNONYM '

+ quotename(SCHEMA_NAME(schema_id))

+'.'

...

it's certainly possible, but I'm not sure if you can integrate it into Reporting Services:

check out this great article here on SQL Server Central, which has the coding and explanation...

i am wondering if you could put an extended event for CREATE_TABLE on the tempdb?

I'll grab one of my sample extended events and try it, but it's just an idea...

It's the principal of...

how are you determining that it is "full"?

my model database is 3.5 Megabytes in size, with three meg for data, and one meg for the log. that's right...one meg.

we just...

SELECT SPACE(81)

or

SELECT CONVERT(CHAR(81),'')

if you are using a column, and you need to guarantee it's 81 spaces, it's similar:

SELECT CONVERT(CHAR(81),YourColumnName)

will both give you strings you are looking for...

THE LEN() property...

nope; if the procedure exists in a different database, then the login needs a matching user mapped to it in each of those databases;

that user in the "procedure" database would...

i have this saved, whcih shows all tables/the filegroup they belong to:

SELECT

objz.[name],

objz.[type],

idxz.[name],

idxz.[index_id],

...