Testcontainers-java: Add specialized container support for SQL Server

[axelfontaine]

Based on https://hub.docker.com/r/microsoft/mssql-server-linux/

[martin-g]

Like this https://github.com/testcontainers/testcontainers-java-module-mssqlserver ?

[axelfontaine]

Yes! Perfect! Thanks!

Then consider this issue like a bug report for the docs :-)

[axelfontaine]

Also note that this one is missing from Maven Central. Which I feel is yet another argument in favor of #431.

[kiview]

I see you're point, but mssqlserver module was actually a real 3rd party contribution we've integrated.
I'm not a big fan of making testcontainers itself bigger, since I'm for example looking forward to integrate testcontainers with testcontainers-spock without the JUnit dependencies :wink:

[axelfontaine]

@kiview This big difference here is that specialized containers do not add additional dependencies. Only 2 classes, which is at most 1-2 kb of bytecode before compression.

[kiview]

Point taken. Maybe we should further discuss this topic in #431.
Also in the other hand, it would help to have either a curated list of plugins, or mention the Github organization for further specialized containers.

[StefanHufschmidt]

@axelfontaine maybe there will be an extension for the MSSQL module where you can pass a SQL-script which will be initially executed on the container e.g. for a specific database structure. This extension will probably need the client library for MSSQL. The client for MSSQL is not that small I guess so I would prefer to choose each module which I need for my project.

[axelfontaine]

@StefanHufschmidt Not necessary. sqlcmd is already present in the Docker image and can be used as described in the "Connect to Microsoft SQL Server" example from the docs at https://hub.docker.com/r/microsoft/mssql-server-linux/

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this is a mistake, please reply to this comment to keep it open. If there isn't one already, a PR to fix or at least reproduce the problem in a test case will always help us get back on track to tackle this.

[stale[bot]]

This issue has been automatically closed due to inactivity. We apologise if this is still an active problem for you, and would ask you to re-open the issue if this is the case.