You wopuld have used dbcc sqlperf(logspace) to see how your log was being used and then tried shrinking.

If you wish you dont want to use the servername,portnumber everytime you connect then you can create a alais and use the alais nmae to cll your sql server.

Restoring master database can't be done as how you do for a user db. You have to have the server in single user mode before you do a restore of...

Yes no access for developers/testers in the production box what if they tamper your data.

Include 'X'n the type clause so that it searches for extended SPs too.

How big is the table and how many users are there in the database? Are permissions being given to individual user or group.

Its not that we don't faith MS but there might be issues that arise when the build is not needed. So better to check and deploy the build as and...

I second him. If you update stats and then rebuild index your sysindexes will be with new set and update stats that you have done will have no effect. better...

To get the login information you have to think of a solution that best suits your needs. I have a service that checks the syslogins database view every 10 secs...

Yes syslogins will have information about logins at server level and sysusers will have users details at database level.

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=5&messageid=374262

This mssage post should help you the script is given there in th post chain itself.

Ok i dint remember that it would be a network protocol problem too.

I agree with Aaron move to the latest service pack and then apply build if and when necessary.

For database level checking use sysusers table for each database moreover the question was not really clear.

It means that you are using functions inside the select statement of the view and the index that youhave created on the view will not be used by the query...