May 16, 2014 at 10:55 am
Hi,
In my company, we have a huge database (about 63 GB). In this database, we have an table, which have 15 million data in it. This table has an identity column, with incremantal (1,1) condition. This table is a stock operations table. So the problem is;
In this table, January term is locked by the accounting operations, so no one write any data to January. But accidentally I realize that, some data write this table yesterday. But the problem is starting right now. We have identity column, as I said before. This inserted column has an ID, which if it created real day of the data (in february). If this row inserted without bulk insert, it must take the ID upper than 18000, but this ,inserted row take an id like 15600 etc. Also I must say, we have no log data about insert, delete or update.
My question is, sql can hold data in memory, page file, log file or something like that, and can write this data after 3 months later?
Thanks for your help,
May 16, 2014 at 11:09 am
No, SQL won't by itself suddenly write data from 3 months ago. If you're seeing inserts happen, something or someone is running those inserts.
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
May 16, 2014 at 11:16 am
Of course, I know that, because it is not possible. But before blame someone, I want to ask if I know false. So this person is professional because, firstly delete rows with the ordinary ID, and hold this data, and after accounting term, insert this data with bulk insert with checked identity insert on.
Thanks for your reply,
May 16, 2014 at 11:40 am
Time to give your legal dept (and maybe HR) a call, then investigate. I hope you have some auditing in place.
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
May 16, 2014 at 11:53 am
I hope so.
Thanks for your reply,
May 16, 2014 at 12:19 pm
First thing to run
SELECT
*
into dbo.myAudittable
FROM sys.dm_exec_connections c
cross apply sys.dm_exec_sql_text(c.most_recent_sql_handle)
If you are lucky, you'll have the culprit there.
😎
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply