Viewing 15 posts - 55,321 through 55,335 (of 59,072 total)
No... not more VB like... more mathematical like ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
August 20, 2007 at 4:15 pm
Sure would be nice if you posted the URL of the article you read... ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
August 20, 2007 at 4:06 pm
Sounds like an interesting article... do you have the link? I'd like to take a peek...
Thanks, Tracey.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 19, 2007 at 9:35 am
Heh... ok... no flaming
But I'll just bet you'll never again let another vendor touch your DB's without making a full backup, huh?...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 19, 2007 at 12:30 am
Not sure if this can be done in Analysis Services because I don't use it
In the T-SQL side of the house, we...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2007 at 11:36 pm
Gova,
Are you all set now?
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2007 at 11:14 pm
Let's see... here's some nicely formed test data that Gova provided...
DECLARE @myTable TABLE
(
DataDate DATETIME,
DataVale INT
)
INSERT @myTable
SELECT '07/01/2007', 100 UNION
SELECT '07/08/2007', 120 UNION
SELECT '07/15/2007', 150 UNION
SELECT '07/22/2007', 190 UNION
SELECT '07/29/2007', 210...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2007 at 8:35 pm
Go back and look at the original post... it's all there even though there may have been a bit of confusion, at first... if it wasn't, I wouldn't have been...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2007 at 8:21 pm
Gova did all that, Lynn...
Even provided a table with data inserts..
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2007 at 3:00 pm
I suppose that there wouldn't be so much overhead associated with an INSTEAD OF trigger... but, ya gotta be a bit careful how you write them (from what I understand)...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2007 at 12:03 pm
Gova...
This'll do it. I use a Tally table (simple well indexed table of sequential numbers) for such a thing... if you don't have one, here's how to make one. It's a...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2007 at 10:03 am
Our DBA's took the easy way... everyone is part of a "role" and we grant privs, by table, by role.
The only problem with that is that read only tables don't...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2007 at 9:18 am
Katie brings up a really good point and it really got me thinking about something that aggravates the hell out of me about both my peers and my subordinates...
I'm normally...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2007 at 9:00 am
You bet... just remember that the "Simple" recovery mode will NOT allow you to recover a damaged DB to a point in time. The only difference between the 3 recovery...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2007 at 8:13 am
Not sure that's it, Peter... he lists
Now, what I need is the missing ranges.
1 01-Feb-2006 14-Jun-2006
2 01-Nov-2006 31-Nov-2006
2. 10-Oct-2006 31-Oct-2006
But, 01 - 30 Nov show up in both tables......
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2007 at 8:08 am
Viewing 15 posts - 55,321 through 55,335 (of 59,072 total)