What is the real world problem you are trying to solve?

Please have a look at what Dave posted. A scalable solution is there for the taking. Hint: look for the function DelimitedSplit8K.

You could do this work with a Script Task but it will be a whole lot more code than using PowerShell. Here is a one line PowerShell command to copy...

Sometimes a sledgehammer is the only way to go depending on the size of the nut you have to crack (or expect to have to crack down the line) 🙂

Here...

james.morrison 19355 (6/19/2011)

---

Make the database read only and see if anyone complains. 🙂

Or take it offline completely and see if anyone notices.

Seriously, if you are really asking the question, it...

You're very close. Keep in mind that the beginning and ending tags of all T-SQL language features must always match up in the order in which they're declared; and that...

Here are a couple ways to get there.

On 2005 you can try the UPDATE...JOIN syntax which is proprietary to SQL Server. It's not ANSI compliant and it suffers from...

I couldn't help myself...it's been a few years since I used BCP regularly so I had to put what I said to the test.

---

Step 1) Execute this code against your...

Jeff Moden (6/17/2011)

---

opc.three (6/17/2011)

---

I don't disagree. My stance on it is part security and part "developers, stay away from the servers hosting my SQL Server instances". If I open up...

I would recommend you use PowerShell for sys admin scripting tasks. You can schedule your scripts to run periodically using the SQL Agent PowerShell step type (2008+) or invoking PowerShell...

The bcp.exe utility is what you want. bcp is much different than BULK INSERT.

BobMcC (6/17/2011)

---

No sooner than I typed this I read an article by Adam Machanic that seemed to wrap everything into one...

http://sqlblog.com/blogs/adam_machanic/archive/2009/08/24/dr-output-or-how-i-learned-to-stop-worrying-and-love-the-merge.aspx

Essentially it looks like I can do....

INSERT into History

SELECT pk1,...

stewartc-708166 (6/17/2011)

---

No, as far as the publisher is concerned, the view is a table (albeit virtual) and will publish to a table at the destination.

this will be substantially more efficient...

One possibility: the account running the SQL Agent job does not have access to the file path where the PS script resides.

PHP on *ix talking to SQL Server is a challenge because of the lack of a complete and current open source driver. FreeTDS is the generally accepted "best one" and...