• jasona.work (8/7/2014)


    Perry: I think CPU-wise we should be OK, and I'm not going to "bulk encrypt" all the other DBs when I'm done, I'll be doing it in chunks. We're targeting DBs initially that have "real" sensitive information in them, then moving on to the others.

    Plus, these DBs are all far more read-heavy then insert-heavy, so that should help some.

    SQLRnnr: At this point, I've decided to go with one Agent job, one DB per step, starting with the smaller DBs (under 1GB {Yes, under a GB}) first, then moving on to the bigger DBs. If one fails, it'll fail the Agent job and e-mail me, so I can restart skipping the problem child and fix it after. Plus I'll check on it off-and-on throughout the day / weekend...

    Thanks guys!

    Jason

    Curious what you will be putting in the agent step - just the command to encrypt the database?

    If that command fails - great. But that command can succeed in about 1 ms. It doesn't wait for the database to fully encrypt.

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events