OK, I didn't quite understand first time. You have these two .cmd files that are triggered automatically whenever a logon or logoff event occurs (presumably on AD) - is...

I don't think it'll work if you just lift sqlcmd.exe and copy it somewhere else. It needs access to all sorts of DLLs and other stuff. Why can't...

It's not a question of whether the file is read-only - it's whether you have permission to change it. Right-click on the file and choose Security. If you...

But you don't want it running against databases that don't have the tables - that would be a waste of resources. That's why I suggested scripting it properly. ...

If you need to run it regularly then it's worth taking the time to script it properly. Are the databases that contain the table the same databases from week...

What are the permissions on ther actual file itself?

When changing NTFS permissions, you either need to change them at the level they were originally set and cascade them down, or...

Why do you say "like sp_msforeachdb"? Is there any reason not to use that stored procedure? Is this a one-off, or a regular requirement?

John

Have you checked your NTFS permissions on the package file?

John

In that case, I think I'd import into SQL Server tables as is, then use a splitter (search this site for how to do that) to separate the values, and...

Notwithstanding Sean's point about SSNs, you could do something like this. It splits the string into a table of component characters, performs the transformation, and then reconcatenates them.

with numbers(n)as...

I don't use packages in msdb, so I'm not entirely sure. Are you using a deployment manifest? If so, you sholuld be able to just specify the location...

What are you going to do with the data once you have separated the columns - import it into SQL Server, or something else? Is there a maximum number...

Not enough information. File system or SQL Server deployment? And what precisely do you want avoid doing - visiting the server physically, using an RDP session, mapping a...

If you're getting collation conflict errors, you have three options:

(1) Insert...

It's not even as simple as that, I'm afraid. Where you have primary or foreign key constraints on any of the columns you're changing, they need...