Skip To Main Content
c.Contact Name on Muck Rack

c.Contact Name

As seen in: SQL Server Central
Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work. Claim your profile
Back to c.Contact Name’s profile

Articles by c.Contact Name

The Curse and Blessings of Dynamic SQL

|
By Cmd.execute NonQuery, c.Contact Name, p.Product Name
An SQL text by Erland Sommarskog, SQL Server MVP. Last revision: 2022-08-30. Copyright applies to this text. See here for font conventions used in this article. Introduction This is a text about dynamic SQL. Used in the right place, dynamic SQL is a tremendous asset, but dynamic SQL is also one of the most abused features in SQL Server.
Open in Who Shared Issue with article?

The Zero to N Parameter Problem (Sql Server 2005 and Up -- Update) – SQLServerCentral

|
By c.Contact Name, c.Contact Title, c.Postal Code, o.Order Date
| SQL Server Central
(Note: We are re-running this as we had a newsletter issue last week) While this topic has been discussed before, here is another look at the "Multiple but Optional Parameters" issue in T-SQL. Sometimes you want to write a stored procedure which returns one or more Result(s), but you may or may not want to pass in some parameters. A comma delimited list just does not seem to cut it anymore, and dynamic SQL isn't a good idea.
Open in Who Shared Issue with article?

The Zero to N Parameter Problem – SQLServerCentral

|
By Sloan Holliday, c.Contact Name, c.Contact Title, c.Postal Code
| SQL Server Central
Specifying 0 to N parameters for Stored Procedures with XML While the topic has been discussed before, here is another look at the "Multiple but Optional Parameters" issue, when using TSQL. Sometimes you want to write a stored procedure which returns ResultSet(s), but you may or may not want to pass in some parameters. A common delimited list just does not seem to cut it anymore. And dynamic sql doesn't cut the mustard either.
Open in Who Shared Issue with article?

Sequential Ordering on SQL 2005 – SQLServerCentral

|
By Michael H. Coles, c.Contact Name, soh.Order Date, Country RegionCode
| SQL Server Central
The Problem Once upon a time Mr. Francois Ansee, SQL guy extraordinaire, wanted to get a list of his customers. The catch? They had to be sequentially numbered, in alphabetical order by CustomerID. It's one of the most basic tasks a SQL guy (or gal) will face, and in prior versions of SQL Server, the choices could be frustrating. Let's consider Francois' problem and look at some possible solutions in SQL 2000.
Open in Who Shared Issue with article?
Show More