this seems to do what you want...i'm doing an order by on the username, and then the username with case sensitive collation:

the desision to order by the second as DESC...

here's the visual results of my current query for reference: my expectation is that for AREAID 1887, the "buidlingindex" should be all "1", and the apartmentindex increments as seen below.

ID...

not an expert here by any means, but i think "NetAPP SnapManager ", and what it is doing behind the scenes is more than jsut a SQL Server Enterpise Snapshot;...

go to the scripting options and check "script indexes" "script "triggers" and anything else you might need scripted,a nds simply rerun the process.

in SQL Server Management Studio, have you tried right clicking on the table and selecting "Script Table As ..."

Then you can rename the table and the constraints that are part...

windows login methods are never disabled...but a domain login might not work yet, is that what you mean?

can you right click on the link to SSMS and choose Run As......

in that case, look at this article, which shows how to audit access to the databases with a server side trace:

http://www.sqlservercentral.com/articles/Administration/trace/872/

once that is in place, you can insert the results...

rather than tracking where the inapproprate acces sis coming from, you could change the passwords for those two users, or maybe use a logon trigger to prevent access for those...

i believe when you google as instructed above,you'll finds posts referencing how when you connect via the Dedicated Admin Connection(DAC), everything is decrypted for you, so you could script...

your table dbo.deleted_table, has an identity column in it, don't stick a value in it .

actually name each and every column that SHOULD receive a value from the insert instead.

INSERT...

well, obviously it would be betrter to redesign the proc so it can run concurrently, but that's a future enhancement.

I think you are right, you'll have to use some sort...

ipconfig will return information about the SERVER's NIC card...it would not have any information about the connecting users. that code might seem to work if your SQL server is also...

you have to use the EXECUTE AT [LinkedServerName] syntax to do that; 4 part names are DML only, so you cna insert/update/delete to a 4 part named object like MyLinkedServer.DatabaseName.Schema.Table,...

this will give you the trigger name and the definition for everything in a given database:

--SQL 2000:

select

sysobjects.name,

syscomments.text

from syscomments

inner join sysobjects on...

probably the easiest way is to to set it to single_user:

alter database emptyexample set single_user with rollback immediate

drop database emptyexample