xp_cmdShell doesn't use your personal credentials. it uses the account SQL starts with instead, and in your case that account doesn't have access to the network path:

this is a common...

profiler = heavy impact i agree, but a server side trace I still believe has negligible/almost nil impact; that was what i was trying to say.

i've placed both a DML...

you need to decide that the new user is going to copy/inherit the roles of a specific user.

for example:

insert into user_role

select

3, --the userid of the new person...

winston I'm in the same camp of not worrying about the trace impact after this article about the near-zero impact of a server side trace where someone actually compared...

ahh... no i don't believe so...the database is not available, or no definitive to the to the logon connection...you know i can connect to master, but query db1 using 3...

this is a per-SQL-Server installation/instance trigger, not a per-machine trigger...

so if you have a server named "PROD", and it has a default SQL instance, and two named instances, ie "PROD\SQL2005"...

i'm thinking something like this:

bring everything is as one big field...i'm assuming varchar(8000) would hold it, but it might need varchar(max).

once in a table, use CHARINDEX2 to chop everything up...

Wayne i thought the OP was running into the fact that...

I don't see an advantage to not copying the functions to the new server's master database.

Cross database functions with a synonym are going to be slow, and have an additional...

you can always connect to the tempdb database and run your scripts; your objects will not have any impact anywhere.

i would simply install a local SQLEXPRESS on my own development...

Mac:

CREATE TABLE definition?

the actual [Account_Code_AK] values for one of the items that is duplicated so we can see?

names of the tables that reference that alternate key?

Mac we probably need a little more info...does the table for Account Code have an identity/primary key, in addition to the two columns you showed us? are their foreign keys...

here's another example i posted that has additional logic, and check out the thread it came from for more info:

http://www.sqlservercentral.com/Forums/Topic927131-359-1.aspx

in this case, i'm trying to prevent SSMS and also...

oops..

forget the cursor, you can and should do this with a single update:

UPDATE SOMETABLE

SET new_date = start_date

WHERE new_date <> start_date

AND status <> 'reopen'