Re: time out (used to work fine and was indexed)
From: Andrew J. Kelly (sqlmvpnooospam_at_shadhawk.com)
Date: 05/26/04
- Next message: Jim Abel: "Re: Forcing a Trigger after a insert of several records"
- Previous message: Aaron Bertrand - MVP: "Re: Stored Procedure for Searching Table"
- In reply to: mike: "Re: time out (used to work fine and was indexed)"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 26 May 2004 16:34:15 -0400
Why would you want a table with 300,000 rows to have no indexes on it?
-- Andrew J. Kelly SQL Server MVP "mike" <anonymous@discussions.microsoft.com> wrote in message news:12d2201c44352$18f4c450$a301280a@phx.gbl... > Aaron, thanks for offering. I just ran the view again > after removing all but the one product our company sells > that I'm interested in. That reduced the size of the main > table I'm working with (which is not indexed) to about > 300,000 records and it worked, albeit a little slower than > usual. I don't even think I can adequately explain this at > the moment, so I'll dig a little deeper, see if I can get > it work with all records included, 2M which I'm sure we'll > need to look at sometime soon, and come back with a more > focused question. Thanks!
- Next message: Jim Abel: "Re: Forcing a Trigger after a insert of several records"
- Previous message: Aaron Bertrand - MVP: "Re: Stored Procedure for Searching Table"
- In reply to: mike: "Re: time out (used to work fine and was indexed)"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
