Sounds like you're doing a good job. Keep it up. Focus on the metrics to drive your decisions. Take a look at Gail Shaw's blog post on "catch-all" queries. That...

Mike Scalise (9/29/2016)

---

Grant Fritchey (9/29/2016)

---

I'd just do them one after another.

I did set up a Powershell script once that spawned threads to run multiple backups simultaneously. I'll never do...

Yes & no. It really comes down to pain points. Not every query...

Without all the details, what I'm about to say should be taken with a large grain of salt...

I'd be inclined to do any updates directly against the table in question,...

Of course using Redgate tools is the ultimate answer. SQL Monitor would be the one to use in this situation. You can link to a server without installing anything to...

I'd just do them one after another.

I did set up a Powershell script once that spawned threads to run multiple backups simultaneously. I'll never do that to a production...

I'm not sure it's 2014. I know 2016 is free. Here's the link.

On the PK:

Don't confuse the primary key and the clustered index. While the default is for the PK to be clustered, you don't have to make the clustered index on...

BLOB_EATER (9/29/2016)

---

so....I will be doing a presentation in front of 40 people soon, I was wondering if the vets here have any advice? Practice in front of a mirror? smile?...

drew.allen (9/28/2016)

---

mcfarlandparkway (9/28/2016)

---

TY for the response, In the recent code we are selecting data form temp table where DOC NOT IN (select DOC from table where code<> -1)

This is what...

ScottPletcher (9/28/2016)

---

Eric M Russell (9/28/2016)

---

ScottPletcher (9/28/2016)

---

You'd still need to keep at least the history from the previous check, because an index/table could be dropped, which would remove it from the...

mw112009 (9/28/2016)

---

Select name FROM ReportServer.dbo.Catalog where type = 2

--This gives you the list of all the SSRS reports in your Reporting Server. Agree ?

-- I am looking forqward to...

For production, first thing, everyone has a second login from their standard one. One that's for your machine, email, development, whatever. Another that's only for production. A lot fewer errors...

Anyone who has the capacity to overwrite the database in a restore from a security stand point is going to be able to undo your changes. DDL triggers don't have...

I don't completely understand what you're asking? Can you expand on what it is that you expect to return? What's the data structure you're pulling information from?