Viewing 15 posts - 61 through 75 (of 149 total)
Sergiy (12/21/2016)
That could be said about the vast majority of those "good advises" you referring to.
Advise does not necessarily equal a solution.
Ready-made solutions which an OP can use but not...
Wes
(A solid design is always preferable to a creative workaround)
December 22, 2016 at 12:50 pm
I can't see the image.
Please also provide more sample data.
Wes
(A solid design is always preferable to a creative workaround)
December 22, 2016 at 7:41 am
olibbhq (12/22/2016)
What I would like to do is to return a running maximum and a running minimum
but with the added complexity that (sorting by rank ID) if the lower...
Wes
(A solid design is always preferable to a creative workaround)
December 22, 2016 at 7:24 am
Sonny Childs (12/21/2016)
Would love to get some feedback on this, because it feels like I've just used a rocket launcher to smite a mosquito.
Tally table provides the power of a...
Wes
(A solid design is always preferable to a creative workaround)
December 21, 2016 at 3:52 pm
Use a number/tally/calendar table to iterate through the days.
http://www.sqlservercentral.com/articles/T-SQL/62867/
On a separate note, UNION eliminates duplicate rows, but your result sets are guaranteed unique (different dates). You are adding unnecessary...
Wes
(A solid design is always preferable to a creative workaround)
December 21, 2016 at 7:41 am
CELKO (12/19/2016)
The best teachers I ever had were the ones that humiliated me when I was blindly stupid and could not get the basic concepts.
Here you just scare people away....
Wes
(A solid design is always preferable to a creative workaround)
December 21, 2016 at 7:21 am
DK13 (12/20/2016)
NULL is a valid action type.
I'll save Celko the effort here. NULL is not a valid action type. It is messing up your results because you are...
Wes
(A solid design is always preferable to a creative workaround)
December 21, 2016 at 7:05 am
Use of Merge seems a good match for what you are asking.
However, I am baffled by what you are trying to accomplish with this. I can't think of any...
Wes
(A solid design is always preferable to a creative workaround)
December 21, 2016 at 6:50 am
m.sams (12/19/2016)
What do I lose by exchanging the Primary Key index with another non-clustered index?
Don't think of the non-clustered PK as an index. It is just a constraint which...
Wes
(A solid design is always preferable to a creative workaround)
December 19, 2016 at 2:46 pm
In addition to Kevin's comments, you also have potential for unexpected results.
SELECT CAST(RTRIM( b.description ) AS FLOAT) AS ohproc,
...
Group by b.description
However many spaces you're trimming are still included when grouping....
Wes
(A solid design is always preferable to a creative workaround)
December 14, 2016 at 11:01 am
This distinct is not necessary and has not effect on the result. It probably won't affect the query time as the optimizer is likely ignoring it, but better to...
Wes
(A solid design is always preferable to a creative workaround)
December 14, 2016 at 10:20 am
Just another thought.
If you're needing space to convert the heap to a clustered index, drop any non-clustered indexes on the table first. NCIs also take up space and they'll...
Wes
(A solid design is always preferable to a creative workaround)
December 14, 2016 at 7:29 am
SQL Learner - VKG (12/14/2016)
Wes
(A solid design is always preferable to a creative workaround)
December 14, 2016 at 7:20 am
Igor Micev (12/12/2016)
Wes
(A solid design is always preferable to a creative workaround)
December 12, 2016 at 7:27 am
bucketlist50 (12/9/2016)
Declare @Counter int = 1;
with cte as (
SELECT @Counter as c,ASSET_NUM,[SHAPE].STPointN(@Counter).STAsText() as Points
FROM [dbo].[GEOMETRY_TABLE]
where ASSET_NUM =...
Wes
(A solid design is always preferable to a creative workaround)
December 9, 2016 at 2:01 pm
Viewing 15 posts - 61 through 75 (of 149 total)