Tag Info

New answers tagged


This is the solution I came up with: Enable xp_cmdshell with EXEC sp_configure 'show advanced options', 1 COMMIT GO RECONFIGURE GO EXEC sp_configure 'xp_cmdshell', 1 COMMIT GO RECONFIGURE GO If needed create a directory with xp_cmdshell to get the needed permissions. EXEC master..xp_cmdshell 'mkdir C:\exportdir' Use BCP with queryout EXEC ...


Does it need to be done in real time? I would engineer the solution differently. The client uses a stored procedure to write to a queue table with what needs to be compressed. A script running on the server periodically checks the queue table and zips up everything that needs to be zipped up, marks it as complete and does whatever else needs to be done.


For #1: Maybe could use xp_cmdshell with a proxy acct initiate zip, or something more "modern" :) with powershell For #2: Maybe OPENROWSET ? http://msdn.microsoft.com/en-us/library/ms190312.aspx


As always, It will depend on how much money are you able to spend. (may I say "invest"?) Although the feature of storing binary files into Oracle is included in all Database editions, storing binary files into the database will increase hardware and human resources costs since your db will become bigger and bigger, and it's very common in these cases that ...


Have you considered Oracle's BFILE ? Sounds like it's a perfect fit for you; http://www.orafaq.com/wiki/BFILE Here's some further reading material on the subject ; http://docs.oracle.com/cd/B10501_01/appdev.920/a96591/adl12bfl.htm


My strong advice (regardless of the RDBMS): store the files separately. This makes a much smaller database, important when you backup, migrate, replicate etc. Additionally, you can separate db and files on different disks, having so much more control over storage locations (e.g. disk subsystems with different fail-over strategies). This means however, you ...

Top 50 recent answers are included