INSERT EXEC statement cannot be nested, the Simple Solution
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
40,098 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
40,098 reads
In this tip we look at how to enable SQL Server Common Runtime Language aka CLR using T-SQL commands.
2019-07-24
The CLR integration in SQL Server 2005 greatly expands on the capabilities of the SQL Server platform. One new area is the ability to build user-defined types and user-defined aggregates. Solomon Rutzky brings us a way to get around some of the limitations in this area with his SQL# toolkit.
2007-09-18
5,678 reads
SQL Server's CREATE ASSEMBLY statement lets you catalog code with one of three predefined security buckets. But under the covers, there are actually two distinct security models at play: Code Access Security and Host Protection, and you need to understand both.
2007-08-02
1,670 reads
With SQL 2005 you can harness the power of a higher-level language to not only do more with stored procedures, but also save time by already knowing a popular .NET language.
2007-07-11
3,137 reads
Working with large objects, BLOBs in SQL Server, has always been a little tedious. The forums are filled with questions on this topic. New authro Yoel Martinez brings us a more advanced looked at BLOBs in SQL Server 2005 with code and a technique for compressing large amounts of data to save space.
2008-01-11 (first published: 2007-01-30)
8,791 reads
This article is meant to explore these architectural issues from the bottom up, and aims to guide you through this new world. In the long run, new programming models are likely to appear that will abstract away a lot of the challenges you will encounter.
2006-12-15
2,929 reads
Auditing is becoming more important all the time for DBAs as regulations and requirements increase. Building auditing into your systems can be done a number of ways, but with SQL Server 2005, you have a new option. New author David Ziffer brings us a generic auditing CLR trigger.
2006-08-02
19,069 reads
s running .NET Framework code within SQL Server 2005 exciting or a threat? Which is it? This article explores the security issues of SQLCLR code so that both developers and DBAs can make informed decisions about its use.
2006-06-15
2,774 reads
Mapping services have become quite popular on the Internet and with many applications, but in order to use these, you need to map an address to a latitude and longtitude. Corey Bunch brings us a CLR example of how you can do this.
2006-05-01
19,043 reads
If you’ve been watching AI roll through the data community and thinking, “this seems...
By Arun Sirpal
Not every production incident is a database in RECOVERY_PENDING or a corrupted event (like...
It is Friday, the queries are running, and nobody is watching the bill. That...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Hi All I am trying to find 'bad' characters that users might type in....
WhatsApp: 0817839777 Kw. Industri Pulogadung, Jl. Raya Bekasi Km. 21, Ruko No.A2/18-19, RW.3, Wil,...
I set up a few users on my SQL Server 2022 instance.
CREATE LOGIN User1 WITH PASSWORD = 'Demo12#1' CREATE USER User1 FOR LOGIN User1 GO CREATE LOGIN User2 WITH PASSWORD = 'Demo12#2' CREATE USER User2 FOR LOGIN User2 GO CREATE LOGIN User3 WITH PASSWORD = 'Demo12#3' CREATE USER User3 FOR LOGIN User3 GOI then created a schema that one of them owned. Under this schema, I added a table with some data.
CREATE SCHEMA MySchema AUTHORIZATION User1
GO
CREATE TABLE Myschema.MyTable(myid INT)
GO
INSERT MySchema.MyTable
(
myid
)
VALUES
(1), (2), (3)
GO
SELECT * FROM MySchema.MyTable
GO
I granted rights and verified that User2 could access this table.
GRANT SELECT ON Myschema.MyTable TO User2 GO SETUSER 'USER2' GO SELECT * FROM MySchema.MyTable GOThis worked. Now, I move this schema to a new user.
ALTER AUTHORIZATION ON SCHEMA::Myschema TO User3; GOWhat happens with this code?
SETUSER 'USER2' GO SELECT * FROM MySchema.MyTable GOSee possible answers