<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>SQL Server on Daniel Genezini</title><link>https://genezini.com/tags/sql-server/</link><description>Recent content in SQL Server on Daniel Genezini</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>2022 Daniel Genezini All rights reserved</copyright><lastBuildDate>Mon, 15 May 2023 06:00:00 -0300</lastBuildDate><atom:link href="https://genezini.com/tags/sql-server/index.xml" rel="self" type="application/rss+xml"/><item><title>How to run scripts on SQL Server container startup</title><link>https://genezini.com/blog/p/how-to-run-scripts-on-sql-server-container-startup/</link><pubDate>Mon, 15 May 2023 06:00:00 -0300</pubDate><guid>https://genezini.com/blog/p/how-to-run-scripts-on-sql-server-container-startup/</guid><description>&lt;img src="https://genezini.com/blog/p/how-to-run-scripts-on-sql-server-container-startup/cover.jpg" alt="Featured image of post How to run scripts on SQL Server container startup" /> Unlike MySQL and PostgreSQL, which execute scripts in the /docker-entrypoint-initdb.d/ directory after initialization, the SQL Server container image doesn't provide a built-in mechanism for running scripts at startup.
In this post, I'll show how to create a custom container image that waits for SQL Server startup and runs a pre-configured script. In addition, I'll show how to use this custom image to run SQL Server in Testcontainers.</description></item></channel></rss>