Cloud First
SQL Server 2016 is the first cloud first version of SQL Server being released as the on-premise product.
SQL Server 2016 is the first cloud first version of SQL Server being released as the on-premise product.
In this new article, we will show how to use the SSIS term lookup transformation tool.
Manvendra Singh explains step by step how to change the server level collation setting for an existing SQL Server instance.
Using Resource Governor on a SQL Server that suffers from CPU contention thus allowing us specify limits on the amount of CPU that an incoming request can use.
In theory, it is easy to determine whether data is equal to, greater than or lesser than a value. Real-world data types can be surprisingly tricky, even for gauging data equivalence. Because SQL cannot remain aloof from any application's data types, you need to be aware of the ways and pitfalls of individual datatypes and how you can test for equality, equivalence, similarity, identity and all that jazz. Joe Celko discusses.
Phil Factor recounts the most important lesson of his early IT career: try not to burst into giggles when you get to look at the client's IT system.
With SQL Powershell, you can check all your database backups in minutes, whether you have ten SQL servers or 100.
Paul Randal continues his knee-jerk performance tuning series, focusing on ways to optimize performance when using temporary tables.
By HeyMo0sh
As a DevOps person, I know that to make FinOps successful, you need more...
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...
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