Lowell (6/14/2013)

---

Ed Wagner (6/14/2013)

---

I've always done this using a .NET application and found it far easier than trying to force it with T-SQL. The first big hurdle in doing it with T-SQL is that the image has to be accessible in the file system on the SQL Server. This makes is generally not very useful for user applications.

That being said, Lowell, thank you for the link. It's definitely something I'm interested in and will check out.

I've done it the same way Ed; typically doing it in /adding that kind of functionality to an application or website.

I've had a few one-off issues, like "export all these documents stored in the database to disk" for various biz reasons, and a simple loop and doing it in TSQL makes sense in those cases, but the main reason you identified: not useful to end users is a rock solid reason to not do it in TSQL. the above is nice to have in your toolbox, but not required.