Yeah, INSTEAD OF triggers are an option, but so aren't cursors. I know cursors do have their use, so I am sure INSTEAD OF triggers do as well. ...

Sure you can do exactly what you propose except you can't wrap CORRECT in single quotes. Since the data you are comparing is in the same row you do...

Does your provider agreement include job scheduling? If not you may not have the option of jobs. You may have to write your own scheduler that connects and...

You do not have rights on the production server to create jobs. In 2000 I believe you need to be in the sysadmin or processadmin group to create jobs...

If you aliased you tables and then used Alias.column it would be a bit easier to help as we don't know what columns go with what tables. That being...

As the others have said, indexes are important, especially in a datawarehouse.

That being said, you need to be careful with recursion as it is basically hidden RBAR. It may...

You can't assign a server role as part of the Create Login statement. You need to call sp_addsrvrolemember after creating the login.

Sounds like MS DTC is not running on one of the servers.

This is one reason actions that rely on resources outside the current database within a trigger is...

At least in my install SQL Server will implicit convert '20080919' to a date like in this query:

Select

Case

When '20080919' > getdate() then 1

Else 2

End

Sure the syntax for a DDL trigger is like this:

Create Trigger dbo.user_log

On Database

For Create_User

As

Insert Into logging_table

(

sql_command

...

Looks like there is not a column named Status in the view you are trying to get the data from. The CreateDate is also not in the view and...

paul.starr (11/11/2008)

---

error is

Msg 207, Level 16, State 1, Procedure BILLTO_Customers, Line 14

Invalid column name 'Status'.

Msg 207, Level 16, State 1, Procedure BILLTO_Customers, Line 34

Invalid column name 'Status'.

Msg 207, Level...

I don't believe that you can add a trigger to sys.sysusers as it is a system view NOT a table.

You can use a DDL trigger on CREATE_USER then you can...

Oh where to begin.

None of your @column-name's will work as anything beginning with @ is a variable and you never declare any variables.

I'm not sure why you are going through...

IMO, you should batch the inserts and do a TX Log backup after each batch. Or set the DB to SIMPLE mode.