In the final installment of this three-Level series, we use another automation-related feature to do what SSDT doesn't handle natively.
2022-06-01 (first published: 2016-03-03)
6,656 reads
(last updated: 2021-09-01 @ 14:18 ET / 2021-09-01 @ 18:18 UTC ) In my previous post, SSMS and SQLCMD: Prevent T-SQL Batch From Not Only Executing, but Also From...
2021-08-31
96 reads
(last updated: 2021-08-13 @ 19:50 ET / 2021-08-13 @ 23:50 UTC ) In a previous post, Prevent Full Script Execution (Understanding and Using PARSEONLY and NOEXEC), I explained how...
2021-08-25 (first published: 2021-08-13)
523 reads
(last updated: 2021-07-02 @ 19:55 EST / 2021-07-02 @ 23:55 UTC ) The sysname data type (in SQL Server) is a system-provided, though not built-in, alias for NVARCHAR(128). This...
2021-07-02
120 reads
(last updated: 2021-05-31 @ 19:00 EST / 2021-05-31 @ 23:00 UTC ) Many of us that work with Microsoft SQL Server, especially those of us working on systems with...
2021-05-21
152 reads
This time we look at the commonly used tools for doing SQLCLR development: Visual Studio (VS), SQL Server Data Tools (SSDT), and SQL Server Express LocalDB (LocalDB).
2021-03-10 (first published: 2016-03-01)
6,404 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)
27,168 reads
Presenting about Module Signing at "Data Architecture Day" this Saturday (May 16th) at 4:10 PM EDT… Continue reading Presenting at “Data Architecture Day” this Saturday (May 16th) at 4:10...
2020-05-14
32 reads
Is EXISTS(SELECT 1 ...) better than EXISTS(SELECT * ...)? Who would know better than SQL Server?… Continue reading Actual Difference Between EXISTS(SELECT 1 …), EXISTS(SELECT * …), and EXISTS(SELECT...
2020-02-03 (first published: 2020-01-24)
3,209 reads
sys.xp_delete_files and 'allow filesystem enumeration': two new undocumented items in SQL Server 2019… Continue reading sys.xp_delete_files and ‘allow filesystem enumeration’: two new undocumented items in SQL Server 2019 ?
2020-01-27
570 reads
By Steve Jones
I wrote a piece on the new SUBSTRING in SQL Server 2025 and got...
By Kevin3NF
The terminology around reliability is a mess If you’ve ever said, “We’re covered, it’s...
By Steve Jones
If you aren’t watching the Ignite keynotes today, then you might have missed the...
I changed my email address in Edit Profile page, but it has no effect...
Comments posted to this topic are about the item The case for "Understanding our...
Comments posted to this topic are about the item Specifying the Collation
I am dealing with issues on my SQL Server 2022 instance related to collation. I have an instance collation of Latin1_General_CS_AS_KS_WS, but a database collation of Latin1_General_CI_AS. I want to force a few queries to run with a specified collation by using code like this:
DECLARE @c VARCHAR(20) = 'Latin1_General_CI_AS'
SELECT p.PersonType,
p.Title,
p.LastName,
c.CustomerID,
c.AccountNumber
FROM Person.Person AS p
INNER JOIN Sales.Customer AS c
ON c.PersonID = p.BusinessEntityID
COLLATE @c
Will this solve my problem? See possible answers