InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comTue, 21 May 2013 02:11:52 GMT20http://www.sqlservercentral.com/Forums/Topic440096-8-1.aspxAs Steve said before, [b]DO NOT USE TRIGGER[/b] !!!!!Wed, 09 Jan 2008 08:24:14 GMTLonerhttp://www.sqlservercentral.com/Forums/Topic440096-8-1.aspxHiya folks, thanks for your responses. So... does anybody know why the error[b]The current transaction could not be exported to the remote provider. It has been rolled back.[/b]is occurring and how we can fix it? That would be a problem solved.ThanksRobWed, 09 Jan 2008 07:39:58 GMTrclarksonhttp://www.sqlservercentral.com/Forums/Topic440096-8-1.aspxIn MS Excel go to Data -> Import External Data -> New Database Query.Follow instructions in the wizard to create a query to your database.Tue, 08 Jan 2008 19:41:39 GMTSergiyhttp://www.sqlservercentral.com/Forums/Topic440096-8-1.aspxExporting to spreadsheet is "Death by SQL"... if someone opens it, BOOM! Process in SQL is dead... period.Tue, 08 Jan 2008 18:45:56 GMTJeff Modenhttp://www.sqlservercentral.com/Forums/Topic440096-8-1.aspxI would create a table that holds a flag.Have your trigger set the flagSet up a schedule job that runs every minute or so with a task that saysIF EXISTS(SELECT 1 FROM dbo.FlagTable WHERE Flag=1)BEGINUPDATE dbo.FlagTable SET Flag=1exec your queryENDThe alternative is to have the trigger start your job but you need to put the check in place to detect if your job is running already. There is a system management view for this but its name escapes me.Tue, 08 Jan 2008 12:47:37 GMTDavid.Poolehttp://www.sqlservercentral.com/Forums/Topic440096-8-1.aspxFirst, triggers are inside the transaction and putting something that needs external resources (send mail, openrowsource, etc.) is a bad idea. You are asking for lots of issues.Insert the row into a table and then periodically, even every minute, run an export with SSIS to throw this into your spreadsheet.Tue, 08 Jan 2008 09:07:30 GMTSteve Jones - SSC Editorhttp://www.sqlservercentral.com/Forums/Topic440096-8-1.aspxHiya all, this is my first post here. I hope you can help me. I have a trigger attached to a table that will export data to an Excel spreadsheet when a record is inserted to that table. When I insert the record, I get the following error:[b]The current transaction could not be exported to the remote provider. It has been rolled back.[/b]The script I am using is below:Insert into OpenDataSource ( 'Microsoft.Jet.OLEDB.4.0', 'Data Source=C:\ITTeam\Excel\Book1.xls;Extended Properties=Excel 8.0' ) ...[Sheet1$] SELECT * FROM CUSTOMERSI think the script is OK because it works when:1. I execute the script from a SqlClient.SqlCommand object within a VB .Net application2. If I place the script in a stored procedure and execute it from a VB .Net application.Thanks in anticipationRobTue, 08 Jan 2008 08:43:26 GMTrclarkson