This is interesting - both Kylie and yourself have confirmed what I have had experience - MS SQL's superior Stored procedure language wins out on those who like to put a bit (or a lot) of code in the database engine.
I'm not big on stored procedures, but that is probably because I focus on InterBase and the stored procs are limited. Richard --- Richard Vowles, Solutions Architect, Borland New Zealand email: [EMAIL PROTECTED] phone: +64-9-9184573 cell: +64-21-467747 other: MSN [EMAIL PROTECTED], skype: rvowles blog: http://www.usergroup.org.nz/blogs/selectBlog.html?id=39769 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeremy Coulter Sent: Thursday, 1 June 2006 12:04 a.m. To: 'NZ Borland Developers Group - Delphi List' Subject: RE: [DUG] Why InterBase I used IB for about 6-7 months after going from MSSQL 7(this is like 6 years ago now), and HATED that IB didn't have a nice GUI interface. I didn't like this whole "Domains" thing for variables, although I did see the sense in it after a while and did use them, and REALLY hated having to use some other DLL to get any decent functions to use when doing Stored Procs. When I left that job, after 6mths cos I hated the pace, and got my current role which I have had for 6years now, I went back to MSSQL, and now MSSQL 2005 is out, I REALLY like it ! I guess it's the old story of horses for courses. We do a LOT with stored procs (well not so much me these days) and we are ready to start getting in MSSQL 2k5 soon as we can. _______________________________________________ Delphi mailing list [email protected] http://ns3.123.co.nz/mailman/listinfo/delphi
