Timeline for SQL Server 2008 R2 DETA Error: Can not get minimal database information in allotted time
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 3, 2011 at 17:24 | comment | added | Mike Walsh | No - I don't think it matters, that is just if you were doing tuning on multiple databases. SQL will connect to the proper database and isn't doing extra work in that one database because it is selected (msdn.microsoft.com/en-us/library/ms178494.aspx) think the biggest thing for you is going to be to "time box" your analysis. Maybe uncheck partitioning and just analyze indexes. | |
| Nov 3, 2011 at 15:05 | comment | added | Furkan Gözükara | but i chose same db for both workload analysis and tune. the image at your link shows master as workload analysis . is it the proper way ? | |
| Nov 3, 2011 at 15:04 | comment | added | Furkan Gözükara | i did not analyze it on real server. i downloaded my database backup restored and used that on my pc. so the sql server was totally free. worst of all it uses only 1 core while i have 8 cores on my pc. this is totally lame :D | |
| Nov 3, 2011 at 14:52 | comment | added | Mike Walsh | I added another point to my answer based on your comment above. Try and set the end time and see what happens. Read that article. HTH | |
| Nov 3, 2011 at 14:52 | history | edited | Mike Walsh | CC BY-SA 3.0 |
added 883 characters in body
|
| Nov 3, 2011 at 14:47 | comment | added | Mike Walsh | Are you doing your analysis on the server and SSMS on it? You are competing for memory and resources with the server when doing that then. DETA is a bit slower and I don't always like its results so I rarely use it and can't offer more than the smaller trace file approach or use SSMS someplace other than the actual server and connect to a separate instance than your prod instance, if not already Competing for load otherwise. | |
| Nov 3, 2011 at 14:33 | comment | added | Furkan Gözükara | hello. i could not find any way to split trace file. after i captured 2 gb trace file (which takes only several hours to capture at my website) and analyzed it. the analyze took more than 2 days to complete on my monster computer. DETA is very very slow. | |
| Nov 2, 2011 at 14:03 | history | answered | Mike Walsh | CC BY-SA 3.0 |