Viewing 15 posts - 42,376 through 42,390 (of 59,067 total)
trackingraj (8/10/2009)
I love sql server very much.
If that's true, follow your heart. Become a "hybrid" DBA and do both jobs very, very well. There's only one way...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2009 at 6:10 pm
Heh... does that make you a Gigo-lo? 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2009 at 5:58 pm
jinette.andelo (8/10/2009)
yes, know this scripts, but How I do this in vbscripts?
What are you doing that requires this to be done from VBS?
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2009 at 5:43 pm
saivko (8/10/2009)
Is there a good link you have in mind that talks about a sequence table? Or is it almost anything...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2009 at 5:42 pm
Ummmm.... does SQL Server's CHECKSUM use the SHA1 algorithm because I was talking about that CHECKSUM. Obviously that doesn't take 6000 to 12000 years to happen because I've seen...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2009 at 5:21 pm
GilaMonster (8/10/2009)
Sorry, but I'm going to greatly disagree with a number of these 'tips'
I have to agree with that. Gail's eval of some of the other tips is spot...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2009 at 6:28 am
17. CREATE TABLE vs. SELECT INTO - Select * INTO works fine for small tables, but when dealing with large record sets or long-running queries, it creates locks on the...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2009 at 6:07 am
Heh... no problem, Paul. The OP's question of "you use with instead while loop,why?" reminded me of the very first time I saw such a thing except my question...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2009 at 5:48 am
For more information on how such a table as Paul speaks of works to replace a While Loop, please see the following article...
http://www.sqlservercentral.com/articles/T-SQL/62867/
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2009 at 5:25 am
shannonjk (8/9/2009)
I am working on a copy I moved into my development environment and before I even started the code I added the indexes I figured were necessary 😉
In that...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2009 at 8:33 pm
shannonjk (8/9/2009)
The original took about 40 minutes.The current is still running but running right now at an hour and 25 minutes.
I appreciate all the help 🙂
I'd just go ahead...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2009 at 7:44 pm
Chuck Lucking (8/9/2009)
This would be the max(PhoneNumber) for each EmployeeID and PhoneType.
You just about wrote the query with that statement...
SELECT EmployeeID, PhoneType, MAX(PhoneNumber) AS PhoneNumber
FROM EmpPhone
...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2009 at 7:37 pm
Not good. I don't know if you've reached that "tipping point" I was talking about or if it's just that we're self-joining a 5.4 million row table. Can...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2009 at 7:29 pm
RichSmith (8/9/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2009 at 7:19 pm
Sorry folks... I'm just a bit sour on things like this. We had one guy at work that would get other people to help him do his work while...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2009 at 7:03 pm
Viewing 15 posts - 42,376 through 42,390 (of 59,067 total)