Viewing 15 posts - 41,446 through 41,460 (of 59,102 total)
Apologies... I modified my previous post because I misread the file data.
Let us know when you get the data loaded (several methods for that have already been offered) with a...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 21, 2009 at 12:21 am
lcsgeek (10/20/2009)
Here is the final code that works if anyone...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 21, 2009 at 12:11 am
Maybe I'm not looking at this problem hard enough, but I don't see the reason for a loop at all. This should be done using set based code.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 20, 2009 at 10:46 pm
a2zwd (10/20/2009)
We have installed new server(W2K8 and sql 2008).
The database has many tables and millions of rows.
How can I check the performance whether I can...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 20, 2009 at 10:43 pm
Bulk Insert and BCP will bring things in in the same order as the file unless done in parallel. Make the table with an IDENTITY column and BULK INSERT...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 20, 2009 at 10:37 pm
GSquared (10/20/2009)
Reboot when you have to, never otherwise.
I'll second that.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 20, 2009 at 10:32 pm
Option "A" is known as a "Slowly Changing Dimension Type 2" and, if I recall correctly, Option "B" is "Type 1". I prefer option "A" as I don't hav...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 20, 2009 at 10:25 pm
I'm not so sure that's true, Steve. Just like with Log Files on full recovery DB's, a time honored server performance "trick" is to move TempDB to it's own...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 20, 2009 at 10:14 pm
The answer is simple on this one... don't use a permanent table as a staging table... use a Temp Table.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 20, 2009 at 10:06 pm
Elliott W (10/20/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 20, 2009 at 10:03 pm
Bob has shown the way with the best performance in 2k5. Lemme show you what you did wrong with yours....
CREATE FUNCTION dbo.fnConcatTest (@PID INT)RETURNS VARCHAR(8000)
AS
BEGIN
DECLARE @Return VARCHAR(8000)
SELECT...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 20, 2009 at 9:49 pm
Heh... like I said...
I know that the use of cursors and loops for flow control is an acceptable use...
... and I agree with all the reasons Bob stated for this...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 20, 2009 at 9:36 pm
I know that the use of cursors and loops for flow control is an acceptable use but... I just can't bring myself to write one if there is another way...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 20, 2009 at 9:12 pm
Ummmm.... why build the reporting view at all? Build the table so it looks like the view, index it correctly, and have synonym pointing at the table in...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 20, 2009 at 6:05 pm
Heh... gettin' old... Seth beat me. Same idea though...
SELECT DATEADD(ss,1,DATEADD(mm,DATEDIFF(mm,-16,GETDATE())-1,-16))
--Jeff Moden
Change is inevitable... Change for the better is not.
October 20, 2009 at 5:55 pm
Viewing 15 posts - 41,446 through 41,460 (of 59,102 total)