Only the brave, and foolhardy, write production CLR routines if you can get the functionality already-written and tested. Whether you’re a DBA or developer, there are plenty of times when a CLR routine will save a lot of time, and occasionally provide new functionality.
2011-10-24
4,490 reads
By Ed Elliott
Running tSQLt unit tests is great from Visual Studio but my development workflow...
By James Serra
I remember a meeting where a client’s CEO leaned in and asked me, “So,...
By Brian Kelley
If you want to learn better, pause more in your learning to intentionally review.
Comments posted to this topic are about the item The Long Name
Comments posted to this topic are about the item Eight Minutes
Comments posted to this topic are about the item T-SQL in SQL Server 2025:...
I run this code to create a table:
When I check the length, I get these results:
A table name is limited to 128 characters. How does this work?