Netapp issues with SQL2000 SP4

Has anyone successfully implemented SQL 2000 or SQL 2005 on Netapps? Main
application is SPS 2007 (5GB of data) and various other smaller DBs (appox
1-2GB, 10 seperate DBs)
We are having major disconnects with SQL when we move to Netapp FAS3020. We
followed the Netapp implementation to the T.
It doesn't matter if we have a IIS 7.0, WebService, or directly quering SQL
on the netapps. It will work for a few hours then all of a sudden, it will
"disconnect". There's nothing in the SQL log. Web services will result in
"Service Unavailable" We will have to totally reboot the SQL Server to get it
back online.
Netapp says it's a Microsoft Issue.
I don't now Netapps.
But you should isolate the problem first. So.
Run Profiler On the SQL server...see if you have time-outs long running
queries?
Check the webserver logs.
Check if youre NIC on database and webserver are not the bottleneck...and
if it is configured okay.
Network performance okay?
Greetz.
"GSoD" wrote:

> Has anyone successfully implemented SQL 2000 or SQL 2005 on Netapps? Main
> application is SPS 2007 (5GB of data) and various other smaller DBs (appox
> 1-2GB, 10 seperate DBs)
> We are having major disconnects with SQL when we move to Netapp FAS3020. We
> followed the Netapp implementation to the T.
> It doesn't matter if we have a IIS 7.0, WebService, or directly quering SQL
> on the netapps. It will work for a few hours then all of a sudden, it will
> "disconnect". There's nothing in the SQL log. Web services will result in
> "Service Unavailable" We will have to totally reboot the SQL Server to get it
> back online.
> Netapp says it's a Microsoft Issue.
>
|||Did all that. The thing is that no errors are generated. Timeouts vary from
under 30 mins to over 4 hrs. There's no pattern and it would stop in random
locations in a test process. Due to the randomness, it's hard to even begin
to start to isolate the issue.
We have a test script that writes and deletes "hello world" to a text field
and that would also generate a failure.
"Hate_orphaned_users" wrote:
[vbcol=seagreen]
> I don't now Netapps.
> But you should isolate the problem first. So.
> Run Profiler On the SQL server...see if you have time-outs long running
> queries?
> Check the webserver logs.
> Check if youre NIC on database and webserver are not the bottleneck...and
> if it is configured okay.
> Network performance okay?
> Greetz.
>
>
>
> "GSoD" wrote:
|||I know you used to have to set a trace flag but I am not sure if that still
holds true or not. Anyway maybe this will help:
http://www.sqlteam.com/article/sql-server-and-network-attached-storage
Andrew J. Kelly SQL MVP
"GSoD" <GSoD@.discussions.microsoft.com> wrote in message
news:FBACC353-992D-49D2-B883-6DDE3DBFEBDF@.microsoft.com...[vbcol=seagreen]
> Did all that. The thing is that no errors are generated. Timeouts vary
> from
> under 30 mins to over 4 hrs. There's no pattern and it would stop in
> random
> locations in a test process. Due to the randomness, it's hard to even
> begin
> to start to isolate the issue.
> We have a test script that writes and deletes "hello world" to a text
> field
> and that would also generate a failure.
> "Hate_orphaned_users" wrote:
sql