administation – SQLpowered.com

Cannot open database X version 706. Upgrade the database to the latest version.

Jan Dvořák — Sat, 20 Apr 2019 19:22:04 +0000

Past week we were using tool for scanning database metadata across all our production servers and at one of them the tool captured following error when trying to access one of the databases:

After some searching and investigating detail about the server we captured two core informations:

The database is set for read-only access
The server was upgraded last week to never version (higher service pack).

This combination is the root cause of the database to be inaccessible: because it was set read-only during the instance upgrade, setup wasn’t able to upgrade the database too. The error above appears at every single action to recover now.

All these steps has failed:

1. Set the database for read_write access:

USE master;  
GO  
ALTER DATABASE [DB1] SET READ_WRITE;  
GO

2. Detach the database

3. Backup the database

4. Check if files aren’t locked at the file system level (read-only attribute)

In the end, we have finished with dropping the database and restoring it from the previous backup which led to successful database version upgrade.

It’s really one the best practices that before any patching or upgrade of SQL Server instance all read-only database should be set back to read-write mode.

Kde najít SQL Server 2017 Configuration Manager

Jan Dvořák — Sat, 05 Jan 2019 14:19:53 +0000

Když nainstalujete SQL Server 2017 na nejnovější Windows 10 a bude chtít pomocí SQL Server Configuration Manageru změnit parametry instance, bude jeho ikonu hledat v nainstalovaných programech marně. Nově je totiž Configuration Manager distribuován jako snap-in do Microsoft Management Console (mmc.exe) a pokud jej chcete spustit, použijte WIN+R a zadejte:

SQLServerManager14.msc => pro SQL Server 2017
SQLServerManager13.msc => pro SQL Server 2016
SQLServerManager12.msc => pro SQL Server 2014
SQLServerManager11.msc => pro SQL Server 2012

Pokud si chcete vytvořit zástupce na ploše, najde jednotlivé verze Manageru zde:

SQL Server 2017	C:\Windows\SysWOW64\SQLServerManager14.msc
SQL Server 2016	C:\Windows\SysWOW64\SQLServerManager13.msc
SQL Server 2014 (12.x)	C:\Windows\SysWOW64\SQLServerManager12.msc
SQL Server 2012 (11.x)	C:\Windows\SysWOW64\SQLServerManager11.msc

Více na MSDN – SQL Server Configuration Manager.

How to log SQL Server error messages to SQL/Windows error logs?

Jan Dvořák — Fri, 08 May 2015 05:57:36 +0000

Is there an option how to log various SQL Server error messages to SQL Server Error Log and to Windows Error Log? There is one and very simple: we can use system stored procedure sp_altermessage to alter system (message_id < 50 000) messages or user defined messages to be forwarder to both logs.Let see an example:

EXEC sp_altermessage 102, 'WITH_LOG', 'true'
EXEC sp_altermessage 208, 'WITH_LOG', 'true'
GO

SELECT * F_ROM dbo.table1
GO
SELECT * FROM dbo.invalid_name
GO

We have altered two system messages to be stored in SQL/WINDOWS logs:

SQL Server Log:

WINDOWS Applications Log:

Both messages are logged there as expected.

The effect of sp_altermessage with the WITH_LOG option is basically the same as of the RAISERROR WITH LOG parameter, except that sp_altermessage changes the logging behavior for all messages fired inside the engine.