Viewing 15 posts - 34,351 through 34,365 (of 59,102 total)
I dug the old black'n'white "Shake'n'Bake" commercials... the Mom was HOT! 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
April 7, 2011 at 8:37 am
sturner (4/7/2011)
The query optimizer is an impressive piece of logic, but in my opinion it is still not a match for an experience SQL database designer/programmer.
I couldn't have said that...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 7, 2011 at 8:29 am
Mark-101232 (4/7/2011)
opc.three (4/7/2011)
Brandie Tarvin (4/7/2011)
Or maybe it was the guy at Simple...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 7, 2011 at 8:21 am
What you've done is a technique that I use all of the time. It's called "Divide'n'Conquer". To put it in simple terms, think of a plate juggler... which...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 7, 2011 at 7:20 am
clement.store (4/7/2011)
I wonder if I m working on some heavy calculation with TSQL. Would SQL server be automatically leverage all the 12 cores in the server? Or some changes...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 7, 2011 at 7:13 am
I think the article of mine that you're looking for is here...
http://www.sqlservercentral.com/articles/Test+Data/61572/
HOWEVER, I believe that the very nice canned solution that Lowell provided is the better way and is VERY...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 7, 2011 at 7:08 am
David McKinney (4/7/2011)
When a stored procedure is created the settings for ANSI NULLS and QUOTED IDENTIFER which were set at creation time are 'saved with the stored procedure' and can...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 7, 2011 at 6:53 am
Are there any known limits for the data so you can remove the human element?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 7, 2011 at 6:43 am
kwoznica (4/1/2011)
Jeff,What would be the best way to do that though?
We already have millions of records. Also would it need to be part of the front end application?
First, no,...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 7, 2011 at 6:34 am
GilaMonster (4/5/2011)
Jeff Moden (4/5/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2011 at 4:45 pm
opc.three (4/6/2011)
1. I could see using the approach from...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2011 at 4:34 pm
I absolutely don't mind. What is the basis of the study and how can I learn more about it and maybe even convince Dad to provide all the information...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2011 at 11:10 pm
philcart (4/5/2011)
But seriously, I reckon they need a more stringent posting process so the numerous superfluous cases don't get lodged. If people had to think more...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2011 at 10:39 pm
Also, you need to explain which table you want the trigger on and what you want to fire it.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2011 at 10:31 pm
So... let's say that everyone has a Status of 1 and you suddenly insert 100 rows. Do you want John to have all 100 rows?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2011 at 10:29 pm
Viewing 15 posts - 34,351 through 34,365 (of 59,102 total)