Viewing 15 posts - 57,616 through 57,630 (of 59,067 total)
Mita,
If you take a look... it is working correctly... you have multiple entries for some of the FMIS codes... notice in the sample data that you have the following inputs...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 18, 2006 at 5:45 pm
This should do it... if you don't already have a TALLY table, here's how to make one...
--===== Create and populate the Tally table on the fly
SELECT TOP 11000...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 18, 2006 at 12:12 am
Do you need ISO weeks by any chance?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 17, 2006 at 10:17 pm
RBAR!
--Jeff Moden
Change is inevitable... Change for the better is not.
September 17, 2006 at 10:09 pm
![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
September 17, 2006 at 4:20 pm
P.s Nice trick with the TOP 0 thing... most folks use WHERE 1=0 to do the same thing. TOP 0 seems more obvious and I like it.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 17, 2006 at 1:09 pm
First, SELECT/INTO does not lock system tables during a SELECT/INTO with no explicit transaction... (at least, none that I can detect)...
Test setup:
First, build yourself a nice medium sized test...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 17, 2006 at 1:00 pm
You should never set the database to grow by a percentage especially if the size of a database starts out small. It takes 73 growth spurts to grow a 1...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 16, 2006 at 8:15 pm
Sure... I'll send you the shrunken head of a Developer that I didn't like ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
September 16, 2006 at 8:05 am
Just curious... did my post help at all?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2006 at 10:25 pm
Yep... write to a UNC instead of a file/path...
The server must have write privs, as well.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2006 at 10:18 pm
SELECT dbo.functionname(@parameter)
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2006 at 10:10 pm
Job Requirements:
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2006 at 9:06 pm
Here's how to do it... you will need to replace "dbname" with the actual name of the database. You will need to do like wise with "servername". Once you've tested...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2006 at 8:29 pm
Why on Earth would you put the creation of a temp table in an explicit transaction? And, so far as exclusively locking the system tables when you use SELECT/INTO to...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2006 at 5:56 pm
Viewing 15 posts - 57,616 through 57,630 (of 59,067 total)