New answers tagged

0

Well I totally agree with the concerns raised by earlier answers in this post but as far as your actual query is concern, the following method can be adapted You may introduce insert/update triggers to encrypt data and do the encryption stuff. You may also trim the actual data iin current table to just keep the last 2 digits for card or SSN or whatever you ...


1

(OK, this is not an answer. Rather it is a warning that the question reflects a need for far more research.) Lock your doors, but don't bother to lock your windows. If you have a laptop with Social Security Number on it and it gets stolen, it won't matter if the data is super-duper-encrypted -- the decryption key is sitting somewhere in the laptop! You ...


1

SQLIO is technically deprecated - it's been replaced by the newer utility Diskspd. However, the same basic answer applies. If you look at an existing server and guess how much storage throughput it's USING, then look at the counters: IOPs - Physical Disk Reads/Sec and Writes/Sec IO size - Physical Disk Read Bytes/sec divided by Reads/sec (and same for ...


5

Good news! You don't have to query Simpana, NetApp, or PowerShell to figure out where the log file sizes have been changing. Just query the msdb.dbo.backupset table - it tracks database name, backup date/time, and backup size. You can trend this over time. I like charting this with Excel or SSRS to show volume trends, and then I can drill down into detail ...



Top 50 recent answers are included