permissions due to a service pack:

http://support.microsoft.com/kb/328151

You need to have admin rights, and this switch must be called in order to restore debug rights:

Exec sp_sdidebug 'legacy_on'

HTH; i ran into the...

also search for the Split() function in the scripts...there are several, and some return a table with multiple columns (ELEMENT,ELEMENTID), some just return a single column, etc. the split a...

could it be a permissions issue? you might have SELECT permission in the master database, but NOT dbowner (so that you can CREATE VIEW) in the other database? what user...

to use the in function on a string, you'll need to grab one of the many SPLIT functions that are in the script contributions here.

otherwise, you really would want...

here's an example I keep around for casting from nvarchar to varbinary and then back to nvarchar:

the key is to use nvarchars... i beleive this fails if you try to...

I saved this snippet for SQL2000, so i would assume it would still be valid in 2005; hope this helps:

USE master

go

EXEC sp_grantlogin 'BUILTIN\Administrators'

go

EXEC sp_defaultdb 'BUILTIN\Administrators', 'master'

go

EXEC sp_defaultlanguage 'BUILTIN\Administrators', 'us_english'

go

EXEC sp_addsrvrolemember...

here's one of many citations on it from microsoft: i just searched for sql 2005 server multi core processors and grabbed the first link

http://www.microsoft.com/technet/prodtechnol/sql/2005/msde2sqlexpress.mspx

so to be clear, if you...

it's physical processors that are counted, not cores...so you could have a 4 processor all with quad cores, as i remember it, and it would work with no problem

valuable article; whenever I found a situation similar to this, I always blamed out of date statistics, and updated statistics and recompiled procedures; nice detective work, I have a better...

Tony may be on to something....a typical problem where something works fine, and then slows down over time often points to out of date statistics on the database; this can...

i think what you are seening is whenever anyone is given the role db_owner(), their user_name is considered to be dbo for the queries performed.... since everyone else comes in...

i fat fingered the link and added a backslash..sorry.

I edited the link and it does take me to the right spot now.

a better explanation of index hints than BOL supplies can be found here:

http://www.sqlservercentral.com/columnists/rmarda/performanceaddinghints_printversion.asp

it's bad to second guess SQL Server's abilities as far as deciding which index to use, but...

you didn't really describe what the problem was...whether it was slow running, received a real error, or just bad performance.....so here's my guesstimate:

There's no problem creating a really big temp...

Glad you worked it out , Dave;  keep reading SSC; lots of good stuff here.