Well all did that, at least once.

I was most fortunate to have blocked out that sad memory... it all case screaming back at me. :hehe:

Thanks for letting us know :w00t:.

Do you preffer Intellisense to SQL Prompt, or is it too soon to make the switch?

The difference is that the constraint is Ainsi standard and makes more portable code.

As a personal prefference I also like to see the constraints straight in the table DDL instead...

There's no way in hell that Select into was the only contributing factor in this.

Are you sure you didn't have other problems like blocking, index building, too much data processed...

I agree that those aprenthesis are useless in that context, but that's not the problem here.

If those are reporting tables, you can consider truncating them before inserting the data. That won't lock temdb for the duration of the insert.

That's what I use to grant permissions on everything at once (only SPs included)

CREATE ROLE SP_EXEC AUTHORIZATION dbo

--User for RAC

CREATE USER TestIdeal FOR LOGIN TestIdeal

--User for Local system

CREATE USER Ideal_Intranet...

Just change your create sp code to this :

CREATE PROCEDURE dbo.Whatever

AS

--...

GO

GRANT EXECUTE ON dbo.Whatever TO SP_EXEC

GO

Of course if you don't have a change management system in place, it might...

Yes, that's 3 rows, 1 row, 3 rows...

Could you post the exact code as well, the only time I had problems with go was within dynamic SQL... so that is most likely not the problem!

I create a role called Sp_exec.

I grant sp_exec permissions to execute all the sps on the server (open a cursor on all the sps and grant exec that way).

Then when...

You can always test that design if you want... just be sure that a children will never be considered a person in the system so that a major refactoring is...

There are cases when putting a proc in master makes for the best solution. We don't have enough details to know wether or not it's needed in this case...

I don't really understand how the 2 statements are equivalent... or more importantly what you need to do. I never had to import a table one column at the...

run sp_who2 and check the column programName. If someone is using Access that will be marked there.

In 2005+, if you access to login trigger where you can do similar...