Database went into suspect mode database corruption One of our servers got migrated from one data center to other data center using third party tool called Zerto. After migration two databases went into suspect mode. Errors in the log: The log scan number (40359:103:2) passed to log scan in database <db name> is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup During undoing of a logged operation in database <db name> , an error occurred…
-
-
Login failed for user Reason: Token-based server access validation failed with an infrastructure error Login lacks Connect SQL permission.
Login failed for user Reason: Token-based server access validation failed with an infrastructure error Login lacks Connect SQL permission. Login failed for user ‘localhost\windows_user’. Reason: Token-based server access validation failed with an infrastructure error. Login lacks Connect SQL permission. [CLIENT: <local machine>] Check you have permission to the user, generally we will have permission. Check you are able to access SSMS local & remote. Most of the case issue will be – Check how many group has deny permission, definitely your login will be one of in the group. For our case it was built in user group. SELECT sp.[name],sp.type_desc FROM sys.server_principals sp INNER JOIN sys.server_permissions PERM ON…
-
MS SQL server remote DBA training course topics Chennai India
Microsoft SQL server training course topics: Overview of IT environment with daily DBA activity and health check A brief of history (RDBMS & DBMS) SQL server internal architecture SQL server overview (Editions) SQL Installation overview (System DBs) Review of new features Transact -SQL overview Normalization TABLES AND CONSTRAINTS Standard data types Tables and columns in SQL server Objects, Tables and columns in T-SQL Modifying tables and columns Database diagram architecture Constrains TRANSACT SQL QUIERES Querying SQL server tables SQL and transact SQL Using the select statement Transact SQL built-in function Summary queries Sub queries MERGING DATA WITH JOINS&UNIONS Working with inner joins Using left outer joins Multiplying data with…
-
DR Test Backup and restore drill test
Overview: There was requirement from business to test live server backup into DR server every month / week, not a completed DR. It was about 30+ databases with total of 500 GB. Steps: Add net use command in sp_DatabaseRestore stored procedure Share backup folder path in source server “\” Run the find the recent backup script on source server Script out and run it on target server where you have created sp_DatabaseRestore Run the restore command in SSMS or SQL agent job. Test Restore with execute N parameter and make sure everything is correct and run with Y. I have started using Ola Hallengren’s maintenance script and searched for…
-
Msg 22906, Level 16, State 1, Procedure sp_cdc_enable_db_internal cannot be enabled for Change Data Capture because a database user named cdc
Overview: There was a database restore from production to UAT and the restore was done without Keep CDC option. When developer asked to enable CDC the following was the error. Always keep CDC while restore is best option whether we have CDC or not. use [DB Name] go exec sys.sp_cdc_enable_db Msg 22906, Level 16, State 1, Procedure sp_cdc_enable_db_internal, Line 49 [batch start line 2] The database ‘DBName’ cannot be enabled for Change Data Capture because a database user named ‘cdc’ or a schema named ‘cdc’ already exists in the current database. These objects are required exclusively by Change Data Capture. Drop or rename the user or schema and retry the…