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,
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,