In SQL Server it is generally a good idea to use temporary tables, rather than table variables within your stored procedures. Temporary tables perform much better, particularly with large volumes of data, as SQL Server is able to compile statistics on the data in temporary tables. However, if you are calling your stored procedures from a Powerbuilder application, you may find that the switch to temporary tables has an unwanted side effect. Here is how the unwanted side effect comes around and what to do about it.
Avoid Potential SQL Server tempdb log file issue when switching from Table Variables to Temporary Tables in a Stored Procedure called by a Data Window retrieval
- Written by David Lacey
- Category: PowerBuilder
- Hits: 3208