Peter Guerndt

My feedback

  1. 146 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    21 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 3

    <=-=Jan 8 2018 12:16PM=-=>

    Thanks for the suggestion.
    We’ll consider it for a future release.

    Are there specific limitations imposed when you have the filegroup, e.g., no database snapshot, that hold you back from creating the filegroup?
    Or is it only the feeling of not being able to turn back?


    Jos de Bruijn – Database Systems PM

    Peter Guerndt supported this idea  · 
  2. 23 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Peter Guerndt commented  · 

    Same problem here. We had to remove the non-clustered index because we would need to use index hints at too many places. For now we can live without it, but it would be nice to have a nc index for some of our queries.

    Has anyone tested if the optimizer behaves differently in SQL Server 2019?

    Peter Guerndt supported this idea  · 
  3. 4 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    9 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Peter Guerndt commented  · 
    An error occurred while saving the comment
    Peter Guerndt commented  · 

    It seems like this is happening because we renamed the [sa] account.

    The script sp_vupgrade_replication is adding a new agent job [Monitor and sync replication agent jobs]. When the [sa] account is renamed it tries to add the job with owner [domain\sa] which doesn't exist in the domain and thus we receive the error:
    "The specified '@owner_login_name' is invalid (valid values are returned by sp_helplogins [excluding Windows NT groups]). " and the script fails.

    When we use the default name [sa] installing SP2CU4 is working without any problems and the new job is created with [sa] as owner.

    Peter Guerndt supported this idea  · 
    An error occurred while saving the comment
    Peter Guerndt commented  · 

    Hi,
    We experienced the same errror when installing SQL 2016 SP2-CU4 on an instance with replication enabled. So this seems to be an issue there too. Thanks so much for the workaround it worked and saved us tonight.

    We received the same error:
    2018-11-29 20:46:09.47 spid3s The specified '@owner_login_name' is invalid (valid values are returned by sp_helplogins [excluding Windows NT groups]).
    2018-11-29 20:46:09.47 spid3s Error executing sp_vupgrade_replication.
    2018-11-29 20:46:09.47 spid3s Saving upgrade script status to 'SOFTWARE\Microsoft\MSSQLServer\Replication\Setup'.
    2018-11-29 20:46:09.47 spid3s Saved upgrade script status successfully.
    2018-11-29 20:46:09.47 spid3s Database 'master' is upgrading script 'upgrade_ucp_cmdw_discovery.sql' from level 218108834 to level 218109041.
    2018-11-29 20:46:09.69 spid3s Database 'master' is upgrading script 'msdb110_upgrade.sql' from level 218108834 to level 218109041.
    2018-11-29 20:46:09.69 spid3s ----------------------------------
    2018-11-29 20:46:09.69 spid3s Starting execution of PRE_MSDB.SQL
    2018-11-29 20:46:09.69 spid3s ----------------------------------
    2018-11-29 20:46:09.76 spid3s Error: 15002, Severity: 16, State: 1.
    2018-11-29 20:46:09.76 spid3s The procedure 'sys.sp_dbcmptlevel' cannot be executed within a transaction.
    2018-11-29 20:46:09.76 spid3s -----------------------------------------
    2018-11-29 20:46:09.76 spid3s Starting execution of PRE_SQLAGENT100.SQL
    2018-11-29 20:46:09.76 spid3s -----------------------------------------
    2018-11-29 20:46:09.77 spid3s Error: 226, Severity: 16, State: 6.
    2018-11-29 20:46:09.77 spid3s ALTER DATABASE statement not allowed within multi-statement transaction.
    2018-11-29 20:46:09.77 spid3s The failed batch of t-sql statements :

    --set compatibility level for msdb database to 130
    ALTER DATABASE msdb
    SET COMPATIBILITY_LEVEL = 130

    2018-11-29 20:46:09.77 spid3s Error: 912, Severity: 21, State: 2.
    2018-11-29 20:46:09.77 spid3s Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 226, state 6, severity 16. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
    2018-11-29 20:46:09.77 spid3s Error: 3417, Severity: 21, State: 3.
    2018-11-29 20:46:09.77 spid3s Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
    2018-11-29 20:46:09.77 spid3s SQL Server shutdown has been initiated
    2018-11-29 20:46:09.79 spid3s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

Feedback and Knowledge Base