What is the best practice to deploy update in a cloud database table

RE: What is the best practice to deploy update in a cloud database table

Srinivas Thota — Fri, 26 Apr 2024 06:00:43 GMT

Hi edmondx0001,

When you deal with database scripts either in manual or automation scripts, I recommend using idempotent SQL Scripts as per Database best practices for deployment, which can be call as rerunnable script. These scripts can be used for creating table, alter, create view and other scripts use of which of information_schema. This will use be useful when you use third party automation pipelines. As per your problem statement i recommend you use replace keyword instead of insert.
below is example of idempotent sql script.

IF (

(

SELECT CASE --return 0 if not nullable 1 if nullable

(--return null if it doesn't exist

SELECT IS_NULLABLE

FROM INFORMATION_SCHEMA.COLUMNS

WHERE TABLE_SCHEMA = 'dbo'

AND TABLE_NAME = 'prices'

AND COLUMN_NAME = 'Edition_id'

) WHEN 'NO' THEN 0

WHEN 'YES' THEN 1 ELSE -1 END

) = 1

)

BEGIN

IF NOT EXISTS (SELECT 1 FROM prices WHERE Edition_id IS NULL)

ALTER TABLE dbo.prices ALTER COLUMN Edition_id INT NOT NULL;

END;

RE: What is the best practice to deploy update in a cloud database table

Karumuru Abhishek — Fri, 26 Apr 2024 05:24:47 GMT

Hi edmondx0001 I would always recommend having a backup of your data when you are running scripts in the database. When you prepare scripts for your target Env, try running them a couple of times in dev and make sure your that your script gives you the expected output. Before deploying the scripts check the data in the target env take back up the data compare the data make necessary changes. Also, make sure if you are using any conditions they should not affect other data in your table

RE: What is the best practice to deploy update in a cloud database table

Konduru Chaitanya — Fri, 26 Apr 2024 05:11:26 GMT

If you are confident about the scripts that you have run in the dev, You can upload the same scripts in the package that you will be deploying to higher environment. Else, try taking a back up or complete export of what is there in the higher environment and then do the deployment for scripts. Also if its an insert statement with no primary keys, I would recommend updating the Scripts with the Primary keys and then proceeding with the deployment.

RE: What is the best practice to deploy update in a cloud database table

SRINIVAS M — Fri, 26 Apr 2024 03:58:39 GMT

Hi,

Create SQL scripts for your changes in the dev environment.
Back up the QA database before applying any changes.
Run the SQL scripts in the QA environment to replicate the dev changes.
Verify the updates in QA before considering deployment to production.

Creating SQL scripts of your database changes, backing up your QA database, running the scripts in QA, and verifying the updates before moving to production while using version control for script management is a best practice for deploying updates across environments.

RE: What is the best practice to deploy update in a cloud database table

Shubham Aware — Fri, 26 Apr 2024 02:08:28 GMT

Hello edmondx0001

I recommend that while inserting data into the development environment, you create an SQL script. Please take note of it and run the same insert SQL script in the targeted environment's database with the proper timestamp. Manage those scripts for future reference.