Viewing 15 posts - 53,551 through 53,565 (of 59,089 total)
You don't really want to have it reclaim space automatically... causes too much fragmentation over time...
You need to find out what's making it grow to 42Gig... that's step 1...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2007 at 2:55 pm
10 hours to 15 minutes? Heh... I like SELECT/INTO a lot but I've not seen that type of performance gain just by switching like that before... Are you sure...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2007 at 2:52 pm
I load flat files that have many different row types. Fortunately, they're identified by a key in the file. I just load the whole shootin' match into a...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2007 at 2:45 pm
Was it sitting at 42GB a week ago with only .5% used as it was this morning? If so, I think you could probably safely shrink the log file...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2007 at 12:36 pm
What is the datatype of the JobDate column and what does the ChangeDate function return as a datatype?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2007 at 11:20 am
Jeff - it's a sequential file setup. look at the multiple segments (1 relates to the next "2" by previous.col3=current.col2).
Heh... I'm getting old... I was looking at trying to...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2007 at 11:14 am
Mindy, the problem is that you have the data stored in a CHAR(32)... trailing blanks come into play there. Either change the column to a VARCHAR(32) or modify my...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2007 at 10:41 am
jeff ...there is no other go, i want ot use only dynamic sql
Heh... you must not have looked because I gave you dynamic SQL. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2007 at 10:29 am
Sorry... not seeing the pattern here between the inputs and the desired output... would you explain how you want the concatenation formed better, please? Also, see the following if...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2007 at 9:58 am
Actually, if you look at the bigger picture, you have a much larger problem... why would you select from 3 different tables into 1? Except, possibly, for reporting, you...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2007 at 9:29 am
if you want to pass parameters into dynamic sql, then you MUST use sp_executesql.
I guess that depends on what you're calling a "parameter"...
Mike, going back to your original post, the...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2007 at 9:12 am
Perfect... thanks, Matt.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2007 at 8:24 am
SELECT INTO to populate the entire recordset is painfully slow compared to INSERT INTO
Not real sure where you're coming up with that... I agree that SELECT/INTO will hold a lock...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2007 at 8:16 am
I was pleasantly surprised a few years back to see MS trot out an actual certification specifically for these folks with most of its emphasis on the SQL side, and...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2007 at 7:44 am
For so many reasons, storing dates as formatted VARCHARs is such a terrible idea. If you need to do any date math or comparison of dates, formatted dates only...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2007 at 6:40 am
Viewing 15 posts - 53,551 through 53,565 (of 59,089 total)