I'm not sure what your question is. Can you please rephrase?

This shows logical files for a given database, space used, and freespace:

SELECT name AS NameOfFile,

size/128.0 as TotalSizeInMB,

...

I think Error: 0x2739, state: 1 is the key to finding the cause of this problem. Is there any additional information in the system or application event logs around...

Possibly a problem with authentication to the domain controller. AD users trying to log in would genereate that error- USUALLY sql accounts would not be affected, but if the...

see this thread for downgrading from Enterprise to standard: http://www.sqlservercentral.com/Forums/Topic367291-146-1.aspx

Perfect! That is my ammo I can use to justify setting max memory... thanks to you both.

would love to find that recommendation. best I can find is:

The default memory management behavior of the Microsoft SQL Server Database Engine is to acquire as much memory as...

Would you agree with me that SQL Server shouldnt do that? there should be no requirement so set max server memory because as designed, sql server should yeild memory...

OK- I have heard that before- can you tell me why that is the case?

My understanding from all SQL Server documentation is that SQL Server will dynamically allocate...

should have mentioned- would really like to have some offiicial MS statement on this that I can use as ammo for those who might argue that this settiing needs to...

There is no specific "event viewer file" for SQL Server. SQL Server will write events to both the application log and the system log depending on the nature of...

Also- you can look at the trace file to see what event immediately precedes the restart if you are convinced it is SQL Server related.

I remember a similar problem a...

What events immedaitely preceed the restart in the event log- both system and application event logs?

What OS is this 2000, 2003?

What SQL Server version and service pack are you running?

unless you explicitly removed BUILTIN\ADMINISTRATORS login from the server, you should be able to log in using windows authentication with an user who is a member of the local ADMINISTRATORS...

Also- is the server you are connecting to configured to allow remote connections? (if 2005 check SQL Server Surface Area Configuration)

The proper value for named pipes configuration is: \\.\pipe\sql\query

I always have TCP/IP enabled as it seems to be less problematic.

I have seen that error message when network connectivity is not...