That is a good read. Basically SQL Server sees your @state variable as a single string not a delimited list for use with IN. You need to split...

Sounds like something you should be doing in PowerShell. Since you haven't actually shared a script it is a bit hard to comment on how you'd implement the check....

Do you mean you do not want the history of your job logged to sysjobhistory? I think you'd have to do custom logging within the job to do it....

You should be able to apply a filter on the HostName column. Have you tried that? If you are not sure how to do it check out this...

What you mention is why I am not super impressed with SQL Server's encryption functions in 2005/2008. I am in favor of doing encryption in the business layer. ...

jcrawf02 (10/9/2009)

---

Jack, wouldn't you want to increment the @enddate value to the next day in the variable itself, and then just use < @enddate instead of two functions in the...

Interestingly enough I just had this conversation Wednesday with one of my bosses who just moved to my location. My take is that I am responsible for my professional...

I believe something like this is how you'd do it:

=Sum(fields!name.value)/Sum(If(fields!name.value = 0, 0, 1),

You don't necessarily have to have everything in the dbo schema as long as all the schemas are owned by dbo. Then ownership chaining will still work. I...

Logging is the way that SQL Server guarantees consistency. By reducing batch size and backing up the transaction log you will not/should not experience log growth which can be...

2 things I'd try:

1. If it is not a production system run Profiler against the database while you run the procedure. You'll want to make sure you filter...

Are you getting any errors? While this is not how I'd go about it, it looks like it should be working.

This article[/url] will answer most of your questions. If you have any questions after reading the article I suggest posting them in the article discussion as the author is...

Well, you are doing the entire copy in a single transaction which is why the log file is growing so much. If you batch it with TX Log backups...

I think this is what you are looking for:

UPDATE A

SET A.Idclient = B.ID

FROM Orders A INNER JOIN Clients B ON A.CleintName = B.ClientName