There is a database in MS SQL 2012 ~ 130 GB in size. The problem is that in the compressed form it takes 9 GB, and if you unload this database as a * .dt file from 1C, we get up to ~ 3 GB. Shrink means MS SQL removes only 2 MB of data. How can I diagnose or find and fix a problem?

  • one
    and how much of them logs, and what data? and what is meant by compressed view - teran
  • @teran, I just cleaned the logs. 5MB occupy the hard disk. I'm talking about MS SQL logs. There are suspicions that 1C logs a large number of actions, but I do not understand 1C itself. Is there such a mechanism in the program, I also do not know. If there is, tell me, please. - Alexey
  • What exactly do you have 120 gigs? Mdf? Ldf? Folder logs? Something else? - PashaPash ♦
  • @PashaPash, I'm talking about the file .mdf - Alex
  • @Alexey look at the sizes of the tables through the Object Explorer Details in Management Studio (F7). Look at the settings for the selection of data (in the database properties there, in Files - the starting size of 100 gigs can be set there). In general, look for what exactly takes place in the database. - PashaPash ♦

1 answer 1

SQL Server Management Studio \ Databases \ Right-click on the base Parameters \ Recovery Model \ set to <Simple> If there is free time, after the above steps, make restructuring, upload to dt. Then load from dt

  • This model changes the degree of logging. When creating a database, I always choose the “simple” model. Now logs are cleared and occupy ~ 5MB - Alexey
  • see also: Configurator \ Administration \ Log Settings; Although this log is kept in a separate file and does not fall into the SQL backup database - santavital