2014-11-19
1,894 reads
2014-11-19
1,894 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 Steve Jones
Last week I spent a few days in Cambridge, UK for the Redgate Company...
By Steve Jones
Recently I had someone internally ask about whether SQL Source Control supports Git Hooks....
By Steve Jones
At Redgate, we’re experimenting with how AI can help developers and DBAs become better...
I'm running a group MSA for the database engine and SQL Agent in a...
All, My query is as follows: SET DATEFORMAT dmy SELECT p.query_id, DATEADD(MICROSECOND,-rs.max_duration,rs.first_execution_time) AS starttime,...
Comments posted to this topic are about the item Encoding Strings
I have this code in SQL Server 2025. What is the result?
DECLARE @message VARCHAR(50) = 'Hello SQL Server 2025!'; DECLARE @encoded VARCHAR(MAX); SET @encoded = BASE64_ENCODE(@message); SELECT @encoded AS EncodedResult;See possible answers