Today one of my colleague reached out to me for an help to drop a subscriber from an publisher which is participating in Always On. We seen same behavior in UI and in T-SQL statement. As a start I was looking online for help to resolve this issue. I found an KB article from Microsoft which describes this is an known issue and fixed in the below versions of SQL Server.
*) SQL Server 2016 SP2 CU1 and above
*) SQL Server 2017 RTM CU7 and above
Category: Troubleshooting
Categories
SSIS Error Code 0xC02092B4
I was working on a SSIS package in SQL 2014 which was working there without any issues. Due to few factors we need to downgrade to work in SQL Server 2008 R2 for few months. I developed the packages in SQL 2008 BIDS and deployed. No changes done to any of the database objects as I thought I’m going to use the same in my package as well.
Question:
Some time back I wrote an article on the new feature that’s added to SQL Server 2012 DTA (database tuning advisor). I have installed SQL Server 2012 on Windows 8 operating system. When I started testing plan cache analysis using DTA , it crashes abruptly with the error message below
I faced an issue during restoration of very large db in our development database server. Issue is restoration takes very long time even though we had latest hardware and recent version of SQL Server (it’s SQL 2008 Ent. Ed). So to troubleshoot it I have used the trace flag 3004 which print all internal things happen during backup and restoration operation.
After a long gap Im writing a article. This article is all about suppressing successful backup information into errorlog. Let me explain my scenario, In my working environment we have a production SQL Server with 60+ databases, all the databases are set to full recovery and data loss is accepted only for 15 min. Yeah you got me, we are taking Full backup daily, differential every 4 hours and transaction log backup every 15 min, there is no problem with the backup. We have one thing that is messing our error log, whenever a backup is taken by default SQL Server will write the detail to the errorlog as shown below.