September 1, 2015 at 9:07 am
Hello,
I might get an assignment of working on mega tables with 10-30 millions records, the original data has no index in it, the raw will be replicated to a staging server for reporting purpose and I work on the staging server.
I am thinking if I should create an index column on the fly when replicating data to the new table on the staging server? will that help in terms of query performance? what is the best practice?
I've noticed if 1 week's data is replicated, the sql job will fail; currently the period is set to 1 day and the job works fine. The number of days will be treaked to get as much data as possible when the job is executed, I am not sure if there is better way to replicate data.
Thank you in advance if you can share your thought on this. Any suggestion is appreciated.
September 1, 2015 at 11:51 am
Maybe
Depends if the index is useful to the query and the query capable of using the index.
Not knowing how you're replicating the data, it's a little hard to suggest alternatives or improvements.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 1, 2015 at 12:12 pm
GilaMonster (9/1/2015)
MaybeDepends if the index is useful to the query and the query capable of using the index.
Not knowing how you're replicating the data, it's a little hard to suggest alternatives or improvements.
Thanks. I will come back here once the assignment is officially on me, by then I will know the current process and maybe apply certain changes on it and hopefully helpful to the query performance.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply