Re: Give me solution

Adi,

It depends. Yes, it should be acceptable, but that would lead to other
questions like what is the user going to do with the first record in the
table? Without a where clause, how do you know that is the record the
client wants?

The basics of Client/Server database development is only select the data the
user requests. When you search Google, do you think they issue a 'Select
TOP 1 * From GoogleDatabase' every time the Search button is clicked? No,
Google forces you to enter something, they take that 'something', parse it,
build a search criteria for their database and return you the results.
That's how it is done (in a most basic sense).

As far as normalization, that is a subject of a number of books (way to much
to get into here). You can start with MSSQL's Books Online. It has a
section on normalization and you can find a lot of resources on the web
(Google is your friend :)

Good luck,
krf

"Bpk. Adi Wira Kusuma" <adi_wira_kusuma@xxxxxxxxxxxx> wrote in message
news:43132a9e@xxxxxxxxxxxxxxxxxxxxxxxxx
> When form show, I've executed: SELECT TOP 1 * FROM TDAV. So This can be
> assumed that amount record will surely 1. But it is still slow. And what
is
> the meaning of normalized?
>
>
> "Kevin Frevert" <kevin@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:4313230b$1@xxxxxxxxxxxxxxxxxxxxxxxxx
> > Adi,
> >
> > How many records are you returning to the client? What does the SQL
> look
> > like (how are you returning the data to the client)? Do you really need
> to
> > return all 200 fields? Why does the table have 200 fields? Can the
table
> > be normalized?
> >
> > krf


.

Quantcast