Depending on how your exchange/default SMTP server is configured, you may want to try changing your SMTP Authentication mode to "Anonymous...

There's nothing really wrong with using a parameter in a WHERE clause, however in cases where the parameter could drastically change the results, then it could have an impact on...

Monster.com, Indeed.com, Dice.com, LinkedIn, Google can give you a wide-range of candidate sites...

Requirements are typically a "wish" list, however I wouldn't apply for a position where you have 3 out...

Man I don't know if that's real code of pseudo code (which I hope it is) because I've never seen BEGIN LOOP 😀

Something like this might work (if you give...

SQL server makes you aware the deadlock occurred, but it's not causing the deadlocks, your code is causing the deadlocks (whether that be TSQL, application code, etc.

Deadlocks typically...

Agreed. Thanks for the clarification!

Sorry, I meant that if the column he's looking to find is a part of/ or is the clustered index, then the structure of the data is already sorted, so...

To add to what sqlbuddy has said, check the fragmentation percentage first, if it's quite low, don't bother rebuilding it unless you're seeing some performance degradation because of it. ...

If the "key" is a part of your clustered index then your top 1 select statement should pose very little overhead. If that's not an option, within your trigger...

Yes, this is a server-level setting.

Check the "Remote Query Timeout" setting under your Connections tab for the SQL Server, you can set a default timeout from there, or set it to 0 (no timeout)

You should be able to snag the total pages used from the DMV below:SELECT used_page_count, row_count

FROM sys.dm_db_partition_stats

WHERE index_id = 1

TRUNCATE will be faster and be minimally logged (it will only log the page deallocations in the transaction log), if the data isn't needed this is the route to take.

I believe there is an issue with your Log Reader Agent (you probably already know this) - it could be because something is blocking it on the publisher so check...

Are you asking this from an SSRS report point-of-view? SSIS? Web application?