﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / SQL Server 2005 / SQL Server 2005 Strategies  / Trigger with OSQL / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Sat, 18 May 2013 22:25:26 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Trigger with OSQL</title><link>http://www.sqlservercentral.com/Forums/Topic1370139-361-1.aspx</link><description>I agree with the advice to use something other than a direct call inside the transaction. Write the data you need to export to a table and then have an external process do the actual export. Service Broker would work. A plain-old "work table" could work too.As an aside, osql.exe has been deprecated since SQL 2005 was released. sqlcmd.exe is the replacement for it. Further to that osql is not really the right tool for exporting data. If you want a command line tool use bcp.exe but SSIS is usually my preference for this type of work.</description><pubDate>Mon, 08 Oct 2012 22:16:25 GMT</pubDate><dc:creator>opc.three</dc:creator></item><item><title>RE: Trigger with OSQL</title><link>http://www.sqlservercentral.com/Forums/Topic1370139-361-1.aspx</link><description>I would not be attempting to execute an external program from within a transaction - there are many potential problems including security (which I suspect may be your current problem) and, potentially, performance.Personally, I would log sufficient information for the file to be written asyncronously and use completely separate process (that read the log) to actually write the files.  There are many options for implementing this including SSIS and also OSQL perhaps scheduled for execution using SQL Server Agent.  Another option is to implement the writing of the files using Service Broker.</description><pubDate>Mon, 08 Oct 2012 21:24:42 GMT</pubDate><dc:creator>happycat59</dc:creator></item><item><title>Trigger with OSQL</title><link>http://www.sqlservercentral.com/Forums/Topic1370139-361-1.aspx</link><description>Hi,I have a requirement as below,1) whenever a column in a table gets updated with a value then i have to join few more tables and get related data and generate a file with that.2) file should be created in windows server at a specified pathOur approach:1) we created a trigger which does data fetching and calls OSQL - not working as it hangs2) A trigger which calls an SP which inturn calls a OSQL to generate a file  - not working as it hangsAny ideas?Thanks in advance</description><pubDate>Mon, 08 Oct 2012 20:49:06 GMT</pubDate><dc:creator>Compassionate</dc:creator></item></channel></rss>