2026-02-04 (first published: 2026-02-03)
107 reads
2026-02-04 (first published: 2026-02-03)
107 reads
The function (Inline function) is used to determine the word count in a textual/string input.
* Compatible from SQL Server 2012 and up.
2016-11-11 (first published: 2016-11-04)
489 reads
2016-04-28 (first published: 2016-04-07)
508 reads
Whenever a query is executed in SQL Server, its execution plan, as well as some useful execution data are placed into the plan cache for future use. This information is a treasure trove of metrics that can allow some very useful insight into your server’s performance and resource consumption - Ed Pollack shares some useful queries to start utilizing it.
2016-03-16
4,373 reads
http://www.sqlservercentral.com/scripts/split+string/117123/
The above script will split upto 256 char length only. This new version will split upto N length.
2016-09-14 (first published: 2014-10-30)
1,857 reads
Splitting strings based on patterns supported by LIKE and PATINDEX can be an interesting way to address a wide variety of problems.
2014-09-12 (first published: 2012-11-29)
33,578 reads
SQL Server 2012 introduces a new string concatenation function. This can be recreated in earlier versions of SQL Server.
2012-06-06 (first published: 2012-05-16)
2,171 reads
find and replace text in a text file using tsql
2012-01-23 (first published: 2011-12-16)
3,115 reads
This article from Todd Fifield shows a Way to avoid the dreaded LIKE operator in your queries and dramatically speed up keyword searches.
2012-09-07 (first published: 2011-02-28)
35,587 reads
We often have need of string splitting in applications. I had need of one in some T-SQL development I am currently doing for a friend.
2011-02-25 (first published: 2011-02-09)
2,030 reads
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
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...
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....
Comments posted to this topic are about the item Extreme DAX: Take your Power...
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