Viewing 15 posts - 23,686 through 23,700 (of 59,102 total)
thomashohner (5/9/2014)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 10, 2014 at 8:15 pm
If you want real performance, I'd recommend that you stop counting altogether. Indexed views have an overhead on inserts in that they have to recalculate the totals for the...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 10, 2014 at 8:10 pm
[font="Arial Black"]WHY[/font] are you returning 600K rows to begin with???:blink: And [font="Arial Black"]WHERE [/font]are you returning them to? :unsure:
--Jeff Moden
Change is inevitable... Change for the better is not.
May 10, 2014 at 10:36 am
First, please don't post a thousand rows in a code window. It drove even my 4 processor 6GB ram laptop a little nuts because of the "prettifier" that SQL...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 10, 2014 at 9:54 am
To add to what Luis suggested, buy a copy of the SQL Server Developer Edition and try everything in the book... literally.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 9, 2014 at 5:33 pm
Except for the dr_sk column, I don't see any other unique indexes on this table and that's a good thing for paritioning-sake.
What's the nature of the dr_frdatetime_hq column?
1. Is it...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 9, 2014 at 10:24 am
Can you post the CREATE TABLE statement (including indexes, keys, FKs)? That might help a bit here.
Just so you know, partitioning a table that has other tables pointing to...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 9, 2014 at 8:36 am
GavD (5/9/2014)
I have inherited a dimension table that has almost 3 billion rows and is 1TB and been...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 9, 2014 at 8:14 am
Just remember that if you use a GLOBAL cursor, there could be a serious amount of contention between concurrent runs.
p.s. I love the tagline in your signature! 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
May 9, 2014 at 8:06 am
@Bals.Prasanna,
Howdy.
I'm not sure that I remember how to write Oracle triggers (they're single row based and then powered by a FOR EACH ROW for sets of rows) but I can...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 9, 2014 at 7:59 am
Sean Lange (5/9/2014)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 9, 2014 at 7:56 am
wendy elizabeth (5/8/2014)
/* Create TempTable */
CREATE TABLE #tempTable...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 8, 2014 at 3:38 pm
spaghettidba (5/8/2014)
I hope you noticed that this thread is 5 years old.
So was that post. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
May 8, 2014 at 9:01 am
Is there a column that could be used as a PK on the table?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 8, 2014 at 8:55 am
J Livingston SQL (4/6/2014)
/*possible proof of concept when applied to wide tables*/
/*response to Jeff's comments
"Also, because you have to make a copy of both the INSERTED and DELETED logical trigger...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2014 at 9:30 pm
Viewing 15 posts - 23,686 through 23,700 (of 59,102 total)