Viewing 15 posts - 52,786 through 52,800 (of 59,098 total)
Thanks for the feedback... as always, my test data may not be 100% the same as your situation... once you've tried the index, lemme know how it works... might be...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 22, 2008 at 8:56 pm
There is... assuming that your serial numbers are actually integers...
SELECT GapStart = (SELECT ISNULL(MAX(b.SerialNumber),0)+1
...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 22, 2008 at 8:25 pm
Heh... make sure you get rid of that pesky TempDB database while your at it. 😛 All it does is take up room and cause headaches... saves a lot...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 22, 2008 at 8:00 pm
ashishchap (1/22/2008)
We are storing the information as xml instead of the tables to minimize the storage space. XML is a MUST for our database.
Just a passing thought... maybe even a...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 22, 2008 at 7:49 pm
I'll add a couple of more...
Everyone who doesn't telecommute will hate you (for obvious reasons).
Everyone who doesn't telecommute will perceive you as a slacker unless you produce double the work...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 22, 2008 at 7:40 pm
Heh... I know what you're thinking and "No", do NOT change the order of the columns in the index I recommended 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
January 22, 2008 at 7:31 pm
The PK Clustered Index you have might be good for something else, but it's no good for this query even though the execution plan say's you're using the clustered index......
--Jeff Moden
Change is inevitable... Change for the better is not.
January 22, 2008 at 7:30 pm
For testing purposes, how many file names are we talking about? And, if you don't mind, can you post the CREATE statment for the table, any existing indexs, and...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 22, 2008 at 6:38 pm
Yowch! The data's a bloody mess. Who in their right mind would list the word "NULL" for a null in a transmitted text file nevermind add trailing spaces...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 22, 2008 at 5:40 pm
Steve Rosenbach (1/13/2005)
Jeff, you have expressed more eloquently and in far less words my frustration with ISO-11179... and I only read Part 5 - the part about naming conventions!
Thanks, Steve......
--Jeff Moden
Change is inevitable... Change for the better is not.
January 22, 2008 at 5:17 pm
That's not nice... Matt was spot-on by saying you weren't providing enough information. I simply took a guess and didn't say much more than he did.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 22, 2008 at 5:04 pm
I do. In fact, I wrote an article about it that should be coming out soon! It was submitted way back on 11 Dec 2007...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 22, 2008 at 5:01 pm
And that, folks, is a Triangular join... works seemingly fine on small groups... cripples CPU's on larger groups... be careful...
See the following URL for more details on Triangular joins...
http://www.sqlservercentral.com/articles/T-SQL/61539/
--Jeff Moden
Change is inevitable... Change for the better is not.
January 22, 2008 at 4:10 pm
Simply stated, there is no equivalent for Oracle's spool command. You can use OSQL with a DOS redirect to a file or BCP or DTS or...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 22, 2008 at 2:11 pm
Gregory,
I'm curious... What size (in gig or tera-bytes) is your OLTP and Reporting databases?
--Jeff Moden
Change is inevitable... Change for the better is not.
January 22, 2008 at 1:51 pm
Viewing 15 posts - 52,786 through 52,800 (of 59,098 total)