Viewing 15 posts - 54,691 through 54,705 (of 59,098 total)
Perfect... I'll be back...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2007 at 9:20 am
Sorry... that just doesn't help me... all of your examples show only one date... would you please do as I ask so I can help? Please change the following...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2007 at 9:02 am
To add to that... are there Primary Keys on these tables? Is there a clustered index? Are the tables in a constant state of flux do to inserts,...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2007 at 8:28 am
If it's the "Estimated" Execution Plan... pay those percentages no mind... it "lies" because it will frequently miss things. For example, only the first pass of a triangular join...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2007 at 8:16 am
Heh... thanks for the "apple" ๐
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2007 at 7:42 am
Dunno about your first question but I'm pretty sure that the answer to your second question of can you "view images in SQL Server" is an emphatic "NO".
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2007 at 7:39 am
Heh... flies haven't found it, yet... :hehe:
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2007 at 7:33 am
Thanks, but doesn't quite tell me what you want... not trying to be difficult here, either but "one picture is worth a thousand words"....;)
You listed this as an "input"...
Insert Into...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2007 at 7:30 am
Yep... I agree with all of that... if it's for GUI code...
For batches, the proc will probably recompile anyway just because the data will have changed enough to need a...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2007 at 7:24 am
A big key here is that David DIDN'T even use a function (although you could if it's for RBAR GUI code)... it splits a whole table's worth of information in...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2007 at 7:16 am
Heh... I cheat like hell... load up one staging table with everything... delete the dupes with the "earliest" information... flip the pass-through-view to look at the new table... drink beer...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 8, 2007 at 8:56 pm
Ramesh Lende (10/8/2007)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 8, 2007 at 8:47 pm
Backups... if for nothing else, to clear log files that are getting big and growing.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 8, 2007 at 8:44 pm
Most people recommend against it for many reasons... most of them are good, some are not... but you could put a view in the Master database and that would draw...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 8, 2007 at 8:34 pm
nba (10/4/2007)
The problem now is not the trigger but why it was there and not documented.
Simple... database is not correctly locked down for changes. No one but DBA's should...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 8, 2007 at 8:21 pm
Viewing 15 posts - 54,691 through 54,705 (of 59,098 total)