|
database
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
|
CPUs and 8GB RAM (using about 6.5GB). The statistics that I get when I run it are below. It is not the first time that I ran it so the execution plan already exists and it looks like the data is all in RAM which is fine. It is taking over 7 seconds to run and using about 1/2 sec of CPU time. I'm in Performance Monitor watching the 8 CPUs and none of them are near 100% - the entire CPU of the system gets to about 10-15% while this is running. The hard drives are not the bottleneck - they barely budge during the execution. Any ideas why it might be taking so long? What else should I look at? Thanks, Mark SQL Server parse and compile time: CPU time = 0 ms, elapsed time = 0 ms. (1242 row(s) affected) Table 'Worktable'. Scan count 1239, logical reads 1249, physical reads 0, read-ahead reads 0. Table 'Worktable'. Scan count 1241, logical reads 1249, physical reads 0, read-ahead reads 0. Table 'Worktable'. Scan count 0, logical reads 0, physical reads 0, read-ahead reads 0. Table 'Worktable'. Scan count 0, logical reads 0, physical reads 0, read-ahead reads 0. Table 'tbFirmClient'. Scan count 1, logical reads 18, physical reads 0, read-ahead reads 0. Table 'tbFirm'. Scan count 1, logical reads 2671, physical reads 0, read-ahead reads 0. Table 'tbFirmStatisticSuitability'. Scan count 0, logical reads 0, physical reads 0, read-ahead reads 0. Table 'tbSecurity'. Scan count 0, logical reads 0, physical reads 0, read-ahead reads 0. Table 'tbStatistic'. Scan count 0, logical reads 0, physical reads 0, read-ahead reads 0. Table 'tbSuitabilityStudy'. Scan count 4, logical reads 12, physical reads 0, read-ahead reads 0. Table 'Worktable'. Scan count 0, logical reads 0, physical reads 0, read-ahead reads 0. Table 'Worktable'. Scan count 0, logical reads 0, physical reads 0, read-ahead reads 0. Table 'tbAltpurchpower'. Scan count 784, logical reads 2287, physical reads 0, read-ahead reads 0. Table 'tbFirmScore'. Scan count 1243, logical reads 12644, physical reads 0, read-ahead reads 0. Table 'tbPosition'. Scan count 1243, logical reads 11966, physical reads 0, read-ahead reads 0. Table 'tbAddressPhone'. Scan count 2480, logical reads 12099, physical reads 0, read-ahead reads 0. Table 'tbRegion'. Scan count 1, logical reads 2, physical reads 0, read-ahead reads 0. Table 'tbCountry'. Scan count 1240, logical reads 2480, physical reads 0, read-ahead reads 0. Table 'tbState'. Scan count 824, logical reads 1648, physical reads 0, read-ahead reads 0. Table 'tbCity'. Scan count 1240, logical reads 2487, physical reads 0, read-ahead reads 0. Table 'tbAddress'. Scan count 1242, logical reads 15080, physical reads 0, read-ahead reads 0. Table 'tbTurnoverRating'. Scan count 1, logical reads 2, physical reads 0, read-ahead reads 0. Table '#04BDFF0F'. Scan count 0, logical reads 0, physical reads 0, read-ahead reads 0. Table 'tbIRXGroup'. Scan count 1, logical reads 2, physical reads 0, read-ahead reads 0. Table 'tbIRXLogin'. Scan count 1, logical reads 2, physical reads 0, read-ahead reads 0. Table 'tbFirmType'. Scan count 2, logical reads 82, physical reads 0, read-ahead reads 0. Table 'tbInvestmentStyle'. Scan count 2, logical reads 4, physical reads 0, read-ahead reads 0. Table 'tbMediaFocus'. Scan count 1, logical reads 2, physical reads 0, read-ahead reads 0. Table 'tbMediaFrequency'. Scan count 1, logical reads 2, physical reads 0, read-ahead reads 0. Table 'tbFirmSuperType'. Scan count 1, logical reads 2, physical reads 0, read-ahead reads 0. SQL Server Execution Times: CPU time = 469 ms, elapsed time = 7442 ms. Are you sure it is using the same query plan? It sounds like the extra time
may be compile time. You are certainly joining lots of tables and to generate a plan like that can take a while. Also what is your MAXDOP set to? Try setting it to 1 or adding a hint in the query to set it to 1 and see if that makes a difference. -- Show quoteAndrew J. Kelly SQL MVP "MarkR" <Ma***@discussions.microsoft.com> wrote in message news:BD0392B0-A37E-477A-A62F-D7727296054E@microsoft.com... >I have a fairly complex SELECT statement. It is running on a server with 8 > CPUs and 8GB RAM (using about 6.5GB). The statistics that I get when I > run > it are below. It is not the first time that I ran it so the execution > plan > already exists and it looks like the data is all in RAM which is fine. > > It is taking over 7 seconds to run and using about 1/2 sec of CPU time. > I'm > in Performance Monitor watching the 8 CPUs and none of them are near > 100% - > the entire CPU of the system gets to about 10-15% while this is running. > The > hard drives are not the bottleneck - they barely budge during the > execution. > Any ideas why it might be taking so long? What else should I look at? > > Thanks, > Mark > > > SQL Server parse and compile time: > CPU time = 0 ms, elapsed time = 0 ms. > > (1242 row(s) affected) > > Table 'Worktable'. Scan count 1239, logical reads 1249, physical reads 0, > read-ahead reads 0. > Table 'Worktable'. Scan count 1241, logical reads 1249, physical reads 0, > read-ahead reads 0. > Table 'Worktable'. Scan count 0, logical reads 0, physical reads 0, > read-ahead reads 0. > Table 'Worktable'. Scan count 0, logical reads 0, physical reads 0, > read-ahead reads 0. > Table 'tbFirmClient'. Scan count 1, logical reads 18, physical reads 0, > read-ahead reads 0. > Table 'tbFirm'. Scan count 1, logical reads 2671, physical reads 0, > read-ahead reads 0. > Table 'tbFirmStatisticSuitability'. Scan count 0, logical reads 0, > physical > reads 0, read-ahead reads 0. > Table 'tbSecurity'. Scan count 0, logical reads 0, physical reads 0, > read-ahead reads 0. > Table 'tbStatistic'. Scan count 0, logical reads 0, physical reads 0, > read-ahead reads 0. > Table 'tbSuitabilityStudy'. Scan count 4, logical reads 12, physical reads > 0, read-ahead reads 0. > Table 'Worktable'. Scan count 0, logical reads 0, physical reads 0, > read-ahead reads 0. > Table 'Worktable'. Scan count 0, logical reads 0, physical reads 0, > read-ahead reads 0. > Table 'tbAltpurchpower'. Scan count 784, logical reads 2287, physical > reads > 0, read-ahead reads 0. > Table 'tbFirmScore'. Scan count 1243, logical reads 12644, physical reads > 0, > read-ahead reads 0. > Table 'tbPosition'. Scan count 1243, logical reads 11966, physical reads > 0, > read-ahead reads 0. > Table 'tbAddressPhone'. Scan count 2480, logical reads 12099, physical > reads > 0, read-ahead reads 0. > Table 'tbRegion'. Scan count 1, logical reads 2, physical reads 0, > read-ahead reads 0. > Table 'tbCountry'. Scan count 1240, logical reads 2480, physical reads 0, > read-ahead reads 0. > Table 'tbState'. Scan count 824, logical reads 1648, physical reads 0, > read-ahead reads 0. > Table 'tbCity'. Scan count 1240, logical reads 2487, physical reads 0, > read-ahead reads 0. > Table 'tbAddress'. Scan count 1242, logical reads 15080, physical reads 0, > read-ahead reads 0. > Table 'tbTurnoverRating'. Scan count 1, logical reads 2, physical reads 0, > read-ahead reads 0. > Table '#04BDFF0F'. Scan count 0, logical reads 0, physical reads 0, > read-ahead reads 0. > Table 'tbIRXGroup'. Scan count 1, logical reads 2, physical reads 0, > read-ahead reads 0. > Table 'tbIRXLogin'. Scan count 1, logical reads 2, physical reads 0, > read-ahead reads 0. > Table 'tbFirmType'. Scan count 2, logical reads 82, physical reads 0, > read-ahead reads 0. > Table 'tbInvestmentStyle'. Scan count 2, logical reads 4, physical reads > 0, > read-ahead reads 0. > Table 'tbMediaFocus'. Scan count 1, logical reads 2, physical reads 0, > read-ahead reads 0. > Table 'tbMediaFrequency'. Scan count 1, logical reads 2, physical reads 0, > read-ahead reads 0. > Table 'tbFirmSuperType'. Scan count 1, logical reads 2, physical reads 0, > read-ahead reads 0. > > SQL Server Execution Times: > CPU time = 469 ms, elapsed time = 7442 ms. > I'm not sure it is using the same query plan. I am assuming it is because
SQL Server parse and compile time: CPU time = 0 ms, elapsed time = 0 ms. .... but I could be wrong. I added a 'maxdop 1' hint which made no difference. Mark Show quote "Andrew J. Kelly" wrote: > Are you sure it is using the same query plan? It sounds like the extra time > may be compile time. You are certainly joining lots of tables and to > generate a plan like that can take a while. Also what is your MAXDOP set to? > Try setting it to 1 or adding a hint in the query to set it to 1 and see if > that makes a difference. > > -- > Andrew J. Kelly SQL MVP > > "MarkR" <Ma***@discussions.microsoft.com> wrote in message > news:BD0392B0-A37E-477A-A62F-D7727296054E@microsoft.com... > >I have a fairly complex SELECT statement. It is running on a server with 8 > > CPUs and 8GB RAM (using about 6.5GB). The statistics that I get when I > > run > > it are below. It is not the first time that I ran it so the execution > > plan > > already exists and it looks like the data is all in RAM which is fine. > > > > It is taking over 7 seconds to run and using about 1/2 sec of CPU time. > > I'm > > in Performance Monitor watching the 8 CPUs and none of them are near > > 100% - > > the entire CPU of the system gets to about 10-15% while this is running. > > The > > hard drives are not the bottleneck - they barely budge during the > > execution. > > Any ideas why it might be taking so long? What else should I look at? > > > > Thanks, > > Mark > > > > > > SQL Server parse and compile time: > > CPU time = 0 ms, elapsed time = 0 ms. > > > > (1242 row(s) affected) > > > > Table 'Worktable'. Scan count 1239, logical reads 1249, physical reads 0, > > read-ahead reads 0. > > Table 'Worktable'. Scan count 1241, logical reads 1249, physical reads 0, > > read-ahead reads 0. > > Table 'Worktable'. Scan count 0, logical reads 0, physical reads 0, > > read-ahead reads 0. > > Table 'Worktable'. Scan count 0, logical reads 0, physical reads 0, > > read-ahead reads 0. > > Table 'tbFirmClient'. Scan count 1, logical reads 18, physical reads 0, > > read-ahead reads 0. > > Table 'tbFirm'. Scan count 1, logical reads 2671, physical reads 0, > > read-ahead reads 0. > > Table 'tbFirmStatisticSuitability'. Scan count 0, logical reads 0, > > physical > > reads 0, read-ahead reads 0. > > Table 'tbSecurity'. Scan count 0, logical reads 0, physical reads 0, > > read-ahead reads 0. > > Table 'tbStatistic'. Scan count 0, logical reads 0, physical reads 0, > > read-ahead reads 0. > > Table 'tbSuitabilityStudy'. Scan count 4, logical reads 12, physical reads > > 0, read-ahead reads 0. > > Table 'Worktable'. Scan count 0, logical reads 0, physical reads 0, > > read-ahead reads 0. > > Table 'Worktable'. Scan count 0, logical reads 0, physical reads 0, > > read-ahead reads 0. > > Table 'tbAltpurchpower'. Scan count 784, logical reads 2287, physical > > reads > > 0, read-ahead reads 0. > > Table 'tbFirmScore'. Scan count 1243, logical reads 12644, physical reads > > 0, > > read-ahead reads 0. > > Table 'tbPosition'. Scan count 1243, logical reads 11966, physical reads > > 0, > > read-ahead reads 0. > > Table 'tbAddressPhone'. Scan count 2480, logical reads 12099, physical > > reads > > 0, read-ahead reads 0. > > Table 'tbRegion'. Scan count 1, logical reads 2, physical reads 0, > > read-ahead reads 0. > > Table 'tbCountry'. Scan count 1240, logical reads 2480, physical reads 0, > > read-ahead reads 0. > > Table 'tbState'. Scan count 824, logical reads 1648, physical reads 0, > > read-ahead reads 0. > > Table 'tbCity'. Scan count 1240, logical reads 2487, physical reads 0, > > read-ahead reads 0. > > Table 'tbAddress'. Scan count 1242, logical reads 15080, physical reads 0, > > read-ahead reads 0. > > Table 'tbTurnoverRating'. Scan count 1, logical reads 2, physical reads 0, > > read-ahead reads 0. > > Table '#04BDFF0F'. Scan count 0, logical reads 0, physical reads 0, > > read-ahead reads 0. > > Table 'tbIRXGroup'. Scan count 1, logical reads 2, physical reads 0, > > read-ahead reads 0. > > Table 'tbIRXLogin'. Scan count 1, logical reads 2, physical reads 0, > > read-ahead reads 0. > > Table 'tbFirmType'. Scan count 2, logical reads 82, physical reads 0, > > read-ahead reads 0. > > Table 'tbInvestmentStyle'. Scan count 2, logical reads 4, physical reads > > 0, > > read-ahead reads 0. > > Table 'tbMediaFocus'. Scan count 1, logical reads 2, physical reads 0, > > read-ahead reads 0. > > Table 'tbMediaFrequency'. Scan count 1, logical reads 2, physical reads 0, > > read-ahead reads 0. > > Table 'tbFirmSuperType'. Scan count 1, logical reads 2, physical reads 0, > > read-ahead reads 0. > > > > SQL Server Execution Times: > > CPU time = 469 ms, elapsed time = 7442 ms. > > > > > The best way to tell if a particular plan is being reused or not is to look
at the UsedCount column in the syscacheobjects table for that plan. If it increases by 1 each time you call it then it is reusing the plan. If not then chances are it is creating a new one each time. Also as Erland stated blocking could be a likely cause as well. What happens if you run the query after setting the isolation level to Read uncommitted? SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED -- run your query here If it comes back in a fraction of the time that is a good bet blocking is an issue. Of coarse there are others ways to see blocking but this pretty much rules it all out. -- Show quoteAndrew J. Kelly SQL MVP "MarkR" <Ma***@discussions.microsoft.com> wrote in message news:78F54CF4-A2F2-48F8-B356-D24FF685DF9C@microsoft.com... > I'm not sure it is using the same query plan. I am assuming it is because > > SQL Server parse and compile time: > CPU time = 0 ms, elapsed time = 0 ms. > > ... but I could be wrong. > > I added a 'maxdop 1' hint which made no difference. > > Mark > > > "Andrew J. Kelly" wrote: > >> Are you sure it is using the same query plan? It sounds like the extra >> time >> may be compile time. You are certainly joining lots of tables and to >> generate a plan like that can take a while. Also what is your MAXDOP set >> to? >> Try setting it to 1 or adding a hint in the query to set it to 1 and see >> if >> that makes a difference. >> >> -- >> Andrew J. Kelly SQL MVP >> >> "MarkR" <Ma***@discussions.microsoft.com> wrote in message >> news:BD0392B0-A37E-477A-A62F-D7727296054E@microsoft.com... >> >I have a fairly complex SELECT statement. It is running on a server >> >with 8 >> > CPUs and 8GB RAM (using about 6.5GB). The statistics that I get when I >> > run >> > it are below. It is not the first time that I ran it so the execution >> > plan >> > already exists and it looks like the data is all in RAM which is fine. >> > >> > It is taking over 7 seconds to run and using about 1/2 sec of CPU time. >> > I'm >> > in Performance Monitor watching the 8 CPUs and none of them are near >> > 100% - >> > the entire CPU of the system gets to about 10-15% while this is >> > running. >> > The >> > hard drives are not the bottleneck - they barely budge during the >> > execution. >> > Any ideas why it might be taking so long? What else should I look at? >> > >> > Thanks, >> > Mark >> > >> > >> > SQL Server parse and compile time: >> > CPU time = 0 ms, elapsed time = 0 ms. >> > >> > (1242 row(s) affected) >> > >> > Table 'Worktable'. Scan count 1239, logical reads 1249, physical reads >> > 0, >> > read-ahead reads 0. >> > Table 'Worktable'. Scan count 1241, logical reads 1249, physical reads >> > 0, >> > read-ahead reads 0. >> > Table 'Worktable'. Scan count 0, logical reads 0, physical reads 0, >> > read-ahead reads 0. >> > Table 'Worktable'. Scan count 0, logical reads 0, physical reads 0, >> > read-ahead reads 0. >> > Table 'tbFirmClient'. Scan count 1, logical reads 18, physical reads 0, >> > read-ahead reads 0. >> > Table 'tbFirm'. Scan count 1, logical reads 2671, physical reads 0, >> > read-ahead reads 0. >> > Table 'tbFirmStatisticSuitability'. Scan count 0, logical reads 0, >> > physical >> > reads 0, read-ahead reads 0. >> > Table 'tbSecurity'. Scan count 0, logical reads 0, physical reads 0, >> > read-ahead reads 0. >> > Table 'tbStatistic'. Scan count 0, logical reads 0, physical reads 0, >> > read-ahead reads 0. >> > Table 'tbSuitabilityStudy'. Scan count 4, logical reads 12, physical >> > reads >> > 0, read-ahead reads 0. >> > Table 'Worktable'. Scan count 0, logical reads 0, physical reads 0, >> > read-ahead reads 0. >> > Table 'Worktable'. Scan count 0, logical reads 0, physical reads 0, >> > read-ahead reads 0. >> > Table 'tbAltpurchpower'. Scan count 784, logical reads 2287, physical >> > reads >> > 0, read-ahead reads 0. >> > Table 'tbFirmScore'. Scan count 1243, logical reads 12644, physical >> > reads >> > 0, >> > read-ahead reads 0. >> > Table 'tbPosition'. Scan count 1243, logical reads 11966, physical >> > reads >> > 0, >> > read-ahead reads 0. >> > Table 'tbAddressPhone'. Scan count 2480, logical reads 12099, physical >> > reads >> > 0, read-ahead reads 0. >> > Table 'tbRegion'. Scan count 1, logical reads 2, physical reads 0, >> > read-ahead reads 0. >> > Table 'tbCountry'. Scan count 1240, logical reads 2480, physical reads >> > 0, >> > read-ahead reads 0. >> > Table 'tbState'. Scan count 824, logical reads 1648, physical reads 0, >> > read-ahead reads 0. >> > Table 'tbCity'. Scan count 1240, logical reads 2487, physical reads 0, >> > read-ahead reads 0. >> > Table 'tbAddress'. Scan count 1242, logical reads 15080, physical reads >> > 0, >> > read-ahead reads 0. >> > Table 'tbTurnoverRating'. Scan count 1, logical reads 2, physical reads >> > 0, >> > read-ahead reads 0. >> > Table '#04BDFF0F'. Scan count 0, logical reads 0, physical reads 0, >> > read-ahead reads 0. >> > Table 'tbIRXGroup'. Scan count 1, logical reads 2, physical reads 0, >> > read-ahead reads 0. >> > Table 'tbIRXLogin'. Scan count 1, logical reads 2, physical reads 0, >> > read-ahead reads 0. >> > Table 'tbFirmType'. Scan count 2, logical reads 82, physical reads 0, >> > read-ahead reads 0. >> > Table 'tbInvestmentStyle'. Scan count 2, logical reads 4, physical >> > reads >> > 0, >> > read-ahead reads 0. >> > Table 'tbMediaFocus'. Scan count 1, logical reads 2, physical reads 0, >> > read-ahead reads 0. >> > Table 'tbMediaFrequency'. Scan count 1, logical reads 2, physical reads >> > 0, >> > read-ahead reads 0. >> > Table 'tbFirmSuperType'. Scan count 1, logical reads 2, physical reads >> > 0, >> > read-ahead reads 0. >> > >> > SQL Server Execution Times: >> > CPU time = 469 ms, elapsed time = 7442 ms. >> > >> >> >> MarkR (Ma***@discussions.microsoft.com) writes:
> I'm not sure it is using the same query plan. I am assuming it is because If that made no difference, your original plan is not a parallel plan.> > SQL Server parse and compile time: > CPU time = 0 ms, elapsed time = 0 ms. > > ... but I could be wrong. > > I added a 'maxdop 1' hint which made no difference. That is, if the original plan was a parallel plan, you would get compile time, this time. -- Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se Books Online for SQL Server 2005 at http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx Books Online for SQL Server 2000 at http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx Do you have the best indexing strategy in place?
Table 'tbCountry'. Scan count 1240, logical reads 2480, physical reads 0, read-ahead reads 0. Table 'tbState'. Scan count 824, logical reads 1648, physical reads 0, read-ahead reads 0. Table 'tbCity'. Scan count 1240, logical reads 2487, physical reads 0, read-ahead reads 0. Table 'tbAddress'. Scan count 1242, logical reads 15080, physical reads 0, read-ahead reads 0. These items would be a good place to start looking as they seem to be pointing to missing indexes. Ideally, there is no need to perform a scan, useless you are specifcally wanting to return the entire content of the table. Regards Colin Dawson. www.cjdawson.com Show quote "MarkR" <Ma***@discussions.microsoft.com> wrote in message news:BD0392B0-A37E-477A-A62F-D7727296054E@microsoft.com... >I have a fairly complex SELECT statement. It is running on a server with 8 > CPUs and 8GB RAM (using about 6.5GB). The statistics that I get when I > run > it are below. It is not the first time that I ran it so the execution > plan > already exists and it looks like the data is all in RAM which is fine. > > It is taking over 7 seconds to run and using about 1/2 sec of CPU time. > I'm > in Performance Monitor watching the 8 CPUs and none of them are near > 100% - > the entire CPU of the system gets to about 10-15% while this is running. > The > hard drives are not the bottleneck - they barely budge during the > execution. > Any ideas why it might be taking so long? What else should I look at? > > Thanks, > Mark > > > SQL Server parse and compile time: > CPU time = 0 ms, elapsed time = 0 ms. > > (1242 row(s) affected) > > Table 'Worktable'. Scan count 1239, logical reads 1249, physical reads 0, > read-ahead reads 0. > Table 'Worktable'. Scan count 1241, logical reads 1249, physical reads 0, > read-ahead reads 0. > Table 'Worktable'. Scan count 0, logical reads 0, physical reads 0, > read-ahead reads 0. > Table 'Worktable'. Scan count 0, logical reads 0, physical reads 0, > read-ahead reads 0. > Table 'tbFirmClient'. Scan count 1, logical reads 18, physical reads 0, > read-ahead reads 0. > Table 'tbFirm'. Scan count 1, logical reads 2671, physical reads 0, > read-ahead reads 0. > Table 'tbFirmStatisticSuitability'. Scan count 0, logical reads 0, > physical > reads 0, read-ahead reads 0. > Table 'tbSecurity'. Scan count 0, logical reads 0, physical reads 0, > read-ahead reads 0. > Table 'tbStatistic'. Scan count 0, logical reads 0, physical reads 0, > read-ahead reads 0. > Table 'tbSuitabilityStudy'. Scan count 4, logical reads 12, physical reads > 0, read-ahead reads 0. > Table 'Worktable'. Scan count 0, logical reads 0, physical reads 0, > read-ahead reads 0. > Table 'Worktable'. Scan count 0, logical reads 0, physical reads 0, > read-ahead reads 0. > Table 'tbAltpurchpower'. Scan count 784, logical reads 2287, physical > reads > 0, read-ahead reads 0. > Table 'tbFirmScore'. Scan count 1243, logical reads 12644, physical reads > 0, > read-ahead reads 0. > Table 'tbPosition'. Scan count 1243, logical reads 11966, physical reads > 0, > read-ahead reads 0. > Table 'tbAddressPhone'. Scan count 2480, logical reads 12099, physical > reads > 0, read-ahead reads 0. > Table 'tbRegion'. Scan count 1, logical reads 2, physical reads 0, > read-ahead reads 0. > Table 'tbCountry'. Scan count 1240, logical reads 2480, physical reads 0, > read-ahead reads 0. > Table 'tbState'. Scan count 824, logical reads 1648, physical reads 0, > read-ahead reads 0. > Table 'tbCity'. Scan count 1240, logical reads 2487, physical reads 0, > read-ahead reads 0. > Table 'tbAddress'. Scan count 1242, logical reads 15080, physical reads 0, > read-ahead reads 0. > Table 'tbTurnoverRating'. Scan count 1, logical reads 2, physical reads 0, > read-ahead reads 0. > Table '#04BDFF0F'. Scan count 0, logical reads 0, physical reads 0, > read-ahead reads 0. > Table 'tbIRXGroup'. Scan count 1, logical reads 2, physical reads 0, > read-ahead reads 0. > Table 'tbIRXLogin'. Scan count 1, logical reads 2, physical reads 0, > read-ahead reads 0. > Table 'tbFirmType'. Scan count 2, logical reads 82, physical reads 0, > read-ahead reads 0. > Table 'tbInvestmentStyle'. Scan count 2, logical reads 4, physical reads > 0, > read-ahead reads 0. > Table 'tbMediaFocus'. Scan count 1, logical reads 2, physical reads 0, > read-ahead reads 0. > Table 'tbMediaFrequency'. Scan count 1, logical reads 2, physical reads 0, > read-ahead reads 0. > Table 'tbFirmSuperType'. Scan count 1, logical reads 2, physical reads 0, > read-ahead reads 0. > > SQL Server Execution Times: > CPU time = 469 ms, elapsed time = 7442 ms. >  |
|||||||||||||||||||||||
Other interesting topics