more on parameters...

We have a custom .net webb app front end that uses the SOAP methods for rs.
For reasons that are not important to explain, we have several different
types of parameters..we have a couple that we would like to have the user do
an external search (there are too many values to set the parameter up to run
an sp to display allowable values) so we want to create a 'search' page for
them to narrow down / search and pick an appropriate value. The SP that
supplies the report(s) needs to have a value passed to run the report (we
can't filter after the fact). My question is that no 2 databases (out of 60
+ databases) are going to have the same value(s) for these particular
parameters - but I need to set the parm up to have a default value...I
believe... . Does the default value have to be an allowable value? Or can
you put something in as a place holder or a phrase to look for in code so we
can take the neccessary next step (open search page)?
I hope I am explaining this ok...
Thanks,Its hard to unserstand. In generay you can define any default values for RS
Reports if you like. Same for SP, but I think you should be careful wit
datatype there.
Markus Pöhler
netpoint-edv gmbh
Germany
"Myles" wrote:
> We have a custom .net webb app front end that uses the SOAP methods for rs.
> For reasons that are not important to explain, we have several different
> types of parameters..we have a couple that we would like to have the user do
> an external search (there are too many values to set the parameter up to run
> an sp to display allowable values) so we want to create a 'search' page for
> them to narrow down / search and pick an appropriate value. The SP that
> supplies the report(s) needs to have a value passed to run the report (we
> can't filter after the fact). My question is that no 2 databases (out of 60
> + databases) are going to have the same value(s) for these particular
> parameters - but I need to set the parm up to have a default value...I
> believe... . Does the default value have to be an allowable value? Or can
> you put something in as a place holder or a phrase to look for in code so we
> can take the neccessary next step (open search page)?
> I hope I am explaining this ok...
>
> Thanks,

monitoring sql server 2000 for problems

I've developed and am deploying a very important enterprise wide app for a
client. This app controls virtually everything the client does, and has
been thoroughly tested. However, I am a bit concerned about sql server
2000.
I noticed just the other day - still testing - that the server, when opened
in EM, said 'suspect'. I had been doing some fooling around and I know what
caused it. But my concern is, how can I monitor the server for this or
other failures to be able to react quickly - with a backup when necessary -
whenever something serious occurs? Is there a way, either inside vb .net or
by other means of continually polling the server for its health?
Thanks for any recommendations.
Regards,
Bernie Yaeger
Start a service application to continously run SELECT
DATABASEPROPERTYEX('pubs', 'Status') and check it's results?
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Try MiniSQLBackup
"Bernie Yaeger" <berniey@.cherwellinc.com> wrote in message
news:WaqAc.39196$0b.10585827@.news4.srv.hcvlny.cv.n et...
> I've developed and am deploying a very important enterprise wide app for a
> client. This app controls virtually everything the client does, and has
> been thoroughly tested. However, I am a bit concerned about sql server
> 2000.
> I noticed just the other day - still testing - that the server, when
opened
> in EM, said 'suspect'. I had been doing some fooling around and I know
what
> caused it. But my concern is, how can I monitor the server for this or
> other failures to be able to react quickly - with a backup when
necessary -
> whenever something serious occurs? Is there a way, either inside vb .net
or
> by other means of continually polling the server for its health?
> Thanks for any recommendations.
> Regards,
> Bernie Yaeger
>

monitoring sql server 2000 for problems

I've developed and am deploying a very important enterprise wide app for a
client. This app controls virtually everything the client does, and has
been thoroughly tested. However, I am a bit concerned about sql server
2000.
I noticed just the other day - still testing - that the server, when opened
in EM, said 'suspect'. I had been doing some fooling around and I know what
caused it. But my concern is, how can I monitor the server for this or
other failures to be able to react quickly - with a backup when necessary -
whenever something serious occurs? Is there a way, either inside vb .net or
by other means of continually polling the server for its health?
Thanks for any recommendations.
Regards,
Bernie YaegerStart a service application to continously run SELECT
DATABASEPROPERTYEX('pubs', 'Status') and check it's results?
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Try MiniSQLBackup
"Bernie Yaeger" <berniey@.cherwellinc.com> wrote in message
news:WaqAc.39196$0b.10585827@.news4.srv.hcvlny.cv.net...
> I've developed and am deploying a very important enterprise wide app for a
> client. This app controls virtually everything the client does, and has
> been thoroughly tested. However, I am a bit concerned about sql server
> 2000.
> I noticed just the other day - still testing - that the server, when
opened
> in EM, said 'suspect'. I had been doing some fooling around and I know
what
> caused it. But my concern is, how can I monitor the server for this or
> other failures to be able to react quickly - with a backup when
necessary -
> whenever something serious occurs? Is there a way, either inside vb .net
or
> by other means of continually polling the server for its health?
> Thanks for any recommendations.
> Regards,
> Bernie Yaeger
>

monitoring sql server 2000 for problems

I've developed and am deploying a very important enterprise wide app for a
client. This app controls virtually everything the client does, and has
been thoroughly tested. However, I am a bit concerned about sql server
2000.
I noticed just the other day - still testing - that the server, when opened
in EM, said 'suspect'. I had been doing some fooling around and I know what
caused it. But my concern is, how can I monitor the server for this or
other failures to be able to react quickly - with a backup when necessary -
whenever something serious occurs? Is there a way, either inside vb .net or
by other means of continually polling the server for its health?
Thanks for any recommendations.
Regards,
Bernie YaegerStart a service application to continously run SELECT
DATABASEPROPERTYEX('pubs', 'Status') and check it's results?
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Try MiniSQLBackup
"Bernie Yaeger" <berniey@.cherwellinc.com> wrote in message
news:WaqAc.39196$0b.10585827@.news4.srv.hcvlny.cv.net...
> I've developed and am deploying a very important enterprise wide app for a
> client. This app controls virtually everything the client does, and has
> been thoroughly tested. However, I am a bit concerned about sql server
> 2000.
> I noticed just the other day - still testing - that the server, when
opened
> in EM, said 'suspect'. I had been doing some fooling around and I know
what
> caused it. But my concern is, how can I monitor the server for this or
> other failures to be able to react quickly - with a backup when
necessary -
> whenever something serious occurs? Is there a way, either inside vb .net
or
> by other means of continually polling the server for its health?
> Thanks for any recommendations.
> Regards,
> Bernie Yaeger
>