sql server

The third article in the series about SQL Server backup and restore will take us through the database restore process and demonstrate the two main principles of database restore available in Microsoft.

Now that we have reviewed the backup basics in the first article of our series dedicated to SQL Server backup, let’s proceed to the implementation and automation of the SQL Server backup process.

The importance of database backup and restore can be neither underestimated nor ignored. And since your data is subject to modification, the primary task is to ensure its safety and mitigate the risks of data loss.

Extended Events is a helpful and convenient solution designed to monitor your system performance. First introduced in SQL Server 2008, it has become the global default solution. SQL Server Extended Events apply to the DBMS state monitoring and help DB developers or DBAs to collect information, view it, and analyze it.

The data stored in the history of queries are among the most valuable for any DBA. Tracking back the SQL Server query history is a must in many cases. For instance, there might be a need to investigate a particular work case, check the backup history, or recover a specific query if your SQL Server suffers a crash.

Database synchronization is an everyday necessity. You need it regularly when you have several similar databases that serve the same “user.”

For 15 years, SSMS has held the title of the top SQL Server database tool. That’s no easy feat, especially in the software world, where things can change faster than you say “blueberry pie.” But then a contender emerged, developed and released by the same Microsoft folks in 2018. It was Azure Data Studio – obviously less mature, weaker in terms of database administration, yet very promising and eager to win its audience. And today, we’re going to put them face to face and find out who’s better.

In the process of software product development that involves a database, one of the key points is the possibility of continuous delivery of changes from the development environment to the production environment.

Unit testing is an essential component of the database DevOps process. Its primary goal is to test the constituent parts of the database objects in order to identify any malfunctions or flaws early in the project. This approach allows database developers to ensure the changes they have made are verified, and the project will work properly. In our article, we will mainly focus on unit testing a stored procedure in a SQL Server database and exemplify how simple it is to conduct unit tests with the dbForge Unit Test tool.

In our fast-changing world, observations of certain events, operations, and processes determine the development of business and implementation of any solutions or ideas. Such observations are captured in the form of data usually stored and processed in a database.