Re: Use query or stored procedure
From: J West (jimw_at_fluffypaws.co.uk)
Date: 12/20/04
- Previous message: Alan: "Use query or stored procedure"
- In reply to: Alan: "Use query or stored procedure"
- Next in thread: Marc Scheuner: "Re: Use query or stored procedure"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 20 Dec 2004 07:26:51 -0000
Stord procedures are far more efficient for use with MSSQL than using
embeded SQL (Not so for other databses) the only draw back is version
control becomes more difficult. Also pay careful attention to naming stored
procedures. Use a naming convention like GetTableNameAll, GetTableNameByID,
UpdateTableName, DeleteTableName, etc..... Where TableName obviously is the
name of the table that is being worked on. Things become a little wooly when
dealing with joins etc... but if you don't do this then it becomes very
difficult to pic the one stored proc out of the hundred or so (For very
large databases) that you need to change.
Regards
James West
"Alan" <NOSPAMalan_pltse@yahoo.com.au> wrote in message
news:41c6189c@newsgroups.borland.com...
>I am learning to use SQL Server and TADO.
> I am going to write a small application to manage the data of membership,
> which component is better to use if I add a new member to the table
> Membership ?
>
> Should I use the TADOQuery to embed the SQL statement like:
> INSERT INTO Membership values (......)
>
> OR write a stored procedure in SQL Server and pass the parameters to it ?
>
>
- Previous message: Alan: "Use query or stored procedure"
- In reply to: Alan: "Use query or stored procedure"
- Next in thread: Marc Scheuner: "Re: Use query or stored procedure"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
