Hello,

I had just a quick question....

I am working with a sql2005 server and recently have been experiencing some
odd problems with connectivity.

I have 4 drive for the sql sql server
C: --> OS
D: --> program files -- SQL server and a few other program are installed
here.
E --> sql DB
F -- > sql trans logs

about the time that the issues started happening we ran out of room on D: I
was not sure how much of an affect this would have actually had.

Any comments would be great.

my personal view and Knowledge states that the SQL Server Program
Files shouldnt be affected unless the Drive is Data or Log Drive
(those 2 are V.IMP).always keep an eye on your Log Drive and Data
Dir.. best practise: Maintain atleast 20% Threshold on these drives.
I am not sure why your SQL Program Drive should be filed up unless you
have your MSDB /TEMPDb in the Program Folder. somewhere here as for
SQL server 2005 (D:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL
\Data)

Are the SQL errorlogs and other log files on D? In that case, you should
ensure the drive has sufficient free space. It's possible to see odd behavior
when SQL can't write to its logs.

Linchi

"Romuald" wrote:

> Hello,
>
> I had just a quick question....
>
> I am working with a sql2005 server and recently have been experiencing some
> odd problems with connectivity.
>
> I have 4 drive for the sql sql server
> C: --> OS
> D: --> program files -- SQL server and a few other program are installed
> here.
> E --> sql DB
> F -- > sql trans logs
>
> about the time that the issues started happening we ran out of room on D: I
> was not sure how much of an affect this would have actually had.
>
> Any comments would be great.
>