RE: Stored Procedures and when to use them

2006-03-02 Thread Michael T. Tangorre
> From: Mike | NZSolutions Ltd [mailto:[EMAIL PROTECTED] > Is there any advantage having this type of query in a SP over > calling a simple CFC ?? Mike, Stored Procedures were a good choice for me when I was working at a place that had two, top-notch DBAs who could really analyze some of the mo

RE: Stored Procedures and when to use them

2006-03-02 Thread Robertson-Ravo, Neil (RX)
: Martin Thorpe [mailto:[EMAIL PROTECTED] Sent: 02 March 2006 10:49 To: CF-Talk Subject: Re: Stored Procedures and when to use them An example. I had a set of queries to delete an organisation from one table and then all the relative data in the database for that organisation. I wrote it

Re: Stored Procedures and when to use them

2006-03-02 Thread Martin Thorpe
An example. I had a set of queries to delete an organisation from one table and then all the relative data in the database for that organisation. I wrote it originally in CF but it was taking about 2 minutes, and timing out, to procees. After putting the whole lot into a stored proc the execu

RE: Stored Procedures and when to use them

2006-03-02 Thread RADEMAKERS Tanguy
One of the nice things about stored procedures wv. inline sql is that your database can tell you which procs are invalidated by a change to your schema, which can be a big time saver in development. /t ~| Message: http://www.hous

Re: Stored Procedures and when to use them

2006-03-02 Thread John C. Bland II
ike this. > > > > > > -Original Message- > From: John C. Bland II [mailto:[EMAIL PROTECTED] > Sent: 02 March 2006 10:15 > To: CF-Talk > Subject: Re: Stored Procedures and when to use them > > Sprocs are faster if you are doing multiple things in 1 call

RE: Stored Procedures and when to use them

2006-03-02 Thread Robertson-Ravo, Neil (RX)
be your vice as CF will choke on large sets like this. -Original Message- From: John C. Bland II [mailto:[EMAIL PROTECTED] Sent: 02 March 2006 10:15 To: CF-Talk Subject: Re: Stored Procedures and when to use them Sprocs are faster if you are doing multiple things in 1 call. The idea

Re: Stored Procedures and when to use them

2006-03-02 Thread John C. Bland II
Sprocs are faster if you are doing multiple things in 1 call. The idea is you are in the database already so go ahead and let the database do what it does best. For general selects, inserts, updates, and deletes keeping it in the app is fine. It does come down to personal preference though. I used

RE: Stored Procedures and when to use them

2006-03-02 Thread Robertson-Ravo, Neil (RX)
No benefit really. Not in this instance. -Original Message- From: Mike | NZSolutions Ltd [mailto:[EMAIL PROTECTED] Sent: 01 March 2006 21:39 To: CF-Talk Subject: Stored Procedures and when to use them Hi guys, I am just getting my head around stored procedures in SQL Server. One of th

Re: Stored Procedures and when to use them

2006-03-01 Thread Will Tomlinson
>Hi guys, > >I am just getting my head around stored procedures in SQL Server. One of >the things I am trying to understand is when I should be using them. I can't stand them myself. Used them in an application just for *hits'n'giggles, then needed to go back and make a few changes later. It was

Re: Stored Procedures and when to use them

2006-03-01 Thread Mike Little
to add to this question (and secretly bump it to the top of the list), how does the newID() function work in this case? mike ~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:233827 Archives: http://www.houseoffusion.c