Tune the query, tune the indexes. Without more information that's about all that can be said.

I asked on your other thread but got no answer, is your instance case-sensitive?

What's the exact version of SQL Server that you're working with?

Look in the SQL Server error log, what is the exact message which gets recorded for the login failure?

'Custom audit' can be as simple as logging information you want to keep for as long as you want to keep it. Start by figuring out what you want to...

Unless you had some custom auditing implemented before that change was made, no way to tell.

That happens so often. 🙂

For what, creating a temp table? http://technet.microsoft.com/en-us/library/ms174979.aspx Scroll down to the Remarks section and look for the header "Temporary Tables"

Same way you test the performance of anything, benchmarks without, benchmarks...

Uninstall. Reinstall.

Kinda, create a table to store the value and increment/decrement the value as appropriate when the procedure is called. You'll have to watch locking/isolation levels to ensure the correct results...

It works much like nonclustered index on a table do. When a row in the table is changed, the indexes are updated appropriately. Indexed view gets much the same treatment.

Could you please post table definitions and some sample data (as insert statements)? See http://www.sqlservercentral.com/articles/Best+Practices/61537/

Try changing the permanent table to a temp table, I can't see any valid reason why that script would be creating a permanent table in tempDb instead of just using...

Restore from backup.

The only time repair rebuild will fix corruption is when the second-last line of the checkDB output reads "REPAIR_REBUILD is the minimum level to repair"

It has a decimal place, hence it can't convert to int. Try float or numeric/decimal instead.