TravisDBA (2/23/2011)

---

The mindset of most managers will never support this at most companies. Most managers I know need to know you are on site to verify you are working. That...

Very true. So work on educating them and helping them to be better managers. Give them reasons to trust...

You can right click the database, then select Tasks, then Shrink, then files. Shrink just the log file.

Look at the largest log backup you have, add a 10-20% pad, and...

I would look to tune to batch instead of worrying about the a temp table v table variable. They can both spill into tempdb, depending on size.

I might look to...

How big is the database?

You could backup/restore every night. I know people that do that. However if you have lots of non-changing data, then it might be easier to do...

GSquared (2/22/2011)

---

What I was asking was: Did Steve mean the question to be about legitimately protecting code, or did he mean to ask about people actually using completely ineffective means...

Not yet, I'll see if I can determine where this is on our list and when it might get changed.

It's not the restore method, it's the recovery model. Run this:

SELECT DATABASEPROPERTYEX('db1', 'recovery')

If it's simple, then just

Backup database mydb to disk = 'c:\mybackup.bak' with INIT

Replace mydb with your database name,...

You might read this to better understand. I believe this is the stripe alignment of each particular drive as seen by Windows. So potentially the array is not aligned as...

On a similar debating note, does anyone know of code in SQL Server that's worth protecting with CLR, obfuscation, or any hassles of encrypting? Not data, but code?

I'm not saying you're wrong. But in two decades of working with all sorts of companies, almost nothing I've seen is worth protecting on the database side. Accounting software, imaging...

I would argue that the database access code, queries, reports, etc. aren't done with a lot of research and development. The techniques for querying data aren't that hard to learn,...

I've reworded the answers to eliminate confusion and awarded back points to everyone up to this time.

You can modify the WHERE clause to avoid those rows that have the item already. So something like this:

update MyTable

set MyChar = '1' + MyChar

WHERE SUBSTRING(...

This can be helpful (developer read in production), but it also produces another attack vector for security. Developers being able to pull that data out, means potential breaches, especially if...