Problem: SQL Server database stuck in RESTORING state Sometimes the database is in a restoring state after restarting the machine or for some other reason. It usually happens with big databases when a long transaction is in progress and an unexpected server shutdown or restart occurs. Fix: Sources: https://www.mssqltips.com/sqlservertip/5460/sql-server-database-stuck-in-restoring-state/
Error: When trying to create a new cluster in Failover Cluster Manager, trying to add a new server gives the following error… The computer "xxxxx" is joined to a cluster. The computer is cloning from an existing computer that was part of a cluster. Fix: Open up PowerShell (as administrator) on that computer and type... » read more
Problem: Unable to start SQL Server services. Error: Error 1069: The service did not start due to a logon failure. Fix: 1. Make sure service account running the service is part of the “Backup Operators” group on the local computer. Control Panel\User Accounts\User Accounts -> Manage User Accounts 2. Make sure the service account running... » read more
Use the following to check the current range for the partition. Example: Extend existing partition from 2018 to 2019. Add additional file group first, then modify partition schema and function. No need to modify partition table itself if the table is already setup to use partition. Step 1: Add Additional File Group Step 2: Add... » read more
Error: The report server was unable to validate the integrity of encrypted data in the database. (rsCannotValidateEncryptedData) Solution: Reporting Services Configuration Manager -> Encryption Keys -> Change Need to reset data source connection in SSRS.
REPLACE Option Impact REPLACE should be used rarely and only after careful consideration. Restore normally prevents accidentally overwriting a database with a different database. If the database specified in a RESTORE statement already exists on the current server and the specified database family GUID differs from the database family GUID recorded in the backup set,... » read more
RDCMan Error Unable to log off from xxxxxxxx. Reason: Unable to enumerate remote sessions. Issue: That error is common when using Remote Desktop Connection Manager and trying to log off via right click. You should log out via the start menu in the remote desktop session.
Please be aware that depending on your DNS provider it can take up to 48 hours for the DNS entry changes to propagate. You can verify that the DNS propagation is working as expected by using http://digwebinterface.com/ http://digwebinterface.com
A Non-clustered index is built using the same 8K-page B-tree structure that is used to build a Clustered index, except that the data and the Non-clustered index are stored separately. A Non-clustered index is different from a Clustered index in that, the underlying table rows will not be stored and sorted based on the Non-clustered... » read more
Remote Desktop Services (RDS or RDP) and Terminal Services provide two options when closing a client session: you can either “Log Off” or “Disconnect“. Log Off – Ends the session running on the remote computer or server. Any applications running within the session will be closed and unsaved changes made to open files will be lost.... » read more