May 18, 2015 at 11:10 am
Hi Experts, I have this really crazy situation. I have this table which is created randomly almost everyday. It fills up the log file to 28+ GB. There are bunch of inserts and then the table gets truncated, so if I run Select statement on that table, it return 0 result.
Question: Is there a way to find out what data is getting inserted into that table?
Let me know if I can provide you guys with additional information regarding this table.
FYI-I have talked to Developers, Application support people but no one knows what this table is and does.
"He who learns for the sake of haughtiness, dies ignorant. He who learns only to talk, rather than to act, dies a hyprocite. He who learns for the mere sake of debating, dies irreligious. He who learns only to accumulate wealth, dies an atheist. And he who learns for the sake of action, dies a mystic."[/i]
May 18, 2015 at 11:50 am
New Born DBA (5/18/2015)
Hi Experts, I have this really crazy situation. I have this table which is created randomly almost everyday. It fills up the log file to 28+ GB. I know what table does. It does bunch of inserts and then the table gets truncated, so if I run Select statement on that table, it return 0 result. Question: Is there a way to find out what kind of data is being inserted into that table? Let me know if I can provide you guys with additional information regarding this table.FYI-I have talked to Developers, Application support people but no one knows what this table is and does.
You can tap into the activities with a trigger, extended events or even a trace, but that might in the end give you even a bigger head ache. Guess there is a single / few large transactions which cause this but few little pieces of information needed: what is the recovery model, how frequently (if applicable) do the log backup run, is this the only transactional activity, what's isolation used?
😎
May 18, 2015 at 11:57 am
Eirikur Eiriksson (5/18/2015)You can tap into the activities with a trigger, extended events or even a trace, but that might in the end give you even a bigger head ache. Guess there is a single / few large transactions which cause this but few little pieces of information needed: what is the recovery model, how frequently (if applicable) do the log backup run, is this the only transactional activity, what's isolation used?
😎
Recovery model is set to FULL. There are multiple transactional activity, but I 'd say this is the only transaction that fills up the log file. TLog backup runs every hour, Isolation level is set to Read Committed.
"He who learns for the sake of haughtiness, dies ignorant. He who learns only to talk, rather than to act, dies a hyprocite. He who learns for the mere sake of debating, dies irreligious. He who learns only to accumulate wealth, dies an atheist. And he who learns for the sake of action, dies a mystic."[/i]
May 19, 2015 at 9:44 am
So I am guessing it is not possible to track what data/value is getting inserted.
"He who learns for the sake of haughtiness, dies ignorant. He who learns only to talk, rather than to act, dies a hyprocite. He who learns for the mere sake of debating, dies irreligious. He who learns only to accumulate wealth, dies an atheist. And he who learns for the sake of action, dies a mystic."[/i]
May 19, 2015 at 9:53 am
Search your stored procedures to see whether any of them are doing the inserts, deletes and/or truncates. Then run a trace against the database, capturing the table name or stored procedure name(s) as appropriate. Don't leave the trace running for any longer than it needs to, since there may be a performance impact.
John
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply