Post reply

sp_addextendedproperty for transaction log file

  • May 7, 2020 at 2:01 pm

    #3749649

    hi there all,

    I am "playing around" with extended properties. I realized you can add them e. g. for the database files, using the logical file name, like this:

    execute sys.sp_addextendedproperty 
      @name  = 'myOwnInformation'
    , @value  = 'that works'
    , @level0type = 'FILEGROUP'
    , @level0name = 'PRIMARY'
    , @level1type = 'LOGICAL FILE NAME'
    , @level1name = 'DataFile1'
    , @level2type = null
    , @level2name = null
    go

    Unfortunately, this seems not to work for the transaction log file, as this seems not to have a filegroup. Giving NULL or empty string as filegroup returns in an error.

    Msg 15600, Level 16, State 1, Procedure sp_addextendedproperty, Line 37 [Batch Start Line 9]

    An invalid parameter or option was specified for procedure 'sp_addextendedproperty'.

    Is there no solution or do I just not find it?

    Thank you very much,

    Wolfgang

     

  • May 8, 2020 at 2:10 pm

    #3749932

    Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

  • May 8, 2020 at 3:50 pm

    #3749979

    I don't see log file listed here: https://docs.microsoft.com/en-us/sql/relational-databases/system-catalog-views/extended-properties-catalog-views-sys-extended-properties?view=sql-server-ver15

  • May 9, 2020 at 7:01 am

    #3750118

    At least is says „database file“, class 22.

    when looking here it is written little bit different, saying @level1type can be „logical file name“.

    thanks for the answer, and ok, when not possible it is not 🙂 would just have been convenient

    • This reply was modified 4 years, 7 months ago by  WolfgangE.

  • May 9, 2020 at 3:22 pm

    #3750186

    It is a logical file name, but from my reading, that is bound below the Filegroup. There isn't a Filegroup for the log.

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

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