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],

...

yep if you are granted execute to a proc, even if you, the caller, are denied permission to the underlying tables, the proc will execute.

is this a real problem for...

unless the procedure starts with "sp_", i believe it assumes the context of the msdb database, right?

i had to poke around to find this; it involves editing an xml file:

http://visualstudiohacks.com/options/changing-the-my-projects-folder-location-and-other-settings-in-ssms/

db042188 (1/21/2013)

---

Hi. It looks like granting a user permission to execute a proc overrides that user's insert/update/delete permissions they'd otherwise have on a table that the proc updates.

I was...

as far as I know, the binaries for SQL must be installed on the %systemdrive% (usually the C:\ drive)

that part cannot be changed, but you can easily change / move...