You are exploring high availability and disaster recovery options and want to know more about SQL Server Availability Groups. What are some of the Frequently Asked Questions about SQL Server Availability Groups?
Please read the latest MSSQLTips post: “SQL Server Availability Groups: Your FAQs Answered“.
Check out all of my tips here: http://www.mssqltips.com/sqlserverauthor/94/svetlana-golovko/.
Check out these SQL Server Agent FAQs to help you get started with this key component of SQL Server.
Please read the latest MSSQLTips post: “SQL Server Agent FAQ“.
Check out all of my tips here: http://www.mssqltips.com/sqlserverauthor/94/svetlana-golovko/.
Please read the latest MSSQLTips post: “Database Administrator Frequently Asked Questions“.
Check out all of my tips here: http://www.mssqltips.com/sqlserverauthor/94/svetlana-golovko/.
Learn about Microsoft Kerberos Configuration Manager and how to use it and for what.
Please read the latest MSSQLTips post: “Kerberos Configuration Manager for SQL Server SPN Validation“.
Check out all of my tips here: http://www.mssqltips.com/sqlserverauthor/94/svetlana-golovko/.
How can we configure transactional replication without primary keys?
Please read the latest MSSQLTips post: “SQL Server Transaction Replication for Tables without a Primary Key“.
Check out all of my tips here: http://www.mssqltips.com/sqlserverauthor/94/svetlana-golovko/.
How to migrate our SQL Server Analysis Services (SSAS) instances from SQL Server 2012 to SQL Server 2017. What are the steps?
Please read the latest MSSQLTips post: “SSAS Migration from SQL Server 2012 to SQL Server 2017“.
Check out all of my tips here: http://www.mssqltips.com/sqlserverauthor/94/svetlana-golovko/.
Recommendations for hardening the SQL Server installation for the configuration where SQL Server is only accessible by the application installed on the same server.
Please read the latest MSSQLTips post: “SQL Server Security Best Practices for an Application“.
Check out all of my tips here: http://www.mssqltips.com/sqlserverauthor/94/svetlana-golovko/.
SQL Server security monitoring is a critical part of the Database Administrator’s job. Some security related alerts could be setup very easy, but others require third-party tools or extra steps to setup. For example, SQL Server Audit can be used to monitor logins or users modification, but it requires audit log review. We would like to get real-time alerts every time a login or a user is created or added to a server or a database role, how can this be done?
In this tip we will provide steps and scripts for setting up WMI alerts and jobs responding to these alerts to monitor the creation and removal of users and logins as well as server and database roles membership changes.
Please read the latest MSSQLTips post: “Alerts and Notifications for SQL Server Login, Database User and Role Membership Changes“.
Check out all of my tips here: http://www.mssqltips.com/sqlserverauthor/94/svetlana-golovko/.
Central Management Server (CMS) is a SQL Server feature that allows you to manage multiple SQL Servers at the same time. You can run T-SQL scripts or execute Policy-Based Management policies on multiple servers. You can also group SQL Servers and run the scripts on a specific group of SQL Servers.
How else can CMS be used? How can we overcome some of the limitations when we run queries against CMS Server Groups?
In this tip we will show you a couple of CMS tricks. In our examples below we will show how you can sort the CMS query results for different scenarios. We will also provide a couple of examples of alternative uses of CMS.
Please read the latest MSSQLTips post: “Different ways to sort multi-server SQL Server query results using Central Management Server“.
Check out all of my tips here: http://www.mssqltips.com/sqlserverauthor/94/svetlana-golovko/.
2018 started out with bad news for most IT professionals. A new “speculative execution side-channel attacks” vulnerability affected many modern processors and operating systems. This vulnerability is very complex and requires patching on many layers, including hardware, operating systems and the application layer.
Database Administrators (DBAs) have to be prepared to patch every SQL Server starting with SQL Server version 2008 and the recommended patching procedure is different for different servers depending on SQL Server configuration settings and features used.
How can we determine what servers are affected and what steps should we take to protect SQL Server?
In this tip we will provide a “Meltdown/Spectre SQL Server Assessment Script” that you can run in Central Management Server (CMS) against all of your SQL Servers. This script will produce a report with recommendations/scenarios for patching and display configurations/features that are not secure and enabled on SQL Server.
Then we will provide a couple of remediation steps to review unsecure use cases.
After remediation we will run the Main Assessment Script again and review the final recommendations.
Please read the latest MSSQLTips post: “SQL Servers Assessment for the Meltdown and Spectre Vulnerabilities“.
Check out all of my tips here: http://www.mssqltips.com/sqlserverauthor/94/svetlana-golovko/.