Viewing 15 posts - 32,461 through 32,475 (of 59,099 total)
pandeesh (9/25/2011)
I have two columns name and Id in a table
I want to have the design in such a way that it should not allow to insert more than 300...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2011 at 7:03 pm
Yep... if the privs are the same and the code is the same, there's only one thing left... the data.
Check and make double sure that the job is running against...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2011 at 6:31 pm
R.P.Rozema (9/25/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2011 at 5:27 pm
Read up on the subjects that Remi recommended above, try some code on your own, and if you still can't figure it out, post your code and we'll be happy...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2011 at 5:07 pm
scottichrosaviakosmos (9/25/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2011 at 5:04 pm
CELKO (9/25/2011)
Please be polite enough...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2011 at 4:44 pm
First of all, Joe is absolutely correct... you'll get better answers more quickly if you invest just a minute or two in how you post your data. Please see...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2011 at 4:35 pm
Yes, it certainly is possible. Please see the following article for how to do it.
http://www.sqlservercentral.com/articles/T-SQL/63681/
I suspect that you could someday have more than 3 "skills" listed. For how...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2011 at 2:31 pm
Gosh, NO!!!! You don't need to make a slow-as-molasses UDF for such a thing. It's just not necessary. Use the following, instead (where "SomeDate" would be the...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2011 at 1:13 pm
balasach82 (9/24/2011)
Its Enterprise edition.Processors: 8
Max Server Memory: set at 10 GB
Memory: 12 GB
In that case, you might want to look into ALTER INDEX instead of DBCC and use the "online"...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2011 at 12:58 pm
J Livingston SQL (9/25/2011)
Do you have the code that built the 20M*30*100 data for both tables so we can test at the level you did?
Did you do a comparison of...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2011 at 12:55 pm
Dang... I almost forgot...
I call the "Lft" and "Rgt" columns "Bowers" after the two large anchors on the front of large ships. It makes the columns a whole lot...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2011 at 12:26 pm
First, I wouldn't store the Employee Name in the table except for demonstration purposes and Joe does cover that in the book I cited. Keep the "functions" of "organization"...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2011 at 12:22 pm
mjbkm (9/25/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2011 at 9:14 am
GilaMonster (9/25/2011)
Jeff Moden (9/24/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2011 at 8:51 am
Viewing 15 posts - 32,461 through 32,475 (of 59,099 total)