If my stored procedure invokes a SELECT, I'd normally just put it inside an INSERT clause, like so:

CREATE PROCEDURE myProc

AS BEGIN

SELECT [name]

...

Ask yourself why you are using the Enterprise edition version - is it for features like backup compression, TDE etc? What might break if you downgrade? Cross reference...

Is your Windows account a member of the Administrators group, and is the Administrators group a valid server login group with sysadmin permissions?

If so then log in using...

hoseam (8/31/2012)

---

I have this table

CSN NAME LOCATION ...

GilaMonster (8/24/2012)

---

derek.colley (8/24/2012)

---

Which presumably means that if the database was located to an instance with a different collation setting, all database, table/object and column levels of collation would achieve this...

Good question, I thought there would be a limit but didn't know what it was. Guessed 1000 would be okay (overlooked the zero!), 8096 too many for a #table,...

You should always create your trace files server-side, since this places least load on the server. SQL Profiler is a client-side wrapper for a server-side process, as such the...

My (dirty) solution: Add a couple of REPLACEs at the end of your code, outside the loops:

SET @str = REPLACE(@str,'nn','n')

SET @str = REPLACE(@str,'nnn','n')

Well spotted!

In response to an email asking some questions about the script I posted, some more related scripts...

The first is short and enables you to create a dictionary of the...

You've got the isolation level set to READ COMMITTED in your second (SELECT) transactions. So if they are trying to read data from tables locked for UPDATE (your first...

Definitely not - the problem with FOR LOGON triggers is that if something happens...

Dwain - elegant but doesn't work for larger values. Example:

DECLARE @foo VARCHAR(20)

SET @foo = '00002432002000'

SET @foo = REVERSE(1*REVERSE(@foo * 1))

PRINT @foo

Output:

Msg 248, Level 16, State 1, Line...

Database users are mapped to server logins (and vice versa). I'm afraid you will need a server login to associate a new database user with. The server level...

Should follow BODMAS, i.e. Boolean, Division, Multiplication, Addition, Subtraction.

If you don't have audit capability, here's my take on how to do it.

-- this sets up the table

CREATE TABLE loginAudit ( login_name VARCHAR(MAX), last_login_date DATETIME )

INSERT INTO...