SQL Server Blogs

AlwaysON

-> Disaster Recovery Using AlwaysON Availability Group – Scenario 1
-> Disaster Recovery Using AlwaysON Availability Group – Scenario 2
-> Configuring Read Only Routing List for AlwaysON Availability Group
-> Reporting Services using AlwaysON Availability Group
-> Difference between Readable Secondary setting Yes and Read Intent only
-> Moving all Availability Groups in the Event of a Single Availability Group Failover
-> AlwaysON – Login Synchronization across Replicas
-> AlwaysON – Working through Crashed Synchronous Secondary Replica
-> Creating Linked Server to a Multi-Subnet Availability Group Listener with ReadOnly routing
-> AlwaysON – How to disable Read-Only routing for an Availability Group
-> AlwaysON – Unable to access the ‘JB1’ database because no online secondary replicas are enabled for read-only access. (Microsoft SQL Server, Error: 982)

Azure

-> Creating a SQL database in Microsoft Azure portal
-> Restore on-Premise SQL server database to Azure SQL Database

CORE

-> Hide Instance set to YES in SQL server Network Configuration
-> Server TCP provider failed to listen on [1519]. Tcp port is already in use.
-> Using certificates with SQL server

PERFORMANCE

-> SQL Server Parameter Sniffing
-> @@FETCH_STATUS -9
-> What DBCC SHOW_STATISTICS tells me
-> Install and Configure PSSDIAG
-> Install and Configure SQLNexus
-> Trace Flag 7471
-> Tempdb contention
-> Optimize for ad hoc workloads
-> Column data may be deleted when you update another variable-length column in a table of a database upgraded from SQL Server 2005
-> Why Bookmark Lookup is BAD?

REPLICATION

-> Cannot insert an explicit value into a timestamp column. Use INSERT with a column list to exclude the timestamp column, or insert a DEFAULT into the timestamp column.

SETUP

-> Database ‘model’ cannot be opened. It is in the middle of a restore.
-> SQL resources not coming online after patching
-> The database owner SID recorded in the master database differs from the database owner SID recorded in database ‘msdb’. You should correct this situation by resetting the owner of database ‘msdb’ using the ALTER AUTHORIZATION statement.

-> SQL services fails after applying service pack

STRETCH DATABASE

-> Stretch Database in SQL Server 2016
-> Adding a table to the stretch database
-> Disabling Stretch Database
-> Stretch database – Modifying the filter function

Advertisements