davidandrews13 (4/7/2009)

---

oh i understand why 'where col1 like 'null%' doesn't work .:) presuming thats the bit your replying to?

i was just shocked that 'where col1 not like 'null%' does seem...

It really depends. There's nothing that says a self-join is inherently bad and with proper indexing I would assume better performance than moving the data out into temporary tables and...

It's a classic bookmark lookup issue. There are a number of possible solutions, but it really depends on your structure & business requirements. Do a search for solutions, but be...

To perform both, you might want to look into using SSIS. You'll get a lot more control although it will require more work out of you. Otherwise, the other posts...

Cool. CA released a free version. That's great. Good to know.

davidandrews13 (4/7/2009)

---

surprisingly, for me it does seem to work.

i just did a simple...

fminns (4/7/2009)

---

Hi

Yes, I guess the WITH REPLACE would be the way foeward here. It's not what the course materials are telling me though which is just bound to confuse me...

The one that comes built in with SQL Server. It's not great, at all, but it does the basics reasonably well. If you have a full Office license there's also...

Can't you use WITH REPLACE just like you would with a regular full backup restore when the tail hasn't been backed up?

Me too. This place is excellent. Thanks Steve.

Jeffrey Williams (4/6/2009)

---

Not in v1 (AFAIK) - but, I hear that v2 not only has remoting capabilities but also the ability to create multiple threads (jobs).

I use powershell scripts to...

We've started using PowerShell more and more, but not so much for monitoring since we use Operations Manager for that. We've mainly been using it as a means for cleaning...

It is possible that checking the queries and getting a good index in place may help as well. I'm personally not a fan of the DTA, but it can help....

First, turn off 1204 when you're collecting the info with 1222. It'll cut down on the noise and make it a bit easier to read.

Second. You're getting lock escalation as...

All three queries are going after sgDataOPERATIONS. Is there a read statement prior to the delete statements that would cause lock escalation? What do the execution plans look like on...