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.
The post The Basics of Inserting Data into a SQL Server Table appeared first on SQLServerCentral.

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.
The post Join the Redgate pre-con at PASS Data Community Summit appeared first on SQLServerCentral.

Learn how you can easily analyze the data lineage in your SQL Server database.
The post Data Lineage Scripts for Microsoft SQL Server and Azure SQL appeared first on SQLServerCentral.

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.
The post SQL Server Internals: Reading Pages appeared first on SQLServerCentral.

Learn how to consume multiple API calls to load data to a SQL Server database using Python.
The post Load Data Asynchronously to SQL Server via an API and Python appeared first on SQLServerCentral.

Learn how to create user defined functions in PostgreSQL.
The post PostgreSQL User Defined Functions appeared first on SQLServerCentral.

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.
The post Finding the Version of a Flyway-managed Database Using SQL appeared first on SQLServerCentral.

Learn how to configure and deploy a new Amazon AWS RDS SQL Server instance with this step-by-step article.
The post Steps to Quickly Configure an AWS RDS SQL Server instance appeared first on SQLServerCentral.