Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Getting query progress from SQL Server
Message
De
01/12/2000 10:11:17
 
 
Information générale
Forum:
Microsoft SQL Server
Catégorie:
Autre
Divers
Thread ID:
00446850
Message ID:
00448040
Vues:
14
Chad,

How many customers are you talking about? One thing I do, which sort of breaks the rules is (an HR ap) bring an EE list across the first time I need it. this is a full list, but only includes indentifying fields like Name, SSN, empnum. I index the view on each field and have a ee-lookup for which I use whenever an employee id is needed.

While this breaks the rules a bit, the large amount of times the list is accessed and the ability to do server side sorting and filtering of the list make the initial hit acceptable. OF course, this also will depend on the size of your customer list. Most of our customers will have less than 5000 employees, and bringing over 5 fields from the employee master for 5000 only takes a few seconds.

But, generally yes, the best bet is as you said, with a parameterized view where the user enters some type of business key, like ssn, phone number, account number, etc to get the specific customer. But, the above can work to, just as I said, only do the query once, the first time you need the list.

BOb



>Oklahoma City. We may be calling or have already contacted you regarding coming to help.
>
>
>We have several large processes that currently traverse the tables. Using parameterized remote views. Unless I'm missing something, this is incredibly wrong and should be SQL statements, either in stored procedures or spt from Fox.
>
>btw, one other big question I have is on the main customer table which is large.
>Is the only (good) way to go ahead and parameterize the view and force searches to pull up one customer at a time or is there a good way to "page" say 100 at a time. I've tried FETCHSIZE but it seems to lock the connection and can't update. I'm now using MAXRECORDS and the go bottom button goes to the last of the "page" recordset then increases MAXRECORDS to itself + 100 and re-queries. And yes, I'm embarrassed about that.
>What I would like to find is a way to keep only say 100 at a time locally, not progressively more.
>
>Any advice you have to offer is greatly appreciated.
>I have your book, Client/Server Applications with VFP and SQL Server
>Chad
>
>chad@linville.net
>AOL IM: chad9991
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform