SQL Server has a rock solid backup and restore routine. However, it is not the most efficient way of handling the backups and restores. Neither in terms of time or space required. A number of software vendors have developed their own additions to SQL Server that accelerate or compress the backups (or both). New Author Wesley Brown has taken four of these products into his environment and run some comparisons. Read part one of his review.
With some recent hubub and questions, Steve Jones decided to spend a few moments welcoming everyone to the community and give some background on what this site is all about.
SQL Server clusters are great tools to ensure that your servers are highly available. However there are some times when you'll want to manually perform a failover for testing, maintenance, etc. New author Anthony Bressi brings you a technique and code to allow you to use VB 6.0 to build a small program to automatically do this.
If you are running Microsoft SQL Server databases to support critical enterprise applications, you are part of a growing trend. The cost/performance benefits of Microsoft SQL Server on the Microsoft Windows NT and Windows 2000 platforms have fueled the growth of SQL Server as a platform for enterprise-class applications.
Transactions in SQL Server are probably no more complicated than those in other RDBMS products, which is to say they are fairly complex. Don Peterson continues with part 3 of his series and takes a look at transaction isolation levels and how they interact with multiple connections and their impact on locking.
This is the twenty-fifth article of the series, MDX Essentials. The series is designed to provide hands-on application of the fundamentals of the Multidimensional Expressions (MDX) language, with each tutorial progressively adding features designed to meet specific real-world needs.
SQL Server 2000 is easy to administer relative to other RDBMS, but there is still plenty of room for improvement. Author Andre Vigneau has built a database toolkit to allow him to manage his cross platform databases. This is the second article in his series and deals with establishing connections to any database platform.
Have you ever wondered if you could start the execution of a stored procedure (SP) asynchronously from some T-SQL code? What I mean is starting the SP in the background and continuing on with the next line of code in your T-SQL script without waiting for the execution of the SP to complete. If so, then this article might be of some interest to you.
The default location for the SQL Server system databases doesn't always meet the standards of many organizations. Author Chris Hedgate has taken the time to put together a short checklist on how you can move the master, msdb, model, and tempdb databases easily.
The system table, "sysperfinfo," is the representation of the internal performance counters of SQL Server. This article demonstrates how to retrieve and store information from "sysperfinfo" to a CSV file, so that it can be analyzed.
By Brian Kelley
If your organization is spending money, then meaningful results are a must. Pen testing...
By HeyMo0sh
In my experience, FinOps success has never been just about tools or dashboards. It...
By HeyMo0sh
As a DevOps person, I know that to make FinOps successful, you need more...
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers