Viewing 15 posts - 53,131 through 53,145 (of 59,072 total)
p.s. I just noticed that I left the code in that creates the "Raw2" table... that code is just not necessary and may be removed. Sorry for the...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2008 at 9:50 pm
Ok... sorry for the delay... couple of things came up and I couldn't get back to this... a shame, really, because this was kind'a fun.
In order to split the...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2008 at 9:48 pm
Did you use Clustered or Non-Clustered?
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2008 at 7:25 pm
Check the spelling of @StartTime in the proc... notice... 2 "T's" in your exec... does it have 2 "T's" in the proc?
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2008 at 7:11 pm
First things, first... call to the proc should be...
EXEC importemp 'EmployeesOld'
... not what you posted.
Second, you have a coding error... correction is highlighted in red...
ALTER PROCEDURE importemp
@dbname varchar(30)
AS
begin...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2008 at 7:06 pm
Yes... must it be a function or can you use a stored procedure to do the concatenation? Store procedure can use a temp table that is defined before the...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2008 at 6:57 pm
Kwitzell,
For those rows that are duplicated, which row would you like to keep... that is, do you want to keep the one with the largest ID or the smallest?
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2008 at 5:45 pm
Nothing wrong with reading the registry...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2008 at 5:42 pm
Actually, are you an independent consultant Jeff?
Only on occasion...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2008 at 5:24 pm
Hi Gail,
I guess my point was that the execution plans aren't always going to show the number of rows touched and that you cannot always determine which of two or...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2008 at 5:09 pm
Oh, heck no... Help yourself, Grant! You're one of the good guys, anyway!
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2008 at 5:03 pm
Outstanding, Steve... congratulations! You most definitely deserve it!
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2008 at 11:01 am
For a 1 time load, I'd export the data to Tab delimited files and Bulk Insert them. Nasty fast...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2008 at 11:00 am
Martin Bastable (1/3/2008)
I loved your comments on embedded documentation. I do that all the time, I find it helps me loads! (And other developers here when needs be). Even though...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2008 at 10:42 am
No, I sure don't, Grant...
I just copy and paste from a Word document that has some "Common Responses" in it.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2008 at 10:36 am
Viewing 15 posts - 53,131 through 53,145 (of 59,072 total)