Post reply

How to Safely Remove a SQL Server Data File Without Downtime

  • May 16, 2025 at 12:00 am

    #4585279

    Comments posted to this topic are about the item How to Safely Remove a SQL Server Data File Without Downtime

  • May 16, 2025 at 5:06 pm

    #4592234

    Very useful article as it is very useful in real-time scenario.

     

    Thanks,

    Rama

  • May 17, 2025 at 3:40 am

    #4592419

    Thanks Rama

  • June 3, 2025 at 2:32 pm

    #4602009

    I had to read this article several times not only because the subject matter was new to me, but, also, because I got hung up on these discrepancies/inconsistencies.

    1. Probable inconsistency: Step 1 specified "we attach a new Azure-managed disk and add an extra .ndf file to that disk (D:)."

    Drive letter "D" was not used in either FILENAME.

    2. Probable discrepancy: Step 2 specified "We force SQL Server to store data in the .ndf file by assigning it to the ExtraFG filegroup."

    In the CREATE TABLE statement, right up to before "ON AzureFG," I could understand how the data file would be assigned to the ExtraFG filegroup.

    Completing the CREATE TABLE statement, I thought that the data file would have been assigned to the AzureFG filegroup and stored on one of its data files whose drive were "F" and "G"; however, the comment posted was "Storing Data on C:\ Drive."

    So, where (filegroup and drive) was this table stored?

    3. Probable discrepancy: Step 2 correctly stipulated that the ALTER DATABASE statement--pointing to FILE ECommerceDataG--would fail.

    Then, in Step 4, the ALTER DATABASE statement pointed to FILE ECommerceData and not ECommerceDataG.

  • June 12, 2025 at 4:44 am

    #4606379

    Hi William,

    Yes I accept a few inconsistency which I will get rectified. But the message and step is clear.

    Below are

    1. Probable inconsistency: Step 1 specified "we attach a new Azure-managed disk and add an extra .ndf file to that disk (D:)."

    Drive letter "D" was not used in either FILENAME.

    Author Reply ---> Yes it should be F: and G: . Sorry for causing confusion due to a typo, but this does not break the entire flow and message.

    2. In the CREATE TABLE statement, right up to before "ON AzureFG," I could understand how the data file would be assigned to the ExtraFG filegroup.--> Yes This is expected to be on AzureFG and in my example I have to remove one drive (G:) from AzureFG only..

    3. Yes In text it is typo, but if you see the screenshot attached you will see ECommerceDataG was removed. I will request to rectify  the typos ..

    Thanks for your inputs and pointing out discrepencies.

    Attachments:
    You must be logged in to view attached files.

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply