Viewing 15 posts - 52,126 through 52,140 (of 59,102 total)
CTE... Derivied table... no difference in performance, memory usage, of disk hits on TempDB... they both equate to "inline views"...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2008 at 1:19 pm
That's certainly another way to do it.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2008 at 1:08 pm
You have the correct idea... but since you didn't post anything about what the "user_splits" table looks like or what data it has in it, I have no idea what...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2008 at 12:58 pm
Wel-l-l-l-l-l.... kind of...
Sys.Objects has a Modify_Date column on it so you can tell when the last change occurred... you just can tell what the change was.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2008 at 12:47 pm
No, no... the TIMESTAMP datatype has absolutely NOTHING to do with a date or a time. Despite what Sam offered up, the best you'll get is some date and...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2008 at 12:41 pm
Grant Fritchey (3/5/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2008 at 12:26 pm
Ok... thanks for the feedback...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2008 at 12:23 pm
Please post the actual query... there's no way the one you posted actually works.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2008 at 12:18 pm
It's certainly not automatic, but my first inclination is to ask...
1. You allow folks to change production stored procedures without DBA approval?
2. Are there no documentation standards? ...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2008 at 12:16 pm
Ok... since you can't actually see Ascii 26 except maybe as a supurious square, how can you tell the end of file marker is being loaded?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2008 at 12:02 pm
Thanks TonyJ, It works but it doesn't work when u have this scenario
And, still, you haven't tried the solution that Ian posted which doesn't have that problem... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2008 at 11:59 am
Ralph Curry (3/5/2008)
select
Widget,
DateValue
from (
select
...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2008 at 11:51 am
Heh... at least you tried. Thanks for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2008 at 11:49 am
The end of file marker is typically an ASCII 26 and SQL Server will not read it in. You don't have to prevent it from happening.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2008 at 11:46 am
I could be wrong, but this sounds like a "running total" problem with an additional SELECT to find the 2 million mark... please see the following...
http://www.sqlservercentral.com/articles/Advanced+Querying/61716/
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2008 at 11:33 am
Viewing 15 posts - 52,126 through 52,140 (of 59,102 total)