Viewing 15 posts - 49,741 through 49,755 (of 59,091 total)
Sorry Mike, I've never used either. Hopefully, someone that has will see this...
...yeah... I'm "bumping" Mike's post because he didn't get an answer and I'm curious as well... 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 5:59 pm
No need for a cursor or While loop here... makes the code too long and slow. Try this instead...
--===== This makes a little test table according to the post
...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 5:57 pm
The major point has been missed... Andras explained it. You need a date column or an IDENTITY column to figure out what the last row actually is. Adding...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 5:15 pm
I find the co-existence of various ways of doing the same thing maddening
I find it makes sex interesting :w00t: Oops... sorry... wrong forum 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 5:11 pm
I think the only thing concrete is what the minimum installation requirements/recommendations are and what the maximum is. The rest is up to you to figure out based on...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 5:04 pm
Just in case you don't know... you can combine the two in a single select...
SELECT MIN(ValidateFromDate) AS MinDate,
MAX(ValidateFromDate) AS MaxDate
...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 4:53 pm
If you try to join 32 tables with multiple aggregates and functions on columns in the ON or WHERE clauses, it'll likely be better to use "Divide'n'Conquer" methods in a...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 4:43 pm
Do you have a time zone column somewhere?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 4:22 pm
Stephanie Giovannini (6/23/2008)
- Different phone ids may represent the same phone number
- Customers may share phone numbers
- A customer...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 4:13 pm
So, write some dynamic SQL to do it...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 3:44 pm
Hey Mark! Nice avatar!!!! 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 3:38 pm
Hey folks... especially Jeff Williams and Peter Larson... thanks for the great help. Like I said, I'm kinda new at 2k5 and you just don't find the...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 3:35 pm
Clear proc cache and clear the free buffers using DBCC commands of a similar name. Then, recompile the stored procedure code.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 2:27 pm
Set the recovery mode to SIMPLE or Bulk Logged... use SELECT INTO to make the tables and transfer the data. Then, add indexes, keys, triggers, and constraints... use NOCHECK...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 2:25 pm
It's the number of seconds since 1970-01-01 and can be changed to an SQL Server DATETIME datatype using something like the following...
SELECT DATEADD(ss,1195507770,'1970-01-01')
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 2:13 pm
Viewing 15 posts - 49,741 through 49,755 (of 59,091 total)