Viewing 15 posts - 28,036 through 28,050 (of 59,101 total)
peter-757102 (11/29/2012)
But one thing I noticed quickly was a quote...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2012 at 4:27 pm
Peter H (11/29/2012)
SELECT TOP(DATALENGTH(@List))
n = ROW_NUMBER() OVER(ORDER BY (SELECT NULL))
FROM
(VALUES (0),(0),(0),(0),(0),(0),(0),(0),(0),(0))...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2012 at 4:21 pm
Irozenberg 1347 (11/29/2012)
Why we have to be inventive and create such acrobatic solution in a first place? Just to compensate for bad design and implementation decisions.
In a word, YES!...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2012 at 4:17 pm
wolfkillj (11/29/2012)
The real problem with the fizzbuzz puzzle for evaluating a programmer's ability is that it is only a puzzle. Once someone has seen it solved, the puzzle presents no...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2012 at 3:20 pm
Grant Fritchey (11/28/2012)
If it's a dev environment, you may not want to set up extensive backup routines (for many obvious reasons) which is yet another reason...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2012 at 7:19 pm
wolfkillj (11/28/2012)
Jeff Moden (11/27/2012)
CELKO (11/27/2012)
Create a million row FizzBuzz table. FizzBuzz isn't a comment. It's the name of a very common problem based on a child's game,...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2012 at 5:33 pm
GilaMonster (11/28/2012)
weberharter (11/28/2012)
... but if the terms are used here, why not explain it? 😉
Because we assume that people know the basic terminology or, if they don't, will go and...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2012 at 4:53 pm
Jennifer Levy (11/28/2012)
I had to change the numeric columns on the SQL Server side to allow NULLs, but it ran just fine once I'd done that.
No kidding? Thanks for...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2012 at 4:49 pm
I'll also add that you pretty much blow yourself out of the water when using any blob-type including things like NVARCHAR(MAX) and XML when it comes to being able to...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2012 at 4:44 pm
suresh0534 (11/28/2012)
But i want when the user updating any fileds in the table , only those fileds i need to insert into another table.
So i can know...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2012 at 4:40 pm
David.Poole (11/28/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2012 at 4:37 pm
Michael Valentine Jones (11/28/2012)
TravisDBA (11/28/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2012 at 4:34 pm
David.Poole (11/28/2012)
Lets suppose that you have old systems ridden with tech debt and propped up by manual processes.
Those powers that...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2012 at 4:31 pm
lynn.huff (11/27/2012)
That all applies to aggregating, which doesn't apply to my problem.
Actually, it does. Use MAX instead of SUM to transpose character based items.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2012 at 2:51 pm
Why not just right click on the database, select "tasks", "generate scripts", and select box to create 1 file per object?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2012 at 2:46 pm
Viewing 15 posts - 28,036 through 28,050 (of 59,101 total)