As much as you can do it it seems like a good idea. Assuming you have CI/users of your application in order for db first to work you need to...

C#/SQL Server product I work on. Generally start debugging in C# to find the particular stored proc/parameters that are being used.

If after a few minutes I can't figure out...

I guess it depends what your job is. If it is supplying relevant information to the program/division etc (whatever is greater than your direct boss) then you probably should do...

This is SQL Server: you might not be able to get MS support but if you have a db inconsistency or something chances are their are 3rd party guys (even...

I agree with the editorial and would add as someone who's worked both as a DBA and now as a server side software developer: it often depends on how actively...

That doesn't really clear it up for me. She talks about rolling back the same transaction that the truncate was done in. There are exclusive locks: "and just like all...

Well there is logged and then there is logged. I seem to recall from by db courses and anywhere I've read online: ex. http://www.mssqltips.com/sqlservertip/1080/deleting-data-in-sql-server-with-truncate-vs-delete-commands/ that the deletion of...

+1 truncate. I ran into it recently but there is one cevate: if the table is referenced by foreign keys you can't truncate (even if the FK constraints are cascade...

More love for SSMS: Specifically I'd like it to look just like Visual Studio (themable, good intellisense, more modern look etc), and roll in all the other tools (profiler and...

The query Kevin added seems to work for SQL 2008 too. Particularly like the calls per minute break down helps compare things that might have been cached a different amount...

Like everything ... it depends. Generally if you are being paid for and paying for (ie have customers and are paying employees salaries) you have to manage some combination of...