Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • This seems to be reversed, you can send emails from production but not from development? Commented Jul 15, 2019 at 18:27
  • I know it's reverse scenario here...unfortunately!!!....Yes... Commented Jul 15, 2019 at 18:44
  • I don't get why you can't send dbmail from pre-prod, but your first idea of writing to a log file, and then scheduling a ps or batch job to send an email with the log contents could be a viable option. Commented Jul 15, 2019 at 19:13
  • Since this seems to be a security related thing, whatever you come up with should be run by the security team. That said, other than the save to disk (probably a shared common drive would be better, not on the SQL Server itself) and send, if there is another machine that has mailing privileges and can run a query from against the Dev machine to generate the report (via linked server for example) and mail it from there, that would be an easier solution than dump to disk and send. Commented Jul 15, 2019 at 19:27
  • Can you have a linked server from Prod to PreProd? Commented Jul 16, 2019 at 4:23