Viewing 12 posts - 16 through 27 (of 27 total)
There is a trick way to allow a function (procedure) take a rowset (a.k.a. table) as an incoming parameter.
Let's say I had a procedure that I wanted to accept a...
June 15, 2006 at 9:18 am
These are part of DTS ("dt_" = data transformation...). They are managed by the system. I would leave them alone.
(I haven't researched into whether it is safe or not to...
November 3, 2004 at 12:30 pm
This is like the request I got once to "make all the databases available at all the company's sites such that if any go down all the rest still operate,...
November 3, 2004 at 11:57 am
Dynamic SQL anywhere -- especially triggers -- is less than optimal. Rather than make a server-side trigger generic, I would suggest writing a "code-generator" script that will generate a "strongly...
November 2, 2004 at 2:18 pm
You are right that the design is questionable. However, technically it's not a normalization issue. (However, you can have fully normalized designs that still have many many issues.)
I would classify...
October 6, 2004 at 5:50 pm
That's good to know. Thanks.
Although it does seem a bit of an odd choice. It will be fun seeing a "practical" example where it's useful.
...
I should have mentioned earlier: I...
September 3, 2004 at 11:56 am
Carl, you've hit upon one of my biggest pet peeves with SQL Server and other products... so-called "relational" systems that do not allow decent manipulation of relational variables (a.k.a. tables).
I...
September 3, 2004 at 10:19 am
Agreed. This is a moronic request from developers and demonstrates a *complete and utter* non-understanding of database fundamentals.
You should push back on the request and request your company hire more...
August 23, 2004 at 2:26 pm
Two comments on prior posts:
a. Try to avoid "where somefunction(x) = somevalue." (E.g., do not use the "isnull(column,'')" suggestion. That pattern in where clauses often causes SQL Server to evaluate...
August 17, 2004 at 10:33 am
UDFs (a.k.a. "cursors in sheep's clothing"!) should be used with caution for any SELECT that returns more than a few results.
If SQL cannot figure how to make it "inline" --...
June 26, 2004 at 11:16 am
That's overly complicating the problem. Simply revise the original CASE suggestion (the best approach) to:
CASE WHEN @EmployeePhone is NULL THEN '' ELSE '<EmployeePhone>' + @EmployeePhone + '</EmployeePhone>' END
(Don't...
June 25, 2004 at 10:07 am
quote:
...where relational integrity is secondary to transactional integrity and capacity/performance is critical. In correctly constructed transactional systems the business object and...
August 15, 2002 at 12:46 am
Viewing 12 posts - 16 through 27 (of 27 total)