Viewing 15 posts - 34,651 through 34,665 (of 59,099 total)
Phil, I have to mostly agree with djackson above. The editorial almost sounds like whining about the disparities of transmittable data formats. A "universal" data format has been...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 12, 2011 at 12:16 pm
djackson 22568 (3/12/2011)
The universities would distain such a practical task.
Oh please, let's not involve the universities! Seriously, I am tired of the better than you attitude of American universities....
--Jeff Moden
Change is inevitable... Change for the better is not.
March 12, 2011 at 12:04 pm
josetur12 (3/11/2011)
I have a flat file with over 200 fixed length columns
We're just guess here because we can't see your file.
Do you have a record layout for this file and...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 12, 2011 at 11:07 am
Sorry, forgot to post the results...
Device StartDateTime StopDateTime ...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 12, 2011 at 10:50 am
Nuno Martins (3/11/2011)
The sample log table:
device1 0 ...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 12, 2011 at 10:48 am
I absolutely agree but, just like I said a year and a half ago, too many people simply give up too easily on finding a high performance set based solution....
--Jeff Moden
Change is inevitable... Change for the better is not.
March 12, 2011 at 9:21 am
Stuart Davies (3/11/2011)
Can anyone help out me please.
If I run select isdate('27/1/2011') from my local install of SQL against a server I get 1
If I run the same query directly...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 12, 2011 at 9:15 am
My recommendation is "Try it". You may forget what you've been told but you won't forget what you've done. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
March 12, 2011 at 9:02 am
jason-772533 (3/12/2011)
I'm probably just being a bit stupid and missing the point.
Nope. You're alright, Jason. 🙂 It's a bit difficult to understand the concept when it comes to...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 12, 2011 at 8:57 am
Everything is good there except I wouldn't make the delimited list for the front end. Just return a result set and consume it at the front end. I...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 12, 2011 at 7:38 am
Brandie Tarvin (3/11/2011)
It wouldn't work if Roy was using some other data or delimiter
It only takes one well place REPLACE to fix that little nuance.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2011 at 11:02 pm
jashwantsingh (3/11/2011)
In my project a user can have multiple friends and I need to store friends of a each user. What I am...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2011 at 10:53 pm
mtillman-921105 (3/11/2011)
Also, you should rewrite the query to use an INNER JOIN rather than the older way its using more than one table.
There's no performance gain in it. The...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2011 at 10:41 pm
Eric M Russell (3/11/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2011 at 5:06 pm
Lowell (3/11/2011)
--using Stefan's setup:
/*--Results
(No column name)(No column name)
1172.24
322.25
3223.25
*/
SELECT Count(IPAddress),parsename(IPAddress,4) + '.' + parsename(IPAddress,3)
FROM #tempIPTable
Group By parsename(IPAddress,4) + '.' +...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2011 at 4:50 pm
Viewing 15 posts - 34,651 through 34,665 (of 59,099 total)