That is what your second query is doing.

Each database master key should be backed up.

Roy Ernest (8/18/2011)

---

Thx Stephan, Gus and Jason for the input.

Thread needs only 865 posts to hit 30K and I need 80 posts to hit 3K. Who will reach first,...

Then I would start looking at what caused that much growth and that much log space to be consumed.

Here is an article to help with that.

http://www.sqlservercentral.com/articles/Log+growth/69476/

In the meantime, I would...

I do it much the same as Gus.

Thanks - it actually made me think of an article to write

FYI - we need only 866 posts to reach 30K

Make sure the file is empty (move contents to another file) and then drop the extra files.

Good to hear.

Precisely.

What is...

This should do it for you.

Declare @ColorType INT = 3

Select cp1.*

From ColorPlate cp1

CROSS APPLY ColorPlate cp2

CROSS APPLY ColorPlate cp3

Where cp1.colortype & cp2.colortype & cp3.colortype & @ColorType <> 0

Order...

Yes, it grew by that amount.

Is this database in Full recovery? Are you backing up the transaction log?

If either query produces a null, the division or multiplication of those fields will result in NULL.

Do either of the subqueries yield a null when you run them individually?

This might be overkill, but it should get you everything you need.

http://jasonbrimhall.info/2010/03/19/security-audit/

I could see that improving perf too. I would be careful in implementation and data change though.