By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,561 Members | 3,221 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,561 IT Pros & Developers. It's quick & easy.

Do web services make sense for me?

P: n/a
I have an existing ASP/ MSSQL project that we are looking at migrating to
VB.Net (standalone app, not ASP) which will still interact with a single
central SQL server. Because we have a requirement to "filter" data returned
depending on the user's permission to certain classes of data we hava all
access implemented via stored procedures. Another reason for using SPs is
that certain tables have a requirement to keep track of who made changes,
what the change was (old and new data), and when the change happened. Given
these requirements, it appears to me that adding a web service simply
inserts another layer between the user and the database, and one that is
going to require that I define a Command object for each stored procedure
call. Are there advantages that I am not seeing, or am I better off just
having my application create the necessary data objects that directly query
the database?

TIA
Ron L
Nov 21 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
Ron,

In my opinion there is the most important advantage by adding a webservice
is that you can close your database completly for the outside world.

You only give the data that is requested without any connection to that
database.

Or did I understand your question wrong?

Cor
"Ron L" <ro**@bogus.Address.com>
....
I have an existing ASP/ MSSQL project that we are looking at migrating to
VB.Net (standalone app, not ASP) which will still interact with a single
central SQL server. Because we have a requirement to "filter" data
returned depending on the user's permission to certain classes of data we
hava all access implemented via stored procedures. Another reason for
using SPs is that certain tables have a requirement to keep track of who
made changes, what the change was (old and new data), and when the change
happened. Given these requirements, it appears to me that adding a web
service simply inserts another layer between the user and the database, and
one that is going to require that I define a Command object for each stored
procedure call. Are there advantages that I am not seeing, or am I better
off just having my application create the necessary data objects that
directly query the database?

TIA
Ron L

Nov 21 '05 #2

P: n/a
Cor
As far as I can tell, I will still need to give the users access to my
database (at least as far as SQL is concerned), because I have to have the
users accessing it under their own login. This is due to the "filter"
requirement I alluded to. I have a table that effectively reads <username>
can read this class, can create that class, can edit a third class, and
can't even see the remaining classes. Because of this, I have to grant each
user access to the database and use integrated authentication - as far as I
can tell, this means that my Web Services classes will effectively mimic my
SP list. The only thing I can see that it might do is not include any
entries for SPs that general users need to run (administrative SPs). I'm
not sure that the extra layer is worth this minor gain

Thanks for your response.
Ron L
"Cor Ligthert" <no************@planet.nl> wrote in message
news:Ow**************@TK2MSFTNGP14.phx.gbl...
Ron,

In my opinion there is the most important advantage by adding a webservice
is that you can close your database completly for the outside world.

You only give the data that is requested without any connection to that
database.

Or did I understand your question wrong?

Cor
"Ron L" <ro**@bogus.Address.com>
...
I have an existing ASP/ MSSQL project that we are looking at migrating to
VB.Net (standalone app, not ASP) which will still interact with a single
central SQL server. Because we have a requirement to "filter" data
returned depending on the user's permission to certain classes of data we
hava all access implemented via stored procedures. Another reason for
using SPs is that certain tables have a requirement to keep track of who
made changes, what the change was (old and new data), and when the change
happened. Given these requirements, it appears to me that adding a web
service simply inserts another layer between the user and the database,
and one that is going to require that I define a Command object for each
stored procedure call. Are there advantages that I am not seeing, or am I
better off just having my application create the necessary data objects
that directly query the database?

TIA
Ron L


Nov 21 '05 #3

P: n/a
Web Service is one of the way involve your class. You need a class but how
to involve your class it depends on your environment.

http://msdn.microsoft.com/architecture

chanmm

"Ron L" <ro**@bogus.Address.com> wrote in message
news:uu**************@TK2MSFTNGP14.phx.gbl...
Cor
As far as I can tell, I will still need to give the users access to my
database (at least as far as SQL is concerned), because I have to have the
users accessing it under their own login. This is due to the "filter"
requirement I alluded to. I have a table that effectively reads
<username> can read this class, can create that class, can edit a third
class, and can't even see the remaining classes. Because of this, I have
to grant each user access to the database and use integrated
authentication - as far as I can tell, this means that my Web Services
classes will effectively mimic my SP list. The only thing I can see that
it might do is not include any entries for SPs that general users need to
run (administrative SPs). I'm not sure that the extra layer is worth this
minor gain

Thanks for your response.
Ron L
"Cor Ligthert" <no************@planet.nl> wrote in message
news:Ow**************@TK2MSFTNGP14.phx.gbl...
Ron,

In my opinion there is the most important advantage by adding a
webservice is that you can close your database completly for the outside
world.

You only give the data that is requested without any connection to that
database.

Or did I understand your question wrong?

Cor
"Ron L" <ro**@bogus.Address.com>
...
I have an existing ASP/ MSSQL project that we are looking at migrating to
VB.Net (standalone app, not ASP) which will still interact with a single
central SQL server. Because we have a requirement to "filter" data
returned depending on the user's permission to certain classes of data we
hava all access implemented via stored procedures. Another reason for
using SPs is that certain tables have a requirement to keep track of who
made changes, what the change was (old and new data), and when the change
happened. Given these requirements, it appears to me that adding a web
service simply inserts another layer between the user and the database,
and one that is going to require that I define a Command object for each
stored procedure call. Are there advantages that I am not seeing, or am
I better off just having my application create the necessary data objects
that directly query the database?

TIA
Ron L



Nov 21 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.