Yes. But doing batch has some caveats. First is you have to physically send your data to the MS-SQL server machine in a proper text format, then turn off ALL triggers for the affected tables then do a bulk operation then turn the triggers back on.
Unfortunately, a lot of our server-side business process are done through triggers. Another is that the SQL server is normally not directly accessible. SQL statements are actually sent to the Web Server with an appropriate web service and it has the responsibility of running the SQL statement. MS-SQL bulk operation require that the data file is directly accessible the MS-SQL itself. I haven't tried using URI's or network shares but it does work if you have the data file (delimited by quotes and comma's) on the local hard drive of the server. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of bill lam Sent: Friday, August 22, 2008 8:00 AM To: [email protected] Subject: Re: [Jgeneral] Successfully Migrated to J602 from J601 > My statement implies that J only creates the SQL statement. This is incorrect. Specifically, the C# application retrieves data from the SQL server over the internet and submit all data into the current J session. J now computes everything and just returns a string containing 3 type of SQL-DDL statements which are DELETE, INSERT and UPDATE statements. The C# calling application now has the responsibility of executing/submitting this SQL statements to the MS-SQL Server. Hahaha, I actually saw and instance where ADO.NET choked on a 25,000 SQL-DDL statement generated by J in less than a minute. Does M$-SQL Server support batch? regards, ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
