Viewing 15 posts - 31,516 through 31,530 (of 59,101 total)
erikpoker (1/4/2012)
Im selecting values from a table a:
SELECT a.col1, a.col2, a.col3, a.foreignkey-value
FROM mytable a
WHERE something=something
If the foreign-key-value is null i would like to insert it into the parent table on...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2012 at 5:40 am
kumar.sachu08 (1/4/2012)
I have 1 TB data in my database & I have only one table in my database
where more than 10 lacs data are available.
When i am going to...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2012 at 5:24 am
Dev (1/3/2012)
Jeff Moden (1/3/2012)
MysteryJimbo (1/3/2012)
Jeff Moden (1/3/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2012 at 5:17 am
EdVassie (1/4/2012)
Most SQL code can be written by anyone in the sprint team.
Gosh... I've worked in shops that have taken that stance. Unless they generally keep things...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2012 at 5:14 am
faijurrahuman17 (1/4/2012)
I am doubt for calling the SP with in the select Query
This is my sample procedure
EXEC [NmStudent] '07UF','10','100','0707'
Here will return the list of result List Like...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2012 at 5:03 am
William Krupinsky JR (1/3/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2012 at 4:56 am
My recommendation is that, while UniqueIdentifier and GUIDs certainly have their good uses, they should probably never be used as a Clustered Index. Further, yes, they can be used...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2012 at 4:48 am
shatrughna (1/3/2012)
Can you post some sample data?
And it actually has more than 10 rows of test data. Nicely done, Jason.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2012 at 11:01 pm
It IS a very small world, indeed. Good article, Steve. Thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2012 at 10:51 pm
MysteryJimbo (1/3/2012)
Jeff Moden (1/3/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2012 at 6:15 am
Dev (1/3/2012)
chandan_jha18 (1/3/2012)
Dev (1/3/2012)
chandan_jha18 (1/3/2012)
Jeff Moden (1/3/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2012 at 6:10 am
Actually, it's "expected" behaviour. An INSERT will "touch" on all indexes. An UPDATE might not even "touch" any of the indexes.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2012 at 5:29 am
There's also a matter of timing here. I've found that if you start the database development before you start any of the front end development, you end up with...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2012 at 4:56 am
I think you meant "PK", not clustered index which can, of course, be different.
Absolutely understood on the concerns over SELECT/INTO. I've build some huge tables with it over many...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2012 at 4:52 am
440692 I am just a number (1/3/2012)
Jeff Moden (12/28/2011)
To be sure, I made a terrible mistake. [font="Arial Black"]ISNULL isn't SARGable.[/font]
That is just a perspective thing.
Your 'terrible mistake' challenged something I...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2012 at 4:46 am
Viewing 15 posts - 31,516 through 31,530 (of 59,101 total)