As you embark on your own Database DevOps journey you are going to hear many new concepts and phrases, but what do they mean and why are they important to consider? Join Grant Fritchey live as he breaks down the key concepts and terminologies around Database DevOps.
2022-10-24
Learn how and why to use THROW in your SQL Server code to be able to better handle errors that may occur during code execution.
2022-10-24
There's still time to register for Summit and unlock access to over 300 sessions. Join peers and industry leaders in the data community homecoming. Get $200 off on the 3-Day Conference pass (in-person) with code REDGATEVIP or 50% off on the 3-Day online pass with code RGVIPONLINE
2022-10-21
2022-10-21
Take on the challenge of deploying database changes every 30 minutes in Redgate's Summit pre-con 'The Journey from Manual Deployments to Database DevOps' on November 15.
Hosted by Steve Jones, Grant Fritchey and Redgate DevOps experts, you'll start with a manual process and slowly implement changes that allow you to reap the benefits of automation.
2022-10-19
Before data can be read from of a SQL Server database table, the table needs to contain rows of data. One of the most typical ways to get data into a table is to use the INSERT statement. One row or multiple rows can be inserted with a single execution of an INSERT statement. You can even use the output of a stored procedure to insert rows. In this article, I will explore the basics of inserting data into a SQL Server table using the INSERT statement.
2022-10-19
Learn how to consume multiple API calls to load data to a SQL Server database using Python.
2022-10-17
The I/O from an instance of the SQL Server Database Engine includes logical and physical reads. A logical read occurs every time the Database Engine requests a page from the buffer cache. If the page is not currently in the buffer cache, a physical read first copies the page from disk into the cache.
2022-10-17
Maintaining a version of a database opens a lot of possibilities, especially if an automated process can easily grab the current version, at runtime, using just SQL. You might, for example, have a routine that is only appropriate after a particular version. It is also very handy to be able to associate entries in an event log or bug report with the database version. No more desultory quests, when dealing with support issues, or when bug fixing, to find which database version was running when the bug happened.
2022-10-14
Learn how to configure and deploy a new Amazon AWS RDS SQL Server instance with this step-by-step article.
2022-10-14
By HeyMo0sh
As a DevOps professional, I’ve seen firsthand how cloud costs can quickly spiral out...
By Steve Jones
AI is everywhere. It’s in the news, it’s being added to every product, management...
By Vinay Thakur
RAG — Retrieval Augmented Generation. we have covered so far — embeddings, vectors, vector...
Hi, ssms is free here. I can think of other reasons to do this...
I've written some documentation on using different Markdown types of files on GitHub. It's...
Comments posted to this topic are about the item Not Just an Upgrade
I am doing development work on a database and want to keep a backup so I can reset my database. I make some changes and want to restore over top of my changes. When I run this code, what happens?
USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO USE DNRTest GO CREATE TABLE MyTest(myid INT) GO USE master RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACESee possible answers