Nice Article Jeff!!!

I was almost disconnected with SSC for couple of months and got a chance to read the article today. Nice work!!!

I remember when I read one of your posts (1...

What about an employee on rotational shifts or flexible timing? Or the one who do overtime? Time data type wouldn’t be sufficient to hold that information.

Did you notice any network issue? Is it only for SQL Server connections or do you get hiccups while pinging or RDP.

A screenshot would be good. It will help us to see what exactly you see. You can attach it here while posting (edit attachment button at bottom right corner).

That’s good. Also, collect the performance statistics of stored procedure executions and share it with .Net team. If it’s still not convincing enough, please share this discussion (SSC) with them...

I can make one of each table - with say, 2 records in each and (hopefully) convert to a different format, if .mdb is no good. Plus screenshot some dummy...

You should worry on Log File size than Backup Size. Adding some...

Divide and Conquer.

Split the SP’s logic in few steps, create new SPs for each step and call each SP from application. Each SP can provide its own status (success /...

@Lynn (and many other dedicated volunteers here): Please don’t give up and remain dedicated as you are. I am happy community is blessed with you guys.

@Humiliators: You have...

Indexed Views:

http://msdn.microsoft.com/en-us/library/ms191432(v=sql.105).aspx

Slight modification...

You can try using the estimated / actual (preferred) query plan with both queries in the same batch, that will show a percentage of the batch that each query...

Nope but you can enforce it with triggers.

select pr.name 'Login', sp.permission_name 'Permission'

from sys.server_permissions sp

inner join sys.server_principals pr

on pr.principal_id = sp.grantee_principal_id

where pr.name = 'test' -- Replace your login names here

select sp.name 'Login' , sr.name 'Role'

from sys.server_role_members srm

inner join...

It should help...

http://blogs.msdn.com/b/psssql/archive/2010/08/03/how-it-works-error-18056-the-client-was-unable-to-reuse-a-session-with-spid-which-had-been-reset-for-connection-pooling.aspx