2014-11-19
1,896 reads
2014-11-19
1,896 reads
2014-09-03
1,992 reads
In SQL Server 2005 and earlier, it is not possible to pass a table variable as a parameter to a stored procedure. When multiple rows of data to SQL Server need to send multiple rows of data to SQL Server, developers either had to send one row at a time or come up with other workarounds to meet requirements. While a VB.Net developer recently informed me that there is a SQLBulkCopy object available in .Net to send multiple rows of data to SQL Server at once, the data still can not be passed to a stored proc.
2008-08-11
3,885 reads
In previous versions of SQL Server, it has not been possible to pass a table variable, as a parameter, to a stored procedure. Microsoft introduces table-valued parameters, along with other features, in SQL Server 2008. This article illustrates the function and usage of table-valued parameters.
2008-06-02
2,812 reads
By Steve Jones
I don’t have SQL Server installed on my laptop. In an effort to keep...
Slow-running queries can degrade your Redshift cluster’s performance and lead to increased costs. Identifying...
By gbargsley
If you've been here before, you know this blog is usually about SQL Server,...
Hi all Can I get some perspective from the community please on performing in-place...
Comments posted to this topic are about the item How Long is a Long...
Comments posted to this topic are about the item T-SQL Trigonometric Functions in SQL...
In SQL Server 2025, a long I/O is recorded in the error log with message 833. How long much an I/O request be outstanding before this message is written to the log?
See possible answers