Viewing 15 posts - 54,871 through 54,885 (of 59,072 total)
Phil's method only works if the ID is contiguous and sequential. However, you can make that true if you copy the data you want into a temp table that has...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2007 at 7:26 am
SELECT
(SELECT COUNT(*) FROM A) AS [Count From A],
(SELECT COUNT(*) FROM B) AS [Count From B]
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2007 at 3:02 am
Heh... now that's funny. Near his avatar, it says that Phil Factor is a "Rookie" 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2007 at 2:41 am
If you take a look at the FROM clause in Books Online, you'll see that using a variable is NOT one of the options for a table name... in order...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2007 at 2:36 am
p.s. The best way to fix this is to pummel the vendor providing the data into submitting properly formatted data. The first row should be in a separate "control" file...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2007 at 2:25 am
Victoria,
The fastest way to do this is to build a BCP format file and then use Bulk Insert to import the data into a table. Of course, all that information...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2007 at 2:22 am
And, how do you do THAT? :Whistling:
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2007 at 1:55 am
Heh... let's see your "low knowledge" do it 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2007 at 1:45 am
Yeaup... quite the mess.
This could be done all in T-SQL by importing the whole row into a wide column and doing a split (using a function or some clever code)...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2007 at 1:36 am
Sorry,
Was reviewing old PM's and came across this link. Here's a split function that has no loops... the details, as always, are in the comments...
drop FUNCTION dbo.fnTSplit
go
CREATE FUNCTION dbo.fnTSplit
/***************************************************************************************************
Purpose:
Split a...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2007 at 1:13 am
I'm working on fixing that little problem... I had 84 PM's... when they shifted to the new system, the limit became 50. I'm working out how to download them (I...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2007 at 12:31 am
Where are you getting the CDR's from? Most CDR's include the CallStartTime as both Date and Time. And, the call duration is almost always listed in seconds. To get the...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2007 at 12:27 am
If you treat Excel like any other application, and you should, you'll soon realize that the best way to do this is to write a little VBS to push the...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2007 at 12:17 am
I'm thinking that Remi thought you were going to move the triggers that did the insert/update on table B to table B... and that's not what you intend...
Of course, I...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2007 at 12:12 am
Heh... lemme change my stance on this subject ...
I pretty sure there's something built in ... 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2007 at 12:00 am
Viewing 15 posts - 54,871 through 54,885 (of 59,072 total)