Viewing 15 posts - 30,301 through 30,315 (of 59,101 total)
Lynn Pettis (4/23/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2012 at 10:51 am
polkadot (4/22/2012)
What was important for me here was that I get the problem solved within pivot framework
Why? Pivot is usually slower and a whole lot more ugly for more...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2012 at 10:32 am
george sibbald (4/23/2012)
Check the URLs it links to as well.
With logs the important thing to be aware of the size and number...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2012 at 10:28 am
Robin Sasson (4/23/2012)
His reasoning was...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2012 at 10:25 am
ricardo_chicas (4/23/2012)
actually all I did was to reate a loop that read the data 10000 records at the time, that allow me to use one of the main indexes...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2012 at 10:20 am
Heh... even when I went back to read what you and Mark had said, there's (IMHO) some abiguity and I didn't want to just assume. Thanks for the answer.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2012 at 10:17 am
capn.hector (4/23/2012)
+1 however i saw this same question as homework for one of my sql classes.
Interesting! Where did you take such a class? I ask...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2012 at 10:12 am
rummings (3/13/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2012 at 8:27 am
Robin Sasson (4/23/2012)
Then generate separate scripts for the data.
BWAAA-HAAAA! That's a bit like saying "It's easy to get to the moon. Just build a rocket ship." 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2012 at 8:26 am
And be very aware that growth by percentage is almost never OK. If your db is small and growing, it can fragment the hell out of the database, the...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2012 at 8:21 am
Almost forgot. Here's an article that explains one method to do as you ask.
http://www.sqlservercentral.com/articles/T-SQL/72503/
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2012 at 12:23 am
dwain.c (4/22/2012)
I have to ask... does "RESOLVED" and "CLOSED" actually mean the same thing? Legally speaking, I would think not.
--Jeff Moden
When I saw you had posted to this...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2012 at 12:18 am
Lynn Pettis (4/22/2012)
Revenant (4/22/2012)
Lynn Pettis (4/22/2012)
Revenant (4/22/2012)
Lynn Pettis (4/22/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2012 at 12:14 am
anil.janu143 (4/22/2012)
//this is my tablecreate table std_table
(
id int,
name nvarchar,
address nvarchar,
)
//this is my table data
10 null null
null anilkuar null
null null hyderabad
//i want the data like this
10 anilkumar hyderbad
Given nothing else...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2012 at 12:02 am
WRACK (4/22/2012)
Jeff Moden (4/22/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 22, 2012 at 11:56 pm
Viewing 15 posts - 30,301 through 30,315 (of 59,101 total)