Niels Berglund

sp_execute_external_script and SQL Compute Context - III

We use WinDbg, Process Monitor and WireShark to look in detail what happens in SQL Server when we use RxSqlServerData to pull data.

sp_execute_external_script and SQL Compute Context - II

We look in detail why we see performance differences when using SQL Server Compute Context.

sp_execute_external_script and SQL Compute Context - I

A drill-down into how SQL Server Compute Context works when executing sp_execute_external_script.

Microsoft SQL Server R Services - sp_execute_external_script - III

A lowdown of sp_execute_external_script and the @parallel and @r_rowsPerRead parameters, the SQL Server compute context, using Process Monitor and Process Explorer

Microsoft SQL Server R Services - sp_execute_external_script - II

A lowdown of sp_execute_external_script and its @params and @parameter1 parameters, using Process Monitor and WireShark

Microsoft SQL Server R Services - sp_execute_external_script - I

A lowdown of sp_execute_external_script and its different parameters, using Process Monitor and WireShark

Microsoft SQL Server R Services - Internals XX

A drill down, using WinDbg, WireShark, Process Monitor, into how error messages in the external engine is handled by SQL Server.

Microsoft SQL Server R Services - Internals XIX

A drill down, using WinDbg, into how print statements in the external engine together with ack messages comes back to SQL Server.

Microsoft SQL Server R Services - Internals XIII

When is SQL statements executed when executing external scripts?

Microsoft SQL Server R Services - Internals XII

More about the TCP/IPpackets sent from SQL Server to SqlSatellite.