Timeline for SQLServer In-Memory database and log file size unexpected increase
Current License: CC BY-SA 3.0
11 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Aug 18, 2016 at 12:34 | vote | accept | irimias | ||
Aug 8, 2016 at 16:05 | answer | added | irimias | timeline score: 1 | |
Aug 5, 2016 at 15:22 | comment | added | Slava Murygin |
fn_dblog is way to search, but I do not know how to find there a transaction, which holds it. Did you look for any opened transaction? I doubt if any, but just in case.
|
|
Aug 5, 2016 at 15:11 | comment | added | irimias | @Slava : what do you mean ? analyzing the growing .ldf file (approx 60 Go) ? I'm not sure to know how to do that... Are there special DMVs (or external tools) you recommend for that ? | |
Aug 5, 2016 at 14:51 | comment | added | Slava Murygin | If the question only on the log, then look inside the log file at the transaction, which is holding it and see what it is doing. | |
Aug 5, 2016 at 8:25 | history | edited | irimias | CC BY-SA 3.0 |
added 431 characters in body
|
Aug 5, 2016 at 7:04 | comment | added | irimias | @Randolph West : the question is : why log file size is suddenly increasing (up to dozens of Go...) although there is no activity on the in-memory objects ? | |
Aug 5, 2016 at 7:04 | comment | added | irimias | @Slaya Murygin : it's not really production, that's why I don't feel sorry. BUT I don't want the same thing to happen when I will use this feature in real production ! | |
Aug 4, 2016 at 23:34 | comment | added | Randolph West | What exactly is your question? | |
Aug 4, 2016 at 16:47 | comment | added | Slava Murygin | Good example of "testing in production". Fill sorry for you. Have to take a look at that. | |
Aug 4, 2016 at 15:06 | history | asked | irimias | CC BY-SA 3.0 |