Evgeniy Gribkov posts

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.”

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.

We quite often face the task of migrating database directory data. And the database for a recruitment service, which we created in the previous series of articles, is no exception. In this article, we are going to demonstrate how you can export data to a .sql file and then import it to the target database. Is it worth mentioning that you can either migrate the whole database or certain objects depending on your purpose.

The present article deals with one of the bottlenecks in the work of database developers and administrators, namely the occurrence of invalid objects and the ways of finding them in the SQL Server database.

Hello and welcome to the fourth part of our series of articles that will help you discover how to design and work with databases. This time we are going to delve into an intricate matter of data and object search in SQL Server, which will be further conducted first with the help of standard scripts and after that, using the dbForge Search tool.

In the previous articles, we studied the basic rules of SQL database design, created a database schema diagram for a recruitment service, and filled the newly-created database with test data on employees.