Re: Error in post with ADOSQLServer
- From: "Guillem" <guillemvicens-nospam@xxxxxxxxxxxxxxxxxx>
- Date: Mon, 30 May 2005 14:30:05 +0200
Hi,
In a table with over 60000 records? You bet it :)
As a matter of fact it's *always* better to have a primary key that helps
you to:
- search faster, as it is also an index
- identify any record without error possibility, which allows you to never
duplicate (your table should be in 3FN at least)
- update exactly what you need to update, as well as any other operation
like inserts, deletes and modifyings
- in other words, help you avoiding a lot of integrity problems
--
Best regards :)
Guillem Vicens
Dep. informática Green Service SA
www.clubgreenoasis.com
--
In order to send me a mail, remove the -nospam
"Sergio Pottstock" <pttk@xxxxxxx> escribió en el mensaje
news:4299f09a@xxxxxxxxxxxxxxxxxxxxxxxxx
> Thank
>
> That is correct!!!, my table dont have any key.
>
> Allway need primary key for update record?
>
> PTTK
>
.
- Follow-Ups:
- Re: Error in post with ADOSQLServer
- From: Sergio Pottstock
- Re: Error in post with ADOSQLServer
- References:
- Error in post with ADOSQLServer
- From: Sergio Pottstock
- Re: Error in post with ADOSQLServer
- From: Kevin Frevert
- Re: Error in post with ADOSQLServer
- From: Sergio Pottstock
- Re: Error in post with ADOSQLServer
- From: Del M
- Re: Error in post with ADOSQLServer
- From: Sergio Pottstock
- Error in post with ADOSQLServer
- Prev by Date: Re: LoadFromFile load error!
- Next by Date: Re: How to use Seek method......
- Previous by thread: Re: Error in post with ADOSQLServer
- Next by thread: Re: Error in post with ADOSQLServer
- Index(es):
Relevant Pages
|