2014-11-19
1,895 reads
2014-11-19
1,895 reads
2014-09-03
1,991 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 Vinay Thakur
Quick Summary for Microsoft SQL Server till 2025, I am fortunate to be part...
By James Serra
Why this comparison feels confusing If you’re a Power BI report author who’s just...
By Steve Jones
I’m not sure I knew identity column values could not be updated. I ran...
I have mentioned this several times over several years. Can someone please help me...
SELECT COUNT(DISTINCT Component) AS Found FROM tblComponents WHERE(Component NOT LIKE '%[a-z]%') AND(LTRIM(RTRIM(Component)) = 'GM13622')...
Comments posted to this topic are about the item Remotely Engineer Fabric Lakehouse objects:...
In a SQL Server 2025 table, called Beer, I have this data:
BeerIDBeerName 1Becks 2Fat Tire 3Mac n Jacks 4Alaskan Amber 8KirinI run this code:
SELECT JSON_OBJECTAGG(
BeerID: BeerName )
FROM beer;
What are the results? See possible answers