Messages sur le rétablissement parallèle
Parallel redo is shutdown for database '' with worker pool size [2].
Parallel redo is started for database '' with worker pool size [2].
Starting up database ''
Je vois cela sur un PC client beaucoup dans l'Observateur d'événements Windows (ID d'événement 49930 ou 17137). Il s'agit d'un PC Windows ordinaire, pas d'un serveur, avec une instance par défaut de SQL Server 2017 Express Edition et SSMS.
Quel est ce refaire parallèle?
Voici la sortie du journal des erreurs:
2019-05-28 12:23:03.360 spid16s A self-generated certificate was successfully loaded for encryption.
2019-05-28 12:23:03.360 spid16s Server is listening on [ 'any' <ipv6> 1433].
2019-05-28 12:23:03.360 spid16s Server is listening on [ 'any' <ipv4> 1433].
2019-05-28 12:23:03.360 spid16s Server is listening on [ 'any' <ipv6> 50374].
2019-05-28 12:23:03.360 spid16s Server is listening on [ 'any' <ipv4> 50374].
2019-05-28 12:23:03.360 spid16s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\FOLLOWIN ].
2019-05-28 12:23:03.360 spid16s Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$FOLLOWIN\sql\query ].
2019-05-28 12:23:03.360 spid16s Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2019-05-28 12:23:03.360 Server SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
2019-05-28 12:23:03.360 spid16s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2019-05-28 12:23:03.370 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/pcFoo:FOLLOWIN ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2019-05-28 12:23:03.370 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/pcFoo:1433 ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2019-05-28 12:23:03.430 spid17s A new instance of the full-text filter daemon Host process has been successfully started.
2019-05-28 12:23:03.520 spid12s Starting up database 'mssqlsystemresource'.
2019-05-28 12:23:03.520 spid21s Starting up database 'Foobar'.
2019-05-28 12:23:03.520 spid20s Starting up database 'msdb'.
2019-05-28 12:23:03.530 spid12s The resource database build version is 14.00.3162. This is an informational message only. No user action is required.
2019-05-28 12:23:03.550 spid12s Synchronize Database 'master' (1) with Resource Database.
2019-05-28 12:23:03.550 spid21s Parallel redo is started for database 'Foobar' with worker pool size [2].
2019-05-28 12:23:03.560 spid12s Starting up database 'model'.
2019-05-28 12:23:03.560 spid21s Parallel redo is shutdown for database 'Foobar' with worker pool size [2].
2019-05-28 12:23:03.580 spid12s Synchronize Database 'model' (3) with Resource Database.
2019-05-28 12:23:03.590 spid12s Polybase feature disabled.
2019-05-28 12:23:03.590 spid12s Clearing tempdb database.
2019-05-28 12:23:03.670 spid12s Starting up database 'tempdb'.
2019-05-28 12:23:03.710 spid20s Synchronize Database 'msdb' (4) with Resource Database.
2019-05-28 12:23:03.710 spid21s Synchronize Database 'Foobar' (5) with Resource Database.
2019-05-28 12:23:03.710 spid22s The Service Broker endpoint is in disabled or stopped state.
2019-05-28 12:23:03.710 spid22s The Database Mirroring endpoint is in disabled or stopped state.
2019-05-28 12:23:03.730 spid22s Service Broker manager has started.
2019-05-28 12:23:03.730 spid6s Recovery is complete. This is an informational message only. No user action is required.
2019-05-28 12:28:21.180 spid51 Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
2019-05-28 12:28:21.180 spid51 Using 'xplog70.dll' version '2017.140.3162' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
2019-05-28 12:28:21.320 spid51 Starting up database 'Foobar'.
2019-05-28 12:28:21.340 spid51 Parallel redo is started for database 'Foobar' with worker pool size [2].
2019-05-28 12:28:21.350 spid51 Parallel redo is shutdown for database 'Foobar' with worker pool size [2].
2019-05-28 12:28:21.360 spid51 Starting up database 'Foo'.
2019-05-28 12:28:21.380 spid51 Parallel redo is started for database 'Foo' with worker pool size [2].
2019-05-28 12:28:21.400 spid51 Parallel redo is shutdown for database 'Foo' with worker pool size [2].
2019-05-28 12:28:21.410 spid51 Synchronize Database 'Foo' (6) with Resource Database.
2019-05-28 14:27:21.430 spid59 Starting up database 'Foo'.
2019-05-28 14:27:21.450 spid59 Parallel redo is started for database 'Foo' with worker pool size [2].
2019-05-28 14:27:21.470 spid59 Parallel redo is shutdown for database 'Foo' with worker pool size [2].
2019-05-28 14:27:21.480 spid59 Starting up database 'Foobar'.
2019-05-28 14:27:21.500 spid59 Parallel redo is started for database 'Foobar' with worker pool size [2].
2019-05-28 14:27:21.510 spid59 Parallel redo is shutdown for database 'Foobar' with worker pool size [2].
2019-05-28 14:27:38.330 spid59 Starting up database 'Foobar'.
2019-05-28 14:27:38.360 spid59 Parallel redo is started for database 'Foobar' with worker pool size [2].
2019-05-28 14:27:38.370 spid59 Parallel redo is shutdown for database 'Foobar' with worker pool size [2].
2019-05-28 14:27:40.010 spid59 Starting up database 'Foo'.
2019-05-28 14:27:40.050 spid59 Parallel redo is started for database 'Foo' with worker pool size [2].
2019-05-28 14:27:40.080 spid59 Parallel redo is shutdown for database 'Foo' with worker pool size [2].
2019-05-28 14:28:04.160 spid59 Starting up database 'Foo'.
2019-05-28 14:28:04.180 spid59 Parallel redo is started for database 'Foo' with worker pool size [2].
2019-05-28 14:28:04.210 spid59 Parallel redo is shutdown for database 'Foo' with worker pool size [2].
2019-05-28 14:28:10.620 spid52 Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2019-05-28 14:28:10.690 spid52 Using 'xpstar.dll' version '2017.140.3162' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2019-05-28 14:28:14.220 spid52 Starting up database 'Foo'.
2019-05-28 14:28:14.240 spid52 Parallel redo is started for database 'Foo' with worker pool size [2].
2019-05-28 14:28:14.270 spid52 Parallel redo is shutdown for database 'Foo' with worker pool size [2].
2019-05-28 14:28:14.410 Backup Database backed up. Database: Foo, creation date(time): 2019/05/08(15:06:00), pages dumped: 2555, first LSN: 48:9778:37, last LSN: 48:9795:1, number of dump devices: 1, device information: (FILE=2, TYPE=DISK: {'C:\Users\Joe\Documents\Backup Followin\Foo_FULL_05272019_235209.BAK'}). This is an informational message only. No user action is required.
2019-05-28 14:28:14.420 Backup BACKUP DATABASE successfully processed 2546 pages in 0.112 seconds (177.529 MB/sec).
2019-05-28 14:28:19.120 spid53 Starting up database 'Foo'.
2019-05-28 14:28:19.140 spid53 Parallel redo is started for database 'Foo' with worker pool size [2].
2019-05-28 14:28:19.160 spid53 Parallel redo is shutdown for database 'Foo' with worker pool size [2].
2019-05-28 14:28:20.610 spid59 Starting up database 'Foo'.
2019-05-28 14:28:20.650 spid59 Parallel redo is started for database 'Foo' with worker pool size [2].
2019-05-28 14:28:20.670 spid59 Parallel redo is shutdown for database 'Foo' with worker pool size [2].
2019-05-28 14:28:31.030 spid54 Using 'dbghelp.dll' version '4.0.5'
0.3162.1 (X64)
May 15 2019 19:14:30
Copyright (C) 2017 Microsoft Corporation
Express Edition (64-bit) on Windows 10 Pro 10.0 <X64> (Build 17763: )
Il s'agit d'un message de journal d'information ajouté dans SQL Server 2017 concernant la restauration parallèle pour les groupes de disponibilité:
Le comportement que vous voyez (où la reprise démarre et s'arrête immédiatement) est normal. C'est parce que les bases de données ne participent pas à un groupe de disponibilité. Lorsqu'une base de données démarre, les threads de rétablissement parallèles pour cette base de données démarrent, puis réalisent qu'il n'y a pas de groupe de disponibilité, puis s'arrêtent.
Vous pouvez le prouver en activant l'indicateur de trace global documenté et pris en charge 3459 pour désactiver la restauration parallèle, puis en désactivant et en ligne une base de données. Vous ne verrez plus ces messages.
Voir la capture d'écran de mon journal d'erreurs.
J'ai activé l'indicateur de trace, désactivé/activé la base de données: aucun message
J'ai désactivé l'indicateur de trace, désactivé/mis en ligne la base de données: messages renvoyés
À moins que vous n'activiez cet indicateur de trace, vous verrez ces messages chaque fois qu'une base de données est mise en ligne (soit parce que le serveur a redémarré, soit parce que la base de données a été spécifiquement mise hors ligne puis à nouveau en ligne, et probablement dans d'autres situations similaires). Cependant, ils ne sont pas une indication d'un problème.
Si votre base de données participe à une AG et que vous voyez ces messages "refaire est arrêté" tout au long de la journée, c'est peut-être parce que AUTO_CLOSE est activé (par défaut pour les bases de données utilisateur d'Express Edition). Envisagez de désactiver ce paramètre, ce qui est généralement considéré comme une "meilleure pratique:"
ALTER DATABASE YourDatabaseName SET AUTO_CLOSE OFF;
REMARQUE: ces messages ne sont [~ # ~] pas [~ # ~] liés à la partie "refaire" de la récupération après incident qui se produit au démarrage de la base de données.