Viewing 15 posts - 53,221 through 53,235 (of 59,072 total)
Are you after the gaps in the EmpNo column?
That's what I want to know...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 31, 2007 at 2:18 pm
Why on Earth would you want to generate a Billion sequential numbers? That will take 8 gigabytes of space all by itself... it is not practical to do such...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 31, 2007 at 2:12 pm
True enough. Just listing options, Adam...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 31, 2007 at 2:07 pm
You are correct... makes no significant difference if you only use it once at the beginning of a sproc... unless the sproc is being called millions of times a day...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 31, 2007 at 2:01 pm
The correct answer should be...
... change the column in the table to the correct data type.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 31, 2007 at 1:09 pm
My experience with resumes is that when people say they want to "Beef Up" their resume, they really mean "stretch the truth" about experience and knowledge. One of my...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 31, 2007 at 1:04 pm
With the possible exception of some RegEx functionality, what is it that you think cannot be done in T-SQL without the use of CLR's?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 31, 2007 at 12:45 pm
If you setup Query Analyzer in the Text mode and use Tab's to delimit the data instead of commas, you can copy and paste directly from the Text results window...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 31, 2007 at 12:43 pm
Concur... trips through CHAR/VARCHAR conversions are somewhat slower especially over millions of rows.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 31, 2007 at 10:43 am
karthikeyan (12/31/2007)
<> Operator perform TableScan method.
Or, if the indexes are correct... an Index Scan which can be a little faster because there's usually fewer pages to step through. If...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 31, 2007 at 10:39 am
Yes... it works.
No, no difference to the sever.
Yes... difference in readability but depends on what you're used to. I prefer the use of "=" to "IN" for single value...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 31, 2007 at 10:28 am
This would be a very good place for you to lookup the POWER function in Books Online... it has a full explanation.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 31, 2007 at 10:12 am
h2sut (12/28/2007)
I just started using sql server 05 and that the only way i know. I not familar with a setbased... what is that
"Set-based" is the whole idea behind databases......
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2007 at 10:42 pm
You code calls on V-1... i see no example of V_1.
Further... all of these views call on the table EmpBase... why do you need the views at all?
Instea of trying...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2007 at 10:34 pm
You crammin' for an interview or a test? Or, is this a take home test.
Please, do your own homework.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2007 at 10:24 pm
Viewing 15 posts - 53,221 through 53,235 (of 59,072 total)