just the methods you probably already know:

SELECT INTO MyTABLE_bak FROM MyTABLE, or if you want to put them in a different database, SELECT INTO SELECT INTO SpecialDatabase.dbo.MyTABLE_bak FROM...

well i found a post stating the obvious: adding debug stuff like PRINT statements would slow down a proc, and forgetting to sue using SET NOCOUNT ON to avoid extra...

David Paskiet (9/2/2011)

---

As I remember the article, that is the root of the problem. Due to the large block, the compiler/execution plan cant do it's thing properly. so...

can you get an execution plans of the same proc with and without the huge comment blocks? that would be where i'd look first, i think...there's GOt to be ...

comments are ignored by SQL server completely...it's much more likely that because you edited the procedure, it was recompiled,a nd the recompilation made a better plan, which executes faster than...

glad i could help!

you can try to get fancy, and do something...

erkan.erbil (9/2/2011)

---

On 08/31/2011 between 13:00 - 14:00 o clock on PROD Servicemanager DB data in Tables XXXXXXM1 / XXXXXXM2 were deleted. We don't know how and by whom.

Appserver Logs showed...

just to confirm and expand on what Howard said...

as soon as you change the ansi setting shown in my screenshot below, and in a new window...

if you perform some updates...

you'll have to script each view out and issue teh ALTER VIEW statement for each;

but you can use the metadata to find them and script them out from there:

select *...

by are not distinct you mean duplicates?

you can use row_number() function or group by...having count(*) > 1

SELECT * FROM

(select row_number() over (partition by ColumnList Order By ColumnList) AS RW,

ColumnList...

that might be normal, if domain users get their access...

well, it's one thing to *think* he ahs db_owner, and another one to check.

run these queries in the database in question:

select

userz.name,

userz.type_desc,

decripz.name as _member_of_this_role

from sys.database_principals userz

inner join sys.database_role_members rolez

on...

compression was...

is there a trigger on the table that is inserting into an audit table somewhere? maybe it's permissions on the Triggers Audit table that the user has no permissions for.

the order of the columns are important.

i hate the pseudocode of col1,col2, so lets switch to a little more detailsed example.

suppose you have an index like this:

CREATE INDEX IX_OrdersTable ON...