Mike Yearwood
Toronto, Ontario, Canada
General information
Category:
Databases,Tables, Views, Indexing and SQL syntax
That'll work, but bear in mind you'll need a new set of indexes per office. You'll pay for that later in that it will take more time to reindex/re-create indexes, and record updates will have to updated those indexes.
SET KEY would be better for this scenario. Views/SPT would be ideal. I don't see how you not knowing SET KEY relates to the budget. You bill your client for time you spend learning?
>It should be set index list based on the office selected.
>
>>>
>>>Unfortunately at this time all we really have budget for is a quick and dirty solution using filtered indexes and changing indexes on the fly.
>>>
>>
>>What do you mean? You're going to create indexes on the fly? That's dirty and definitely not quick. SET KEY will knock your socks off!
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only