Capture, or show, output from SQL Scripts

[philcart]

A few of our scripts, particularly those run after migration, maintain seed data.

These scripts have standard SQL PRINT statements showing if actions are being taken.
eg:

PRINT 'Inserted n new division codes';

Currently Grate shows the script being executed, but there is no output from the script.

Looking for AfterMigration scripts in "script folder". These scripts will run every time.
--------------------------------------------------------------------------------
 Running 'my script to run.sql'.
--------------------------------------------------------------------------------

Is it possible to have that output show up somewhere?

[erikbra]

Good question. I personally don't have much experience with capturing stdout from SQL scripts back in calling code. But I would guess this is definitely database specific. For SQL Server, it looks like the InfoMessage on the connection can be used. But I'm not sure how to do this on other DB connections.

If we collect info on how to collect the output from each database provider, we could always try to implement this feature, and display it as debug- or trace-level messages, perhaps?