July 17, 2018 at 6:07 pm
ETL jobs which are reading from remote mainframe database and writing to SQL server database on daily basis. Those queries are running very slow these days. I try to create the trace using SQL server profiler and ran tuning using Database Engine Tuning advisor. Tuning advisor suggested to create around 290 indexes for 30 tables. I gave this recommendation to my boss. His immediate question was "why our weekly index rebuild maintenance job not taking care this indexing ? i was not having any answer to convince him. Please advise if anyone has suggestion.
July 17, 2018 at 6:33 pm
saptek9 - Tuesday, July 17, 2018 6:07 PMETL jobs which are reading from remote mainframe database and writing to SQL server database on daily basis. Those queries are running very slow these days. I try to create the trace using SQL server profiler and ran tuning using Database Engine Tuning advisor. Tuning advisor suggested to create around 290 indexes for 30 tables. I gave this recommendation to my boss. His immediate question was "why our weekly index rebuild maintenance job not taking care this indexing ? i was not having any answer to convince him. Please advise if anyone has suggestion.
Index maintenance won't create indexes if they are needed. And the Database Tuning Advisor gives inappropriate recommendations a lot/most of the time.
Look at your query stats and query plans. Find what's running the worst most often and start tuning the queries.
Start running some of the stored procedures out on the internet that can help identify issues with your instance. The first one I thought of is sp_Blitz:
sp_Blitz
Sue
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply