Natively Compiled Stored Procedures: What they are all about
What are natively compiled stored procedures? Why would we want to use them and what are the performance benefits of using them over classic disk-based stored procedures?
What are natively compiled stored procedures? Why would we want to use them and what are the performance benefits of using them over classic disk-based stored procedures?
This week Steve Jones looks at the formal way in which you might verify changes to your system. Do you have a process?
Denzil Ribeiro looks at the validation phase of transaction lifetime.
A brief comparison of three different JDBC Drivers built for connecting with MySQL
Branching code creates complexity to development and should be undertaken with caution.
What are your options for connecting to an Azure VM? Sure, a Remote Desktop Protocol (RDP) connection will get you started but you'll soon need a full secure VPN connection. Azure can provide three different options for doing this: Point-to-Site (P2S), Site-to-Site (S2S), and ExpressRoute, but what are their relative advantages, and which one is right for the way you need to use Azure?
This level starts with an overview of how versioning works in Git, a DVCS, and suggests a sensible database project versioning strategy. It then offers some simple, but illustrative, practical examples showing how to share database changes and deal gracefully with any conflicting changes.
Atul Gaikwad details the differences between DELETE and TRUNCATE, including how they vary in terms of being rolled back.
Steve Jones notes that some features aren't fully developed, but that's not a reason to avoid releasing them.
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