Re: Simple Best Practice Question
From: Marek (Marek_at_discussions.microsoft.com)
Date: 10/19/04
- Next message: EBohn: "Poor performance using Set FMTONLY On"
- Previous message: Mingqing Cheng [MSFT]: "RE: IN vs EXISTS vs INNER JOIN"
- In reply to: Uri Dimant: "Re: Simple Best Practice Question"
- Next in thread: Uri Dimant: "Re: Simple Best Practice Question"
- Reply: Uri Dimant: "Re: Simple Best Practice Question"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 19 Oct 2004 06:57:03 -0700
Are there any code examples I can look at? I am unsure how to go about this.
If I want a simple stored procedure to edit a record in a table that
contains 10 columns, but I only need to modify one column, do I use 10
different variables or is there such a thing as optional parameters??
"Uri Dimant" wrote:
> Marek
> In short the answer is Stored Procedures
>
>
> "Marek" <Marek@discussions.microsoft.com> wrote in message
> news:9A9AD8BF-4426-43D6-BD26-65B4FE03162B@microsoft.com...
> > Hi,
> >
> > I am looking for advice on best practice with SQL 2000. I have created a
> > fairly simple database - about 12 tables. I am unsure about the best way
> to
> > build the front end - it is going to be web based. Do I use asp.net code
> to
> > create, edit and delete records or do I use stored procedures?? I have
> > created 12 stored procedures for new records but an unsure on the best way
> to
> > handle edits and deletes.
> >
> > --
> > Many thanks in advance for any assistance
>
>
>
- Next message: EBohn: "Poor performance using Set FMTONLY On"
- Previous message: Mingqing Cheng [MSFT]: "RE: IN vs EXISTS vs INNER JOIN"
- In reply to: Uri Dimant: "Re: Simple Best Practice Question"
- Next in thread: Uri Dimant: "Re: Simple Best Practice Question"
- Reply: Uri Dimant: "Re: Simple Best Practice Question"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
