Viewing 15 posts - 56,056 through 56,070 (of 59,086 total)
Doesn't help the processing speed at all but does take less size for the dynamic SQL, the WHERE clause should be constructed more like the following...
FROM RecurrentOutcomeParticipants rop
WHERE...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 22, 2007 at 7:29 pm
use occ_archives
insert into asqcrr.occ_archives.dbo.hvcfids
select * from asqcrr.occ_archives.dbo.hvcfids as dest
Where not exists
(select workitemid
from asqcrr.occ_archives.dbo.hvcfids as source
where source.workitemid = dest.workitemid)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 22, 2007 at 1:33 pm
Way too much info ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
June 22, 2007 at 1:29 pm
Yes, and no... if you use a format file for repetative imports, the answer is yes... but the data in this example won't support your method or my method because the...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 22, 2007 at 1:28 pm
Then there's THAT
Works almost everytime...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 22, 2007 at 1:24 pm
If you use OSQL with the -h-1 option and the -o option, something like the following works very well...
USE Northwind
SET NOCOUNT ON
SELECT QUOTENAME('CustomerID','"')+','
+ QUOTENAME('CompanyName','"')+','
+...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 22, 2007 at 1:17 pm
My pleasure... however, Wayne is correct... his method not only inherently checks the row counts, it also checks the actual data...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 22, 2007 at 1:06 pm
Ack! A cursor? ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
June 22, 2007 at 1:01 pm
Heh... understood and no worries... you've just got my curiosity up especially on the performance thing...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 22, 2007 at 8:15 am
Sorry... missed the fact that you were still working on this to take variables... I'll take a crack at it over the weekend...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 22, 2007 at 8:00 am
Sorry... didn't read the whole thread... I pretty much repeated what David McFarland already posted.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 22, 2007 at 6:21 am
Agreed... BIGINT will certainly work... But consider a couple of things before you decide to use any numeric datatype for any "numbers" column such as credit card numbers, bank account numbers,...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 22, 2007 at 6:19 am
Gosh, you would think so... I guess I understand why some folks don't, though... some DBA's don't practice what I consider to be the cardinal rule of being a DBA...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 22, 2007 at 5:58 am
Once again, your ideas are extemely sound, but I see no code from you...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 21, 2007 at 11:38 pm
Start with OSQL -L
--Jeff Moden
Change is inevitable... Change for the better is not.
June 21, 2007 at 11:35 pm
Viewing 15 posts - 56,056 through 56,070 (of 59,086 total)