Cambridge, UK, 2 July 2015 – Redgate, the SQL Server and .NET software company, returns to London and Seattle in October with its enormously popular training event, SQL in the City.
2015-07-03
503 reads
This metric measures the amount of memory used by the total number of ad-hoc queries that are currently in the plan cache. If the value is high, it indicates memory is being wasted by storing the execution plans of queries that will never be run more than one time.
2015-06-25
2,334 reads
Redgate is researching how people deploy their database changes. This is a very quick survey, and there's an opportunity to sign up for a research call in exchange for a $50 Amazon voucher.
2015-06-16
3,886 reads
This metric shows Writelog wait time in ms, per elapsed second. Writelog wait types occur when the log cache is being flushed to disk. If this happens all the time, it may suggest disk bottlenecks where the transaction log is stored.
2015-06-09
2,958 reads
Each year SQLServerCentral runs a survey to get some insight into what who our readers are, what they like about the site, and what can be improved. Please take a few minutes to complete this survey by June 12 and get the opportunity to win one of three $50 Amazon vouchers.
2015-06-02 (first published: 2015-05-26)
13,214 reads
The MidnightDBA team is announcing the release of a new, free backup solution for SQL Server: Minion Backup. We created Minion Backup (or MB, for short) to be the most flexible, feature-rich backup solution possible.
2015-06-01
1,611 reads
This is a good general indicator of performance problems. High stall times indicate I/O problems, which can be attributed to busy physical disks or queries that return large data sets to the client.
2015-05-26
6,171 reads
Join Brian A. Randell, Grant Fritchey and Steve Jones in this panel discussion to hear tips, ideas and share your questions on managing application and database deployments with continuous delivery. This Free webinar will be on May 27th at 4PM BST, register while space is available.
2015-05-26 (first published: 2015-05-21)
13,036 reads
Join this workshop on July 8, 2015 to learn how to: link your source control repository to a build system, trigger database builds automatically when you make a change, use DLM tools to test your database changes, and lay the foundations for package-based deployment of your database. Register while space is available.
2015-05-22
6,320 reads
This free guide includes worked examples, practical advice, and covers the hows and why of SQL Server monitoring. Download the guide and get a 26 monitoring tips as well.
2015-05-20
10,591 reads
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
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