2009-03-09
3,507 reads
2009-03-09
3,507 reads
Let us look at another means to increase the availability of your highly critical databases. We will extend the concept of filegroups as highlighted in a previous tip on Disaster Recovery Procedures in SQL Server 2005 Part 2 (Isolating Critical Objects) wherein we can use filegroups to isolate and store a critical object.
2008-11-20
3,127 reads
Along with some best practices, SQL Server MVP Hilary Cotter shares a log shipping setup process from start to finish.
2008-04-22
2,862 reads
One of the four high availability technologies in SQL Server is replication, though this can be very cumbersome to setup and get working. Longtime author Paul Ibison looks at how this has changed from SQL Server 2000 to 2005 and what you should consider before setting this up.
2008-04-17
7,791 reads
2007-10-17
2,322 reads
One of the more interesting new technologies in SQL Server 2005 is database mirroring, allowing you to implement high availability on a database with commodity hardware. Jay Dave brings us a nice description of this technology.
2008-06-18 (first published: 2007-07-17)
15,611 reads
One very interesting new feature in SQL Server 2005 is the ability to run backups to multiple locations, ensuring you have a second copy of the backup file if your first one were to be corrupted. SQL Server expert Andy Warren takes a look at how this feature works and the implications of using it.
2008-05-12 (first published: 2007-06-12)
8,479 reads
In this presentation, Brian shows you how you can use database snapshots for data protection. He shows you how to create a snapshot, read from it and lastly how to do a database recovery from the snapshot.
2006-09-27
2,767 reads
By Steve Jones
It’s Prime Day. A few of my recommendations, since I want to do some...
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
If you’ve been watching AI roll through the data community and thinking, “this seems...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Comments posted to this topic are about the item Concurrency and Baseline Control: Level...
Comments posted to this topic are about the item Spending Time in the Office
I have this code on SQL Server 2022. What happens when it runs all at once?
DROP TABLE IF EXISTS dbo.Commission GO CREATE TABLE dbo.Commission (id INT NOT NULL IDENTITY(1,1) CONSTRAINT CommissionPK PRIMARY KEY , salesperson VARCHAR(20) , commission VARCHAR(20) ) GO INSERT dbo.Commission ( salesperson, commission) VALUES ( 'Brian', 12 ), ( 'Brian', 'None' ) GOSee possible answers