Should I stick with TSQL or use VB's ADO?

[rlwan]

I have a couple of small projects that will require me to apply simple IF-THEN logic to combine tables & update records. What is a better tool? Create a stored procedure to do this or write some VB code that uses ADO to update? Please forgive my ignorance. I am still relatively new to coding.

 

[balves]

If it's just for you to run, and not a user, why go to the trouble of building a VB program and interface? Just write stored procedures.

 

[Brad123]

I would like to suggest that if this is for a user that you use ADO to call a stored procedure. Stored Procs offer many advantages over writing the code in an app. i.e.

Centralized administration
Faster performance
Improved security
etc...

Hope this helps!!

Brad

 

[stoolpigeon]

You might want to try both. I have apps that I have to run through VB w/recordsets because they take too long to run as stored procedures.
Properly written VB, using ADO can move much of the processing load from the database server to the client.

It really depends on a lot of factors and sometimes I think I know which way will be better and then I find that I was mistaken.

If you have the time, I would try both ways and see what works better for your specific situation. This could be very helpful if similar issues arise down the line.

 

[webuser]

In my opinion, Stored procedures are usually faster b/c the processing is done on the Server. But VB is easier to code, especially for beginners and if the updates you are making are not huge, VB might be a better solution...