asked on
Hello Experts,
Is there any way that I can determine what fields should be indexed in a specific table, or group of tables, without crawling through the code and analyzing all the queries?
I am specifically concerned with a group of 201 tables that I use to store customer inventory. The tables have names like 0000,0001,0002...0200, and each table, with the identical structure, has about 125 fields.
This table naming convention that I've used, allows me to programmatically create queries and recordsources based upon a specific customers inventory (for example, table [0101], so I can not simply search my code for a specific table name as you would normally do to find all the SQL statements in our code that reference a specific table (this code has matured for more than 10 years, so the variable names used in the code varies depending upon the routine.)
I'm sure there are at least 200 queries and RecordSource statements embedded in my code.
In addition, I likely have a hundred or more queries, that use this data.
Is there any way to determine which fields should be indexed, without crawling through the code and examining every SQL statement and query?
Some of the tables have a hundred thousand records, so performance is a critical concern.
Thanks
In other words, my code may use a variable to represent the table name.
Is there any way that I can determine what fields should be indexed in a specific table, or group of tables, without crawling through the code and analyzing all the queries?
I am specifically concerned with a group of 201 tables that I use to store customer inventory. The tables have names like 0000,0001,0002...0200, and each table, with the identical structure, has about 125 fields.
This table naming convention that I've used, allows me to programmatically create queries and recordsources based upon a specific customers inventory (for example, table [0101], so I can not simply search my code for a specific table name as you would normally do to find all the SQL statements in our code that reference a specific table (this code has matured for more than 10 years, so the variable names used in the code varies depending upon the routine.)
I'm sure there are at least 200 queries and RecordSource statements embedded in my code.
In addition, I likely have a hundred or more queries, that use this data.
Is there any way to determine which fields should be indexed, without crawling through the code and examining every SQL statement and query?
Some of the tables have a hundred thousand records, so performance is a critical concern.
Thanks
In other words, my code may use a variable to represent the table name.
Learn from the best
Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.
Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 5 Comments.
Try for 7 days”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.
Our community of experts have been thoroughly vetted for their expertise and industry experience.
The Fellow title is reserved for select members who demonstrate sustained contributions, industry leadership, and outstanding performance. We will announce the experts being inducted into the Experts Exchange Fellowship during the annual Expert Awards, but unlike other awards, Fellow is a lifelong status. This title may not be given every year if there are no obvious candidates.
The Most Valuable Expert award recognizes technology experts who passionately share their knowledge with the community, demonstrate the core values of this platform, and go the extra mile in all aspects of their contributions. This award is based off of nominations by EE users and experts. Multiple MVEs may be awarded each year.