I have a series of report where ALL 500 of the tables were brought over in the initial building of the reports. The user who built these never got any training. So instead of the reports being efficient they are painfully slow. The problem is we just converted all the reports to the SQL version a much faster reporting database and all the old unneeded tables we are not using or needing came over with the report. We found after mapping the old tables to the new SQL version of the reports made the reports run faster. If we removed the redundant or unused tables from the reports they ran even faster. We want to remove the unused tables.
However when we do this we
1. disconnect the mapped network drive to the report
2. go to the design view of the report
3. click on Verify database under the Database menu.
4. either click with mouse or hold down the Enter key to remove all unnecessary reports
When I notice sometimes ALL 500 tables can be removed in a matter of 2 minutes. Other times the report takes literally an hour plus to remove all the tables. I have watched the Task Managers CPU spike for several seconds from 10% to 100% for every table removed. In some cases the CPU stays spiked at 100% for minutes. Thus causing my removal of the tables to be painfully slow.
Does anyone know what causes this or knows what can be done about it. Please advise. thank you.
When table data gets too large to manage or queries take too long to execute the solution is often to buy bigger hardware or assign more CPUs and memory resources to the machine to solve the problem. However, the best, cheapest and most effective so…
A company’s centralized system that manages user data, security, and distributed resources is often a focus of criminal attention. Active Directory (AD) is no exception. In truth, it’s even more likely to be targeted due to the number of companies …
Using examples as well as descriptions, step through each of the common simple join types, explaining differences in syntax, differences in expected outputs and showing how the queries run along with the actual outputs based upon a simple set of dem…