AWS DMS(Database migration service) causing the DB log file usage to increase

Kranthi DBA 221 Reputation points
2021-07-22T07:22:26.347+00:00

I am seeing issues wherein the sessions that run from the AWS DMS service go into sleeping state resulting the DB log file usage to increase and we are unable to shrink the log file due to this. DMS service was stopped to resolve the issue. Could some one please advise if they came across this issue and what needs to be done to resolve the same.

Thanks in Advance!

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
13,826 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Erland Sommarskog 111.5K Reputation points MVP
    2021-07-22T07:58:00.88+00:00

    You should probably inquire in an Amazon forum about their products.

    But I get a little worried when you say "we are unable to shrink the log file due to this". Why would you shrink the log file in the first place? That's a very exceptional thing to do.


  2. CathyJi-MSFT 22,206 Reputation points Microsoft Vendor
    2021-07-22T08:14:36.63+00:00

    Hi @Kranthi DBA ,

    Log for AWS DMS migration task growing? If so, please post your issue on AWS Database Migration Service forum, people there will give you a better help. SQL server general tag that talking about issues about MS SQL server.

    By the way, check if below log could help you.

    Introducing log management in AWS Database Migration Service


    If the response is helpful, please click "Accept Answer" and upvote it, as this could help other community members looking for similar queries.


  3. CathyJi-MSFT 22,206 Reputation points Microsoft Vendor
    2021-07-23T10:03:36.487+00:00

    Hi @Kranthi DBA ,

    >It i s the SQL log file that is growing in size.

    If you want to reduce the log file size. You need to find the reason that why the log file growth rapidly, then shrink the SQL log file to reduce the log size.

    Normally we follow the steps below to shrink SQL log file:

    1. Perform full backup of database
    2. Perform transaction log backup
      sometimes, we have to perform multi transaction log backup before the transaction log could be shrank.
    3. Shrink transaction log
      if the transaction log cannot be shrank, please execute the following statement to check why the transaction log cannot be shrink:
      SELECT log_reuse_wait_desc FROM sys.databases WHERE name='<database name>'
      if the result is other than NOTHING, please perform corresponding operation. Then please try step 2 and 3 again.
    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.