2023-12-01
406 reads
2023-12-01
406 reads
Step-by-step guide to solve the "INSERT EXEC cannot be nested" problem by using a CLR when unit testing stored procedures using the tSQLt framework.
2022-08-19
31,757 reads
In the second level of our Stairway to SQLCLR, we look at how to enable the SQLCLR in SQL Server. We then build an assembly, store procedure, and a function that can be called from your T-SQL code.
2020-07-09 (first published: 2019-09-24)
26,017 reads
2018-10-11
19,580 reads
T-SQL does not have an easy way to transpose a row and a column. Of course, there is the PIVOT statement, but it doesn’t quite accomplish the task. In this article, Darko Martinovic shares another method using a SQLCLR stored prodedure.
2018-04-03
5,350 reads
Transform your query result into an Excel file using this technique.
2018-03-05
7,430 reads
SQLCLR is now considered a robust solution to the few niche requirements that can't be met by the built-in features of SQL Server. Amongst the legitimate reasons for avoiding SQLCLR, there is the fear of getting bogged down in code with special requirements that is difficult to debug. Darko takes a real example, extending the features of sp_send_dbmail, to demonstrate that there need be few terrors in SQLCLR.
2017-09-25
7,840 reads
This article shows a few techniques with SQLCLR to to transform a query result into HTML.
2017-06-05
4,029 reads
SQL SERVER Includes a Hashbytes function, however it's limited to VARCHAR(8000). This can cause a problem when trying to build hashes over wide datasets.
Solution
Expose the C# Hashbytes function using CLR
2015-12-01 (first published: 2015-11-06)
921 reads
Acknowledging fundamental design flaws lead to a more flexible, maintainable phonetic framework
2018-11-23 (first published: 2015-08-27)
3,694 reads
By Steve Jones
vicarous – adj. curious to know what someone else would do if they were...
Say we have a database that we want to migrate a copy of into...
We are trying to get apps and users off of using SQL accounts to...
Hi I have this view to check if a job is running: SELECT...
All, if you are like me and do not care for the built-in color...
Certain internal SQL Server actions cause internal checkpoints. Which of these actions does not cause an internal checkpoint?
See possible answers