Viewing 15 posts - 54,916 through 54,930 (of 59,072 total)
Sorry... my mistake... didn't read the reply well enough and this new system won't let me edit or delete my previous post...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 22, 2007 at 8:34 am
Shoot... that's not true in 2000... lookup "Creating a Partioned View" to see how to partition tables... :discuss:
--Jeff Moden
Change is inevitable... Change for the better is not.
September 22, 2007 at 8:30 am
Great idea, George... just keep in mind that only works if you're calling BCP via xp_CmdShell in T-SQL or you have Windows Authentication enabled on the server... ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
September 21, 2007 at 8:25 pm
You bet... thanks for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 21, 2007 at 8:24 pm
Heh... at least you said "set"...
Ok, thanks, guys... I've gotta study this a bit. ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
September 21, 2007 at 8:15 pm
Ummm... "monitoring" is great... helps you identify crap code that takes days to run without finishing... but, unless you take the next step, you might as well not waste your...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 21, 2007 at 7:59 pm
| Hi, I want to copy production database to a testing server. The production database is too... |
--Jeff Moden
Change is inevitable... Change for the better is not.
September 21, 2007 at 7:36 pm
Wouldn't have a problem at all if the HD's were labeled correctly as HD1, HD2, HD3, etc ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
September 21, 2007 at 7:24 pm
Here's the corrected query... since I don't have the tables available that you do, I'm unable to test it, but it should be close. Combine that with the suggestions others...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 21, 2007 at 7:19 pm
Heh... damned straight it's slow... you've written it as you would in Oracle... you've used a "Correlated Subquery" in the SET clause and that means that the query must be...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 21, 2007 at 7:01 pm
Unless the worksheet is protected against mistakes like adding an unexpected column or hitting the space-bar to "delete" data, you may get some wildly unexpected results and failures using Excel...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 21, 2007 at 6:51 pm
You actually expect an Access ODBC driver to operate as fast as an SQL Server OLE DB driver when used against SQL SERVER?
...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 21, 2007 at 6:46 pm
Heh... I have to laugh at what they call "best practices" for most performance issues... no where do they say "review all code for possible performance issues before it goes...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 21, 2007 at 6:43 pm
Can you post the code for your final solution, please?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 21, 2007 at 6:35 pm
Thank you for the feedback and I have a very high speed solution in mind... but I need to know what you want done with the data that I posted......
--Jeff Moden
Change is inevitable... Change for the better is not.
September 21, 2007 at 6:05 pm
Viewing 15 posts - 54,916 through 54,930 (of 59,072 total)