Does anyone have experience with both Netapp SANs and EMC SANs,
supporting MS SQL 2000. If so, what's your opinion of one versus the
other?
We're currently using a netapp f825c and are wondering how EMC
compares.
Tom Chutedo you mean network appliance "NAS" ?
Greg Jackson
PDX, Oregon|||FYI: Yes, I do mean SAN. We're using a fiber channel to connect an
825c to an MS SQL Server. We have a single database split across two
filer heads.|||tom_chute01@.yahoo.com (Tom Chute) wrote in message news:<b5d5c748.0410081554.41c2fb84@.posting.google.com>...
> FYI: Yes, I do mean SAN. We're using a fiber channel to connect an
> 825c to an MS SQL Server. We have a single database split across two
> filer heads.
Tom,
I just finished a very lengthy trial of NetApp FAS940's and EMC
CX700's. From a LUN performance perspective, EMC just edged out
NetApp mainly due to EMC's 8 GB of cache. Administratively, I liked
EMC better as they have a built in administrative console (Java based)
to manage multiple EMC systems and all the their functions from one
console. As you probably know, NetApp requires a different
application for just about everything they do.
Where NetApp pulls ahead is in the application support and replication
arenas. EMC does a bad job of managing Exchange and SQL replication
and snapshots. One of our main purposes for going with a large SAN
environment was for disaster recovery. The big question we had for
EMC is how do they bring back changed SQL and Exchange data from a
disaster site once the disaster is over? Their first response was to
bring over the entire database (SQL or Exchange). Our Exchange system
is over 700 gigs and we have SQL servers well over 300 gigs. Even
with a DS3 we're looking at several hours to replicate (our
replication site is 1000 miles away in a branch office).
EMC then came back with an incremental restore option that was
basically a log file rollup. Essentially the same thing as a manual
Exchange or SQL database restore. EMC just didn't offer anything
above what manual steps are required to restore databases. This may
not be an issue if you're only doing local snapshots. Both EMC and
NetApp require about the same amount of overhead for a LUN snapshot.
However, NetApp has just announced improvements to their LUN snapshots
that require less than 100% LUN overhead.
With NetApp's SnapManager for Exchange and SQL, I can perform an
incremental restore from my disaster site directly to my production
SQL databases or Exchange datastores without stopping services,
rebooting servers, and without user interruption. We internally setup
a FAS system in both locations and performed live tests with test
data. I can literally move to my disaster site, make as many changes
as I want, replicate back only the changed blocks of data back to my
production system and be working again in only minutes above the time
it takes to replicate the data back. And since NetApp does everything
on a true changed block basis, it takes me only minutes to recover
changes rather than hours or days to bring over the entire database.
The trade-off? NetApp costs twice as much as EMC. NetApp may make you
install a few more apps and administrativly it may not be as
centralized but we choose NetApp simply because it will allow us to
work with our applications better than EMC.
EMC is the monster of SAN's and maybe a Symetrics with SRDF might have
worked better but that was getting out of our comfort level for
administration and I don't think they have any different support for
enterprise applications.
Hope this helps,
JT|||Hi
We are running EMC Symmetrics with SRDF (going A-SRDF as soon as we can) to
a remote site over 1Gb fiber. Pushing 0.5Tb an hour, capable of 19Tb an
hour. 128GB on the Cache Controllers.
Big environment, but we just have to have 99.999 uptime.
Once you start to look at large SAN's, 'go big or go home'.
Photons, Clarions, DMX's and local storage are being phased out and we will
then only be running a dozen EMC's.
We are happy and won't consider anything else.
Cheers
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"JT Johnson" <jtjohnson@.faegre.com> wrote in message
news:b09ab426.0410110924.27bd276c@.posting.google.com...
> tom_chute01@.yahoo.com (Tom Chute) wrote in message
news:<b5d5c748.0410081554.41c2fb84@.posting.google.com>...
> > FYI: Yes, I do mean SAN. We're using a fiber channel to connect an
> > 825c to an MS SQL Server. We have a single database split across two
> > filer heads.
> Tom,
> I just finished a very lengthy trial of NetApp FAS940's and EMC
> CX700's. From a LUN performance perspective, EMC just edged out
> NetApp mainly due to EMC's 8 GB of cache. Administratively, I liked
> EMC better as they have a built in administrative console (Java based)
> to manage multiple EMC systems and all the their functions from one
> console. As you probably know, NetApp requires a different
> application for just about everything they do.
> Where NetApp pulls ahead is in the application support and replication
> arenas. EMC does a bad job of managing Exchange and SQL replication
> and snapshots. One of our main purposes for going with a large SAN
> environment was for disaster recovery. The big question we had for
> EMC is how do they bring back changed SQL and Exchange data from a
> disaster site once the disaster is over? Their first response was to
> bring over the entire database (SQL or Exchange). Our Exchange system
> is over 700 gigs and we have SQL servers well over 300 gigs. Even
> with a DS3 we're looking at several hours to replicate (our
> replication site is 1000 miles away in a branch office).
> EMC then came back with an incremental restore option that was
> basically a log file rollup. Essentially the same thing as a manual
> Exchange or SQL database restore. EMC just didn't offer anything
> above what manual steps are required to restore databases. This may
> not be an issue if you're only doing local snapshots. Both EMC and
> NetApp require about the same amount of overhead for a LUN snapshot.
> However, NetApp has just announced improvements to their LUN snapshots
> that require less than 100% LUN overhead.
> With NetApp's SnapManager for Exchange and SQL, I can perform an
> incremental restore from my disaster site directly to my production
> SQL databases or Exchange datastores without stopping services,
> rebooting servers, and without user interruption. We internally setup
> a FAS system in both locations and performed live tests with test
> data. I can literally move to my disaster site, make as many changes
> as I want, replicate back only the changed blocks of data back to my
> production system and be working again in only minutes above the time
> it takes to replicate the data back. And since NetApp does everything
> on a true changed block basis, it takes me only minutes to recover
> changes rather than hours or days to bring over the entire database.
> The trade-off? NetApp costs twice as much as EMC. NetApp may make you
> install a few more apps and administrativly it may not be as
> centralized but we choose NetApp simply because it will allow us to
> work with our applications better than EMC.
> EMC is the monster of SAN's and maybe a Symetrics with SRDF might have
> worked better but that was getting out of our comfort level for
> administration and I don't think they have any different support for
> enterprise applications.
> Hope this helps,
> JT
Showing posts with label netapp. Show all posts
Showing posts with label netapp. Show all posts
Wednesday, March 28, 2012
Network Applicance V's EMC
Does anyone have experience with both Netapp SANs and EMC SANs,
supporting MS SQL 2000. If so, what's your opinion of one versus the
other?
We're currently using a netapp f825c and are wondering how EMC
compares.
Tom Chute
do you mean network appliance "NAS" ?
Greg Jackson
PDX, Oregon
|||FYI: Yes, I do mean SAN. We're using a fiber channel to connect an
825c to an MS SQL Server. We have a single database split across two
filer heads.
|||No, I mean SAN. We're using a fiber connection to connect a SQL Server
to an 825 cluster. We have a single database split across two filer
heads.
The problem is that we've outgrown the 825c and need to upgrade. I like
Netapp, but my management wants me to look at EMC. I have no experience
w/ EMC, and was wondering if anyone out there has. If they have, what
was their opinion of dealing w/ Netapp and using a Netapp SAN V's EMC.
Tom C.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||tom_chute01@.yahoo.com (Tom Chute) wrote in message news:<b5d5c748.0410081554.41c2fb84@.posting.google. com>...
> FYI: Yes, I do mean SAN. We're using a fiber channel to connect an
> 825c to an MS SQL Server. We have a single database split across two
> filer heads.
Tom,
I just finished a very lengthy trial of NetApp FAS940's and EMC
CX700's. From a LUN performance perspective, EMC just edged out
NetApp mainly due to EMC's 8 GB of cache. Administratively, I liked
EMC better as they have a built in administrative console (Java based)
to manage multiple EMC systems and all the their functions from one
console. As you probably know, NetApp requires a different
application for just about everything they do.
Where NetApp pulls ahead is in the application support and replication
arenas. EMC does a bad job of managing Exchange and SQL replication
and snapshots. One of our main purposes for going with a large SAN
environment was for disaster recovery. The big question we had for
EMC is how do they bring back changed SQL and Exchange data from a
disaster site once the disaster is over? Their first response was to
bring over the entire database (SQL or Exchange). Our Exchange system
is over 700 gigs and we have SQL servers well over 300 gigs. Even
with a DS3 we're looking at several hours to replicate (our
replication site is 1000 miles away in a branch office).
EMC then came back with an incremental restore option that was
basically a log file rollup. Essentially the same thing as a manual
Exchange or SQL database restore. EMC just didn't offer anything
above what manual steps are required to restore databases. This may
not be an issue if you're only doing local snapshots. Both EMC and
NetApp require about the same amount of overhead for a LUN snapshot.
However, NetApp has just announced improvements to their LUN snapshots
that require less than 100% LUN overhead.
With NetApp's SnapManager for Exchange and SQL, I can perform an
incremental restore from my disaster site directly to my production
SQL databases or Exchange datastores without stopping services,
rebooting servers, and without user interruption. We internally setup
a FAS system in both locations and performed live tests with test
data. I can literally move to my disaster site, make as many changes
as I want, replicate back only the changed blocks of data back to my
production system and be working again in only minutes above the time
it takes to replicate the data back. And since NetApp does everything
on a true changed block basis, it takes me only minutes to recover
changes rather than hours or days to bring over the entire database.
The trade-off? NetApp costs twice as much as EMC. NetApp may make you
install a few more apps and administrativly it may not be as
centralized but we choose NetApp simply because it will allow us to
work with our applications better than EMC.
EMC is the monster of SAN's and maybe a Symetrics with SRDF might have
worked better but that was getting out of our comfort level for
administration and I don't think they have any different support for
enterprise applications.
Hope this helps,
JT
|||Hi
We are running EMC Symmetrics with SRDF (going A-SRDF as soon as we can) to
a remote site over 1Gb fiber. Pushing 0.5Tb an hour, capable of 19Tb an
hour. 128GB on the Cache Controllers.
Big environment, but we just have to have 99.999 uptime.
Once you start to look at large SAN's, 'go big or go home'.
Photons, Clarions, DMX's and local storage are being phased out and we will
then only be running a dozen EMC's.
We are happy and won't consider anything else.
Cheers
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"JT Johnson" <jtjohnson@.faegre.com> wrote in message
news:b09ab426.0410110924.27bd276c@.posting.google.c om...
> tom_chute01@.yahoo.com (Tom Chute) wrote in message
news:<b5d5c748.0410081554.41c2fb84@.posting.google. com>...
> Tom,
> I just finished a very lengthy trial of NetApp FAS940's and EMC
> CX700's. From a LUN performance perspective, EMC just edged out
> NetApp mainly due to EMC's 8 GB of cache. Administratively, I liked
> EMC better as they have a built in administrative console (Java based)
> to manage multiple EMC systems and all the their functions from one
> console. As you probably know, NetApp requires a different
> application for just about everything they do.
> Where NetApp pulls ahead is in the application support and replication
> arenas. EMC does a bad job of managing Exchange and SQL replication
> and snapshots. One of our main purposes for going with a large SAN
> environment was for disaster recovery. The big question we had for
> EMC is how do they bring back changed SQL and Exchange data from a
> disaster site once the disaster is over? Their first response was to
> bring over the entire database (SQL or Exchange). Our Exchange system
> is over 700 gigs and we have SQL servers well over 300 gigs. Even
> with a DS3 we're looking at several hours to replicate (our
> replication site is 1000 miles away in a branch office).
> EMC then came back with an incremental restore option that was
> basically a log file rollup. Essentially the same thing as a manual
> Exchange or SQL database restore. EMC just didn't offer anything
> above what manual steps are required to restore databases. This may
> not be an issue if you're only doing local snapshots. Both EMC and
> NetApp require about the same amount of overhead for a LUN snapshot.
> However, NetApp has just announced improvements to their LUN snapshots
> that require less than 100% LUN overhead.
> With NetApp's SnapManager for Exchange and SQL, I can perform an
> incremental restore from my disaster site directly to my production
> SQL databases or Exchange datastores without stopping services,
> rebooting servers, and without user interruption. We internally setup
> a FAS system in both locations and performed live tests with test
> data. I can literally move to my disaster site, make as many changes
> as I want, replicate back only the changed blocks of data back to my
> production system and be working again in only minutes above the time
> it takes to replicate the data back. And since NetApp does everything
> on a true changed block basis, it takes me only minutes to recover
> changes rather than hours or days to bring over the entire database.
> The trade-off? NetApp costs twice as much as EMC. NetApp may make you
> install a few more apps and administrativly it may not be as
> centralized but we choose NetApp simply because it will allow us to
> work with our applications better than EMC.
> EMC is the monster of SAN's and maybe a Symetrics with SRDF might have
> worked better but that was getting out of our comfort level for
> administration and I don't think they have any different support for
> enterprise applications.
> Hope this helps,
> JT
supporting MS SQL 2000. If so, what's your opinion of one versus the
other?
We're currently using a netapp f825c and are wondering how EMC
compares.
Tom Chute
do you mean network appliance "NAS" ?
Greg Jackson
PDX, Oregon
|||FYI: Yes, I do mean SAN. We're using a fiber channel to connect an
825c to an MS SQL Server. We have a single database split across two
filer heads.
|||No, I mean SAN. We're using a fiber connection to connect a SQL Server
to an 825 cluster. We have a single database split across two filer
heads.
The problem is that we've outgrown the 825c and need to upgrade. I like
Netapp, but my management wants me to look at EMC. I have no experience
w/ EMC, and was wondering if anyone out there has. If they have, what
was their opinion of dealing w/ Netapp and using a Netapp SAN V's EMC.
Tom C.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||tom_chute01@.yahoo.com (Tom Chute) wrote in message news:<b5d5c748.0410081554.41c2fb84@.posting.google. com>...
> FYI: Yes, I do mean SAN. We're using a fiber channel to connect an
> 825c to an MS SQL Server. We have a single database split across two
> filer heads.
Tom,
I just finished a very lengthy trial of NetApp FAS940's and EMC
CX700's. From a LUN performance perspective, EMC just edged out
NetApp mainly due to EMC's 8 GB of cache. Administratively, I liked
EMC better as they have a built in administrative console (Java based)
to manage multiple EMC systems and all the their functions from one
console. As you probably know, NetApp requires a different
application for just about everything they do.
Where NetApp pulls ahead is in the application support and replication
arenas. EMC does a bad job of managing Exchange and SQL replication
and snapshots. One of our main purposes for going with a large SAN
environment was for disaster recovery. The big question we had for
EMC is how do they bring back changed SQL and Exchange data from a
disaster site once the disaster is over? Their first response was to
bring over the entire database (SQL or Exchange). Our Exchange system
is over 700 gigs and we have SQL servers well over 300 gigs. Even
with a DS3 we're looking at several hours to replicate (our
replication site is 1000 miles away in a branch office).
EMC then came back with an incremental restore option that was
basically a log file rollup. Essentially the same thing as a manual
Exchange or SQL database restore. EMC just didn't offer anything
above what manual steps are required to restore databases. This may
not be an issue if you're only doing local snapshots. Both EMC and
NetApp require about the same amount of overhead for a LUN snapshot.
However, NetApp has just announced improvements to their LUN snapshots
that require less than 100% LUN overhead.
With NetApp's SnapManager for Exchange and SQL, I can perform an
incremental restore from my disaster site directly to my production
SQL databases or Exchange datastores without stopping services,
rebooting servers, and without user interruption. We internally setup
a FAS system in both locations and performed live tests with test
data. I can literally move to my disaster site, make as many changes
as I want, replicate back only the changed blocks of data back to my
production system and be working again in only minutes above the time
it takes to replicate the data back. And since NetApp does everything
on a true changed block basis, it takes me only minutes to recover
changes rather than hours or days to bring over the entire database.
The trade-off? NetApp costs twice as much as EMC. NetApp may make you
install a few more apps and administrativly it may not be as
centralized but we choose NetApp simply because it will allow us to
work with our applications better than EMC.
EMC is the monster of SAN's and maybe a Symetrics with SRDF might have
worked better but that was getting out of our comfort level for
administration and I don't think they have any different support for
enterprise applications.
Hope this helps,
JT
|||Hi
We are running EMC Symmetrics with SRDF (going A-SRDF as soon as we can) to
a remote site over 1Gb fiber. Pushing 0.5Tb an hour, capable of 19Tb an
hour. 128GB on the Cache Controllers.
Big environment, but we just have to have 99.999 uptime.
Once you start to look at large SAN's, 'go big or go home'.
Photons, Clarions, DMX's and local storage are being phased out and we will
then only be running a dozen EMC's.
We are happy and won't consider anything else.
Cheers
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"JT Johnson" <jtjohnson@.faegre.com> wrote in message
news:b09ab426.0410110924.27bd276c@.posting.google.c om...
> tom_chute01@.yahoo.com (Tom Chute) wrote in message
news:<b5d5c748.0410081554.41c2fb84@.posting.google. com>...
> Tom,
> I just finished a very lengthy trial of NetApp FAS940's and EMC
> CX700's. From a LUN performance perspective, EMC just edged out
> NetApp mainly due to EMC's 8 GB of cache. Administratively, I liked
> EMC better as they have a built in administrative console (Java based)
> to manage multiple EMC systems and all the their functions from one
> console. As you probably know, NetApp requires a different
> application for just about everything they do.
> Where NetApp pulls ahead is in the application support and replication
> arenas. EMC does a bad job of managing Exchange and SQL replication
> and snapshots. One of our main purposes for going with a large SAN
> environment was for disaster recovery. The big question we had for
> EMC is how do they bring back changed SQL and Exchange data from a
> disaster site once the disaster is over? Their first response was to
> bring over the entire database (SQL or Exchange). Our Exchange system
> is over 700 gigs and we have SQL servers well over 300 gigs. Even
> with a DS3 we're looking at several hours to replicate (our
> replication site is 1000 miles away in a branch office).
> EMC then came back with an incremental restore option that was
> basically a log file rollup. Essentially the same thing as a manual
> Exchange or SQL database restore. EMC just didn't offer anything
> above what manual steps are required to restore databases. This may
> not be an issue if you're only doing local snapshots. Both EMC and
> NetApp require about the same amount of overhead for a LUN snapshot.
> However, NetApp has just announced improvements to their LUN snapshots
> that require less than 100% LUN overhead.
> With NetApp's SnapManager for Exchange and SQL, I can perform an
> incremental restore from my disaster site directly to my production
> SQL databases or Exchange datastores without stopping services,
> rebooting servers, and without user interruption. We internally setup
> a FAS system in both locations and performed live tests with test
> data. I can literally move to my disaster site, make as many changes
> as I want, replicate back only the changed blocks of data back to my
> production system and be working again in only minutes above the time
> it takes to replicate the data back. And since NetApp does everything
> on a true changed block basis, it takes me only minutes to recover
> changes rather than hours or days to bring over the entire database.
> The trade-off? NetApp costs twice as much as EMC. NetApp may make you
> install a few more apps and administrativly it may not be as
> centralized but we choose NetApp simply because it will allow us to
> work with our applications better than EMC.
> EMC is the monster of SAN's and maybe a Symetrics with SRDF might have
> worked better but that was getting out of our comfort level for
> administration and I don't think they have any different support for
> enterprise applications.
> Hope this helps,
> JT
Network Appliance VS EMC
Hi,
We are deciding whether or not to buy a FA270 NetApp filer. Do you guys have
experience using this filer in the past and how does it rate against DELL
EMC CX600? I would just like to have some non biased opinion about both of
the products.
Thanks,
ShivaHi
For general background information you may want to look at:
http://support.microsoft.com/default.aspx?scid=304261
and
http://www.perftuning.com/pdf/MSSqlSAN.pdf
The SAN should out perform the NAS, therefore if this is the main choice
criteria, then the SAN is the one to opt for.
Whatever option you choose you should carry out stress testing, possibly
using the SQLIOStress utilty
http://support.microsoft.com/default.aspx?scid=kb;en-us;231619
John
"Shiva" wrote:
> Hi,
> We are deciding whether or not to buy a FA270 NetApp filer. Do you guys have
> experience using this filer in the past and how does it rate against DELL
> EMC CX600? I would just like to have some non biased opinion about both of
> the products.
> Thanks,
> Shiva
>
>
We are deciding whether or not to buy a FA270 NetApp filer. Do you guys have
experience using this filer in the past and how does it rate against DELL
EMC CX600? I would just like to have some non biased opinion about both of
the products.
Thanks,
ShivaHi
For general background information you may want to look at:
http://support.microsoft.com/default.aspx?scid=304261
and
http://www.perftuning.com/pdf/MSSqlSAN.pdf
The SAN should out perform the NAS, therefore if this is the main choice
criteria, then the SAN is the one to opt for.
Whatever option you choose you should carry out stress testing, possibly
using the SQLIOStress utilty
http://support.microsoft.com/default.aspx?scid=kb;en-us;231619
John
"Shiva" wrote:
> Hi,
> We are deciding whether or not to buy a FA270 NetApp filer. Do you guys have
> experience using this filer in the past and how does it rate against DELL
> EMC CX600? I would just like to have some non biased opinion about both of
> the products.
> Thanks,
> Shiva
>
>
Network Appliance VS EMC
Hi,
We are deciding whether or not to buy a FA270 NetApp filer. Do you guys have
experience using this filer in the past and how does it rate against DELL
EMC CX600? I would just like to have some non biased opinion about both of
the products.
Thanks,
ShivaHi
For general background information you may want to look at:
http://support.microsoft.com/default.aspx?scid=304261
and
http://www.perftuning.com/pdf/MSSqlSAN.pdf
The SAN should out perform the NAS, therefore if this is the main choice
criteria, then the SAN is the one to opt for.
Whatever option you choose you should carry out stress testing, possibly
using the SQLIOStress utilty
http://support.microsoft.com/defaul...kb;en-us;231619
John
"Shiva" wrote:
> Hi,
> We are deciding whether or not to buy a FA270 NetApp filer. Do you guys ha
ve
> experience using this filer in the past and how does it rate against DELL
> EMC CX600? I would just like to have some non biased opinion about both of
> the products.
> Thanks,
> Shiva
>
>
We are deciding whether or not to buy a FA270 NetApp filer. Do you guys have
experience using this filer in the past and how does it rate against DELL
EMC CX600? I would just like to have some non biased opinion about both of
the products.
Thanks,
ShivaHi
For general background information you may want to look at:
http://support.microsoft.com/default.aspx?scid=304261
and
http://www.perftuning.com/pdf/MSSqlSAN.pdf
The SAN should out perform the NAS, therefore if this is the main choice
criteria, then the SAN is the one to opt for.
Whatever option you choose you should carry out stress testing, possibly
using the SQLIOStress utilty
http://support.microsoft.com/defaul...kb;en-us;231619
John
"Shiva" wrote:
> Hi,
> We are deciding whether or not to buy a FA270 NetApp filer. Do you guys ha
ve
> experience using this filer in the past and how does it rate against DELL
> EMC CX600? I would just like to have some non biased opinion about both of
> the products.
> Thanks,
> Shiva
>
>
Monday, March 26, 2012
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
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
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 i
t
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 SQ
L
> 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...an
d
> 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-...ttached-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:
>
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 i
t
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 SQ
L
> 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...an
d
> 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-...ttached-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:
>
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:
> 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.
> >
> >|||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...
> 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:
>> 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.
>> >
>> >
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:
> 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.
> >
> >|||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...
> 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:
>> 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.
>> >
>> >
NetApp filers with SQL
I wanted to pose the question out there, are NetApp filers, connected via
iSCSI, supported as a storage device for a SQL 2000 database?
If yes/no, does someone have recent supporting documentation, within the
last year?
If not, I'd like to find some things to identify (via perfmon/elsewhere), to
backup this information, if possible.
Thank you!
See the article
http://support.microsoft.com/default...&Product=sql2k
then check the WHCL/WHQL to see if the specific NetApps device is on it. If
so, you are good to go.
Hal Berenson
VP, Yukon Readiness
Scalability Experts, Inc.
"Pete" <pbmain@.wideopenwest.com> wrote in message
news:eE4MGuXVEHA.2988@.TK2MSFTNGP10.phx.gbl...
> I wanted to pose the question out there, are NetApp filers, connected via
> iSCSI, supported as a storage device for a SQL 2000 database?
> If yes/no, does someone have recent supporting documentation, within the
> last year?
> If not, I'd like to find some things to identify (via perfmon/elsewhere),
to
> backup this information, if possible.
> Thank you!
>
|||Hi Pete,
This is neto from Brazil.
How are you?
Please see this: http://www.netapp.com/tech_library/3301.html
"Pete" wrote:
> I wanted to pose the question out there, are NetApp filers, connected via
> iSCSI, supported as a storage device for a SQL 2000 database?
> If yes/no, does someone have recent supporting documentation, within the
> last year?
> If not, I'd like to find some things to identify (via perfmon/elsewhere), to
> backup this information, if possible.
> Thank you!
>
>
iSCSI, supported as a storage device for a SQL 2000 database?
If yes/no, does someone have recent supporting documentation, within the
last year?
If not, I'd like to find some things to identify (via perfmon/elsewhere), to
backup this information, if possible.
Thank you!
See the article
http://support.microsoft.com/default...&Product=sql2k
then check the WHCL/WHQL to see if the specific NetApps device is on it. If
so, you are good to go.
Hal Berenson
VP, Yukon Readiness
Scalability Experts, Inc.
"Pete" <pbmain@.wideopenwest.com> wrote in message
news:eE4MGuXVEHA.2988@.TK2MSFTNGP10.phx.gbl...
> I wanted to pose the question out there, are NetApp filers, connected via
> iSCSI, supported as a storage device for a SQL 2000 database?
> If yes/no, does someone have recent supporting documentation, within the
> last year?
> If not, I'd like to find some things to identify (via perfmon/elsewhere),
to
> backup this information, if possible.
> Thank you!
>
|||Hi Pete,
This is neto from Brazil.
How are you?
Please see this: http://www.netapp.com/tech_library/3301.html
"Pete" wrote:
> I wanted to pose the question out there, are NetApp filers, connected via
> iSCSI, supported as a storage device for a SQL 2000 database?
> If yes/no, does someone have recent supporting documentation, within the
> last year?
> If not, I'd like to find some things to identify (via perfmon/elsewhere), to
> backup this information, if possible.
> Thank you!
>
>
NetApp filers with SQL
I wanted to pose the question out there, are NetApp filers, connected via
iSCSI, supported as a storage device for a SQL 2000 database?
If yes/no, does someone have recent supporting documentation, within the
last year?
If not, I'd like to find some things to identify (via perfmon/elsewhere), to
backup this information, if possible.
Thank you!See the article
http://support.microsoft.com/default.aspx?scid=kb;en-us;304261&Product=sql2k
then check the WHCL/WHQL to see if the specific NetApps device is on it. If
so, you are good to go.
--
Hal Berenson
VP, Yukon Readiness
Scalability Experts, Inc.
"Pete" <pbmain@.wideopenwest.com> wrote in message
news:eE4MGuXVEHA.2988@.TK2MSFTNGP10.phx.gbl...
> I wanted to pose the question out there, are NetApp filers, connected via
> iSCSI, supported as a storage device for a SQL 2000 database?
> If yes/no, does someone have recent supporting documentation, within the
> last year?
> If not, I'd like to find some things to identify (via perfmon/elsewhere),
to
> backup this information, if possible.
> Thank you!
>
iSCSI, supported as a storage device for a SQL 2000 database?
If yes/no, does someone have recent supporting documentation, within the
last year?
If not, I'd like to find some things to identify (via perfmon/elsewhere), to
backup this information, if possible.
Thank you!See the article
http://support.microsoft.com/default.aspx?scid=kb;en-us;304261&Product=sql2k
then check the WHCL/WHQL to see if the specific NetApps device is on it. If
so, you are good to go.
--
Hal Berenson
VP, Yukon Readiness
Scalability Experts, Inc.
"Pete" <pbmain@.wideopenwest.com> wrote in message
news:eE4MGuXVEHA.2988@.TK2MSFTNGP10.phx.gbl...
> I wanted to pose the question out there, are NetApp filers, connected via
> iSCSI, supported as a storage device for a SQL 2000 database?
> If yes/no, does someone have recent supporting documentation, within the
> last year?
> If not, I'd like to find some things to identify (via perfmon/elsewhere),
to
> backup this information, if possible.
> Thank you!
>
NetApp filers with SQL
I wanted to pose the question out there, are NetApp filers, connected via
iSCSI, supported as a storage device for a SQL 2000 database?
If yes/no, does someone have recent supporting documentation, within the
last year?
If not, I'd like to find some things to identify (via perfmon/elsewhere), to
backup this information, if possible.
Thank you!See the article
http://support.microsoft.com/defaul...1&Product=sql2k
then check the WHCL/WHQL to see if the specific NetApps device is on it. If
so, you are good to go.
Hal Berenson
VP, Yukon Readiness
Scalability Experts, Inc.
"Pete" <pbmain@.wideopenwest.com> wrote in message
news:eE4MGuXVEHA.2988@.TK2MSFTNGP10.phx.gbl...
> I wanted to pose the question out there, are NetApp filers, connected via
> iSCSI, supported as a storage device for a SQL 2000 database?
> If yes/no, does someone have recent supporting documentation, within the
> last year?
> If not, I'd like to find some things to identify (via perfmon/elsewhere),
to
> backup this information, if possible.
> Thank you!
>|||Hi Pete,
This is neto from Brazil.
How are you?
Please see this: http://www.netapp.com/tech_library/3301.html
"Pete" wrote:
> I wanted to pose the question out there, are NetApp filers, connected via
> iSCSI, supported as a storage device for a SQL 2000 database?
> If yes/no, does someone have recent supporting documentation, within the
> last year?
> If not, I'd like to find some things to identify (via perfmon/elsewhere),
to
> backup this information, if possible.
> Thank you!
>
>sql
iSCSI, supported as a storage device for a SQL 2000 database?
If yes/no, does someone have recent supporting documentation, within the
last year?
If not, I'd like to find some things to identify (via perfmon/elsewhere), to
backup this information, if possible.
Thank you!See the article
http://support.microsoft.com/defaul...1&Product=sql2k
then check the WHCL/WHQL to see if the specific NetApps device is on it. If
so, you are good to go.
Hal Berenson
VP, Yukon Readiness
Scalability Experts, Inc.
"Pete" <pbmain@.wideopenwest.com> wrote in message
news:eE4MGuXVEHA.2988@.TK2MSFTNGP10.phx.gbl...
> I wanted to pose the question out there, are NetApp filers, connected via
> iSCSI, supported as a storage device for a SQL 2000 database?
> If yes/no, does someone have recent supporting documentation, within the
> last year?
> If not, I'd like to find some things to identify (via perfmon/elsewhere),
to
> backup this information, if possible.
> Thank you!
>|||Hi Pete,
This is neto from Brazil.
How are you?
Please see this: http://www.netapp.com/tech_library/3301.html
"Pete" wrote:
> I wanted to pose the question out there, are NetApp filers, connected via
> iSCSI, supported as a storage device for a SQL 2000 database?
> If yes/no, does someone have recent supporting documentation, within the
> last year?
> If not, I'd like to find some things to identify (via perfmon/elsewhere),
to
> backup this information, if possible.
> Thank you!
>
>sql
NetApp Filers - Does MS support them, and do they work?
I've posed this before, but never seem to get a concrete answer:
1) Is a Network Appliance NetApp 940 Filer connected via a fiber card
running iSCSI supported by MS for SQL 2000 implementations?
2) Does anyone run a similar configuration and run into problems?
Thanks everyone
1) A snip from the KB below
Windows Hardware Quality Lab (WHQL) Qualified Devices
Microsoft Windows servers and networked servers or NAS storage servers that
are Windows Hardware Quality Lab (WHQL) certified automatically meet the
data write ordering and write-through guarantees required to support a SQL
Server storage device. Microsoft supports both application and
storage-related issues in these configurations.
Other Devices
If you use a non-WHQL qualified storage device with SQL Server that supports
the I/O guarantees for transactional database use described in this article,
Microsoft will provide full support for SQL Server and SQL Server-based
applications.
INF: Support for Network Database Files
http://support.microsoft.com/?kbid=304261
You can check the status of the exact model here
http://www.microsoft.com/windows/catalog/server/
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Gary Klohouse" <fastman@.earthlink.net> wrote in message
news:OfDHJUjfEHA.2812@.tk2msftngp13.phx.gbl...
> I've posed this before, but never seem to get a concrete answer:
> 1) Is a Network Appliance NetApp 940 Filer connected via a fiber card
> running iSCSI supported by MS for SQL 2000 implementations?
> 2) Does anyone run a similar configuration and run into problems?
> Thanks everyone
>
|||they are not great with Sequential Reads.
We use a NetApp filer and are not totally satisfied.
we are moving off to a Hitachi SAN.
Cheers,
Greg Jackson
PDX, Oregon
|||What is happen?
"Gary Klohouse" wrote:
> I've posed this before, but never seem to get a concrete answer:
> 1) Is a Network Appliance NetApp 940 Filer connected via a fiber card
> running iSCSI supported by MS for SQL 2000 implementations?
> 2) Does anyone run a similar configuration and run into problems?
> Thanks everyone
>
>
1) Is a Network Appliance NetApp 940 Filer connected via a fiber card
running iSCSI supported by MS for SQL 2000 implementations?
2) Does anyone run a similar configuration and run into problems?
Thanks everyone
1) A snip from the KB below
Windows Hardware Quality Lab (WHQL) Qualified Devices
Microsoft Windows servers and networked servers or NAS storage servers that
are Windows Hardware Quality Lab (WHQL) certified automatically meet the
data write ordering and write-through guarantees required to support a SQL
Server storage device. Microsoft supports both application and
storage-related issues in these configurations.
Other Devices
If you use a non-WHQL qualified storage device with SQL Server that supports
the I/O guarantees for transactional database use described in this article,
Microsoft will provide full support for SQL Server and SQL Server-based
applications.
INF: Support for Network Database Files
http://support.microsoft.com/?kbid=304261
You can check the status of the exact model here
http://www.microsoft.com/windows/catalog/server/
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Gary Klohouse" <fastman@.earthlink.net> wrote in message
news:OfDHJUjfEHA.2812@.tk2msftngp13.phx.gbl...
> I've posed this before, but never seem to get a concrete answer:
> 1) Is a Network Appliance NetApp 940 Filer connected via a fiber card
> running iSCSI supported by MS for SQL 2000 implementations?
> 2) Does anyone run a similar configuration and run into problems?
> Thanks everyone
>
|||they are not great with Sequential Reads.
We use a NetApp filer and are not totally satisfied.
we are moving off to a Hitachi SAN.
Cheers,
Greg Jackson
PDX, Oregon
|||What is happen?
"Gary Klohouse" wrote:
> I've posed this before, but never seem to get a concrete answer:
> 1) Is a Network Appliance NetApp 940 Filer connected via a fiber card
> running iSCSI supported by MS for SQL 2000 implementations?
> 2) Does anyone run a similar configuration and run into problems?
> Thanks everyone
>
>
NetApp Filers - Does MS support them, and do they work?
I've posed this before, but never seem to get a concrete answer:
1) Is a Network Appliance NetApp 940 Filer connected via a fiber card
running iSCSI supported by MS for SQL 2000 implementations?
2) Does anyone run a similar configuration and run into problems?
Thanks everyone1) A snip from the KB below
Windows hardware Quality Lab (WHQL) Qualified Devices
Microsoft Windows servers and networked servers or NAS storage servers that
are Windows hardware Quality Lab (WHQL) certified automatically meet the
data write ordering and write-through guarantees required to support a SQL
Server storage device. Microsoft supports both application and
storage-related issues in these configurations.
Other Devices
If you use a non-WHQL qualified storage device with SQL Server that supports
the I/O guarantees for transactional database use described in this article,
Microsoft will provide full support for SQL Server and SQL Server-based
applications.
INF: Support for Network Database Files
http://support.microsoft.com/?kbid=304261
You can check the status of the exact model here
http://www.microsoft.com/windows/catalog/server/
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Gary Klohouse" <fastman@.earthlink.net> wrote in message
news:OfDHJUjfEHA.2812@.tk2msftngp13.phx.gbl...
> I've posed this before, but never seem to get a concrete answer:
> 1) Is a Network Appliance NetApp 940 Filer connected via a fiber card
> running iSCSI supported by MS for SQL 2000 implementations?
> 2) Does anyone run a similar configuration and run into problems?
> Thanks everyone
>|||they are not great with Sequential Reads.
We use a NetApp filer and are not totally satisfied.
we are moving off to a Hitachi SAN.
Cheers,
Greg Jackson
PDX, Oregon|||What is happen?
"Gary Klohouse" wrote:
> I've posed this before, but never seem to get a concrete answer:
> 1) Is a Network Appliance NetApp 940 Filer connected via a fiber card
> running iSCSI supported by MS for SQL 2000 implementations?
> 2) Does anyone run a similar configuration and run into problems?
> Thanks everyone
>
>
1) Is a Network Appliance NetApp 940 Filer connected via a fiber card
running iSCSI supported by MS for SQL 2000 implementations?
2) Does anyone run a similar configuration and run into problems?
Thanks everyone1) A snip from the KB below
Windows hardware Quality Lab (WHQL) Qualified Devices
Microsoft Windows servers and networked servers or NAS storage servers that
are Windows hardware Quality Lab (WHQL) certified automatically meet the
data write ordering and write-through guarantees required to support a SQL
Server storage device. Microsoft supports both application and
storage-related issues in these configurations.
Other Devices
If you use a non-WHQL qualified storage device with SQL Server that supports
the I/O guarantees for transactional database use described in this article,
Microsoft will provide full support for SQL Server and SQL Server-based
applications.
INF: Support for Network Database Files
http://support.microsoft.com/?kbid=304261
You can check the status of the exact model here
http://www.microsoft.com/windows/catalog/server/
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Gary Klohouse" <fastman@.earthlink.net> wrote in message
news:OfDHJUjfEHA.2812@.tk2msftngp13.phx.gbl...
> I've posed this before, but never seem to get a concrete answer:
> 1) Is a Network Appliance NetApp 940 Filer connected via a fiber card
> running iSCSI supported by MS for SQL 2000 implementations?
> 2) Does anyone run a similar configuration and run into problems?
> Thanks everyone
>|||they are not great with Sequential Reads.
We use a NetApp filer and are not totally satisfied.
we are moving off to a Hitachi SAN.
Cheers,
Greg Jackson
PDX, Oregon|||What is happen?
"Gary Klohouse" wrote:
> I've posed this before, but never seem to get a concrete answer:
> 1) Is a Network Appliance NetApp 940 Filer connected via a fiber card
> running iSCSI supported by MS for SQL 2000 implementations?
> 2) Does anyone run a similar configuration and run into problems?
> Thanks everyone
>
>
NetApp Filers - Does MS support them, and do they work?
I've posed this before, but never seem to get a concrete answer:
1) Is a Network Appliance NetApp 940 Filer connected via a fiber card
running iSCSI supported by MS for SQL 2000 implementations?
2) Does anyone run a similar configuration and run into problems?
Thanks everyone1) A snip from the KB below
Windows Hardware Quality Lab (WHQL) Qualified Devices
Microsoft Windows servers and networked servers or NAS storage servers that
are Windows Hardware Quality Lab (WHQL) certified automatically meet the
data write ordering and write-through guarantees required to support a SQL
Server storage device. Microsoft supports both application and
storage-related issues in these configurations.
Other Devices
If you use a non-WHQL qualified storage device with SQL Server that supports
the I/O guarantees for transactional database use described in this article,
Microsoft will provide full support for SQL Server and SQL Server-based
applications.
INF: Support for Network Database Files
http://support.microsoft.com/?kbid=304261
You can check the status of the exact model here
http://www.microsoft.com/windows/catalog/server/
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Gary Klohouse" <fastman@.earthlink.net> wrote in message
news:OfDHJUjfEHA.2812@.tk2msftngp13.phx.gbl...
> I've posed this before, but never seem to get a concrete answer:
> 1) Is a Network Appliance NetApp 940 Filer connected via a fiber card
> running iSCSI supported by MS for SQL 2000 implementations?
> 2) Does anyone run a similar configuration and run into problems?
> Thanks everyone
>|||they are not great with Sequential Reads.
We use a NetApp filer and are not totally satisfied.
we are moving off to a Hitachi SAN.
Cheers,
Greg Jackson
PDX, Oregon
1) Is a Network Appliance NetApp 940 Filer connected via a fiber card
running iSCSI supported by MS for SQL 2000 implementations?
2) Does anyone run a similar configuration and run into problems?
Thanks everyone1) A snip from the KB below
Windows Hardware Quality Lab (WHQL) Qualified Devices
Microsoft Windows servers and networked servers or NAS storage servers that
are Windows Hardware Quality Lab (WHQL) certified automatically meet the
data write ordering and write-through guarantees required to support a SQL
Server storage device. Microsoft supports both application and
storage-related issues in these configurations.
Other Devices
If you use a non-WHQL qualified storage device with SQL Server that supports
the I/O guarantees for transactional database use described in this article,
Microsoft will provide full support for SQL Server and SQL Server-based
applications.
INF: Support for Network Database Files
http://support.microsoft.com/?kbid=304261
You can check the status of the exact model here
http://www.microsoft.com/windows/catalog/server/
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Gary Klohouse" <fastman@.earthlink.net> wrote in message
news:OfDHJUjfEHA.2812@.tk2msftngp13.phx.gbl...
> I've posed this before, but never seem to get a concrete answer:
> 1) Is a Network Appliance NetApp 940 Filer connected via a fiber card
> running iSCSI supported by MS for SQL 2000 implementations?
> 2) Does anyone run a similar configuration and run into problems?
> Thanks everyone
>|||they are not great with Sequential Reads.
We use a NetApp filer and are not totally satisfied.
we are moving off to a Hitachi SAN.
Cheers,
Greg Jackson
PDX, Oregon
Subscribe to:
Posts (Atom)