any tips for testing a san?

we finally got our san going here on a test db server.
any tips on testing it?
old disks are raid 5, san is configured raid 5.
so far i've moved some db's data and log files to the san. no problems.
changed the backups to point to the san.
saw significant improvements in backup times.
no improvement on full dbreindex.
nearly all of my databases are small (50mb to 500mb) which sort of
prevents large scale testing. i've got one 5gb db that i'll move over
(should be able to get some good read tests from it). i've also got a
sql stress test tool that i downloaded from somewhere (forget the name
of it though) that inserts millions of records and then reads them.
any other ideas or things to watch out for?when we first implemented SAN we were told to limit size
of individual files to 40gb, since then we have made sure
to set maximum growth of data / log files to 40gb, and add
additional files as needed. I am not sure if this is the
limit of SAN or Windows operating system or sql server.
Out experience is that if you have very large files then
you may have issues restoring them.
We never had any significant issues with SAN, and I am
glad that burden of managing 30+ spindles and few disk
cages is off my shoulders.
hth.
>--Original Message--
>we finally got our san going here on a test db server.
>any tips on testing it?
>old disks are raid 5, san is configured raid 5.
>so far i've moved some db's data and log files to the
san. no problems.
>changed the backups to point to the san.
>saw significant improvements in backup times.
>no improvement on full dbreindex.
>nearly all of my databases are small (50mb to 500mb)
which sort of
>prevents large scale testing. i've got one 5gb db that
i'll move over
>(should be able to get some good read tests from it).
i've also got a
>sql stress test tool that i downloaded from somewhere
(forget the name
>of it though) that inserts millions of records and then
reads them.
>any other ideas or things to watch out for?
>
>.
>

Any documentation anywhere on vs.net 2005 + report services

Well, it finally arrived, my eval version of vs.net 2005...I was so
excited, I think I really must 'get a life'...
Anyway, I recall on here mention that in vs.net 2005 you get more
control over the parameter area....can anyone point me to any
documentation on how vs.net allows more control of reports than 2003?
Did anyone write something about it somewhere?
Thanks
Peter Nolan
www.peternolan.comYou are saying vs.net 2005. vs.net is not Reporting Service. VS 2005 comes
with 2 controls. A winform control and a webform control. If you have your
own application that is integrating with RS then these controls are great.
The controls work in local mode (render without a server) and server mode.
In server mode the server must be running RS 2005, it does not work with RS
2000.
It sounds like you are using Report Manager for your portal to the reports
(versus creating your own app that interacts with the user). If so, then VS
2005 does not provide anything of use to you. You need to upgrade to RS 2005
to see any improvement. As far as more control over the parameter area. RS
2005 has a calendar date picker and it support multi-selection parameters.
Two major improvements.
RS 2005 is faster and also has support for end user sorting.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Peter Nolan" <peter@.peternolan.com> wrote in message
news:1141230819.293974.223770@.u72g2000cwu.googlegroups.com...
> Well, it finally arrived, my eval version of vs.net 2005...I was so
> excited, I think I really must 'get a life'...
> Anyway, I recall on here mention that in vs.net 2005 you get more
> control over the parameter area....can anyone point me to any
> documentation on how vs.net allows more control of reports than 2003?
> Did anyone write something about it somewhere?
> Thanks
> Peter Nolan
> www.peternolan.com
>|||Hi Bruce,
yes, I mean vs.net 2005...I also have sql server 2005.....I have been
going through the 'upgrade' process from sql server 2000 + RS and
vs.net 2003. We are playing around with all the 2005 stuff and
integrating dundas chart controls.
We are building a product based on all the MSFT technology stack (music
to your eyes I am sure)...and we are trying to make it the very best we
can on all 2005 stuff.
We want to integrate it into dotnetnuke in the future but it looks like
it is a bit of work to do and we decided for version 1.0 we would go
with the out of the box report manager.
So currently, we want the 'best result' we can get with vs.net 2005 and
sql server 2005...sounds to me like we can't do any more with the
webform and we might just have wait until version 1.1 and we get it
into the dot net nuke portal...
This sound correct to you?
Best Regards
Peter
www.peternolan.com|||If you want your own frontend then look at the new webform controls that
come with VS 2005, they work with RS 2005.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Peter Nolan" <peter@.peternolan.com> wrote in message
news:1141333522.027909.311300@.j33g2000cwa.googlegroups.com...
> Hi Bruce,
> yes, I mean vs.net 2005...I also have sql server 2005.....I have been
> going through the 'upgrade' process from sql server 2000 + RS and
> vs.net 2003. We are playing around with all the 2005 stuff and
> integrating dundas chart controls.
> We are building a product based on all the MSFT technology stack (music
> to your eyes I am sure)...and we are trying to make it the very best we
> can on all 2005 stuff.
> We want to integrate it into dotnetnuke in the future but it looks like
> it is a bit of work to do and we decided for version 1.0 we would go
> with the out of the box report manager.
> So currently, we want the 'best result' we can get with vs.net 2005 and
> sql server 2005...sounds to me like we can't do any more with the
> webform and we might just have wait until version 1.1 and we get it
> into the dot net nuke portal...
> This sound correct to you?
> Best Regards
> Peter
> www.peternolan.com
>|||Hi Bruce,
we'd like out own but we see it is a lot of work to do....I bought the
hitch-hikers book and I agree with their opinion...too hard...
I also think someone else is going to do it and charge a reasonable fee
for it...failing that, we will put it into dotnetnuke....we don't
want to have to write an application just to present our
reports...there's too much to write...we like DNN as it now has
windows authentication, lots of modules, a developer ecosystem
happening, the source code is availble, and it's the right price.. LOL!
Personally, I'd love to see MSFT and DNN core team work together to
develop a really, really good suite of modules for Report Services.
There is one out there already and I am using it...but I think someone
actually spending a good amount of time and effort on it might be
useful...perhaps I should do that myself!!! Maybe we can use the new
webform inside DNN.....sounds like Version 1.1 to me...and we are
still working on getting V 1.0 out the door...
Best Regards
Peter
www.peternolan.com