Viewing 15 posts - 28,051 through 28,065 (of 59,101 total)
Koen Verbeeck (11/28/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2012 at 2:38 pm
LoosinMaMind (11/28/2012)
many thanks
I want to ephasize again that there must be some way of guaranteeing the insert order of the original data so the IDENTITY column will actually reflect the...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2012 at 11:40 am
Lidou123 (11/28/2012)
Thank you for your answer.
For my company, the first day of the week is Monday.
And the weeks are numbered by the start of the year.
We use the ISO...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2012 at 11:09 am
This is actually a duplicate post. Please provide any answers on the original post which, BTW, has been updated with even more clarification than what is on this post....
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2012 at 11:01 am
Lidou123 (11/27/2012)
I have a script problem.
I calculate data per week (group by week)
However, for indicators, I have business rules which apply in the month.
Here is the problem because I have...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 27, 2012 at 8:40 pm
CELKO (11/27/2012)
I should have posted this in the previous posting. Hugo makes all the arguments.http://sqlblog.com/blogs/hugo_kornelis/archive/2008/03/09/lets-deprecate-update-from.aspx
I've seen all of his arguments and appreciate them but they still boil down to...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 27, 2012 at 6:07 pm
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, is frequently given...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 27, 2012 at 6:02 pm
CELKO (11/27/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 27, 2012 at 5:58 pm
rhythm.varshney (11/26/2012)
Jeff Moden (11/26/2012)
rhythm.varshney (11/26/2012)
Phil Parkin (11/26/2012)
rhythm.varshney (11/26/2012)
waiting for your valuable input guys........You still have not asked a single question - there is nothing to respond to.
please suggest the way...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 27, 2012 at 3:08 pm
jgenovese (11/26/2012)
look at my post from 4:34:43 PM
The times change according to each of our local times. So there is no such entry according to what I can see....
--Jeff Moden
Change is inevitable... Change for the better is not.
November 27, 2012 at 5:39 am
Here's an article that explains the base method that Lynn is using (sans the formatting).
http://www.sqlservercentral.com/articles/T-SQL/71550/
--Jeff Moden
Change is inevitable... Change for the better is not.
November 27, 2012 at 5:13 am
karthik M (11/26/2012)
I have a procedure in SQL 2008 & 2012.
If I fine tune the procedure in SQL 2012, I would know what are all the new...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2012 at 10:21 pm
Or, send it to WORD as a "merge file" and let it do it. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2012 at 10:08 pm
sqldummy79 (11/25/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2012 at 10:05 pm
What do you get for the following???
SELECT *
FROM citytime
WHERE city_state='Mountain View, CA'
;
If the answer is "more than 1 row", then you've probably identified...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2012 at 9:18 pm
Viewing 15 posts - 28,051 through 28,065 (of 59,101 total)