2014-11-19
1,892 reads
2014-11-19
1,892 reads
2014-09-03
1,985 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
Here’s how these tools can make Kubernetes security easier and help you avoid common...
By Steve Jones
lackout – n. the sudden awareness that you’re finally over someone, noticing that the...
By Ed Elliott
All Spark Connect Posts I have just finished an update for the spark connect dotnet...
Comments posted to this topic are about the item Shades and Reflecting on SQLBits...
In Azure SQL DB, i want to merge records from the staging table to...
Full error message: SSRS error: The Value for the image 'Image1' has a constant...
I have a table, called dbo.logger, in SQL Server 2022. I decide to add two new columns to this table with this code.
ALTER TABLE dbo.logger ADD CreateDate DATETIME CONSTRAINT dfGetDate DEFAULT GETDATE() GO ALTER TABLE dbo.logger ADD ModifyDate DATETIME DEFAULT dfGetDate GOWhat happens when I run these two batches? See possible answers