Viewing 15 posts - 43,486 through 43,500 (of 59,097 total)
RBarryYoung (6/10/2009)
What you should be able to see however is that the Unicode .sql file is about twice the size of the Ascii one.
Any idea if SQL Server supports UTF-8?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2009 at 9:16 pm
balars_2000 (6/10/2009)
thanks jeff.
You bet. Thanks for the feedback. So, are you all set or do you have a remaining question?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2009 at 8:39 pm
It's what you can't see that makes the difference... the following is a very good article on the subject...
http://www.joelonsoftware.com/articles/Unicode.html
As a side bar, it took me about 2 minutes to...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2009 at 8:27 pm
{insert jeaopardy them song here} Heh... I'll just bet someone talked him into a cursor solution.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2009 at 8:00 pm
Using QUOTENAME will pretty much put the kabosh on SQL Injection. But, I agree... if it's not used in a public facing environment, there's not much need for the...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2009 at 7:57 pm
Lynn Pettis (6/10/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2009 at 7:51 pm
lmu92 (6/10/2009)
It's not that hard to generate sample data - but it's time consuming.
It's a lot less time consuming than putting it into an excel spreadsheet, attaching the file, and...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2009 at 7:11 pm
GSquared (6/10/2009)
BUT, in a company with thousands of employees, can top management, or even upper middle management, actually get to personally know every employee?
Absolutely agreed. I didn't say they...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2009 at 6:36 pm
GSquared (6/10/2009)
So, in other words, no human anywhere should use any tool for anything, because it will cause the loss of responsibility and "the human touch".
I don't believe anyone even...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2009 at 6:15 pm
Mad Hacker (6/10/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2009 at 11:54 am
drogers (6/10/2009)
Uh, why would you "not agree with the idea that RAND() doesn't work like NEWID() in T-SQL." Do you find the discrepancy "unexpected?" 😀
Heh... Only the first time...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2009 at 11:09 am
RBarryYoung (6/9/2009)
Jeff Moden (6/9/2009)
O(wtf2) 😉Heh. Hey, I'm not the one who asked the question, I'm just trying to answer them.
Oh no... sorry, Barry. Wasn't directed at anyone in...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2009 at 5:52 am
Mike C (6/9/2009)
Jeff Moden (6/9/2009)
Mike C (6/9/2009)
Another minor quibble - each instance of RAND() is invoked once per query.
SELECT RAND(), RAND()
Generates two different random numbers because RAND() is actually called...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 9, 2009 at 10:45 pm
Steve Jones - Editor (6/9/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 9, 2009 at 10:40 pm
balars_2000 (6/9/2009)
I would display 0's to indicate there was no data during that particular week.--Ta
Then you need a complete list of dates to join against for any given year...
[font="Courier New"]DECLARE @FirstDate DATETIME
SELECT @FirstDate = '20090104'
SELECT v.Number AS Week,
DATEADD(wk, v.Number ,@FirstDate) AS StartDate,
DATEADD(wk, v.Number+1 ,@FirstDate) AS NextDate
FROM Master.dbo.spt_Values v
WHERE Type = 'P'
AND Number BETWEEN 0 AND 51[/font]
--Jeff Moden
Change is inevitable... Change for the better is not.
June 9, 2009 at 10:34 pm
Viewing 15 posts - 43,486 through 43,500 (of 59,097 total)