Viewing 15 posts - 57,736 through 57,750 (of 59,101 total)
Yep... I believe you are correctm Gopi... didn't realize the Stor_ID in the Stores table of PUBS was actually a CHAR(4).
Soooooo..... the correct code should look something more like this...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 6, 2006 at 7:46 pm
Funny, I don't see a post here by Ramesh...
So, what did you guys come up with? ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
September 6, 2006 at 7:41 pm
Leifa and David hit the nail on the head... well done.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 6, 2006 at 7:31 pm
Unless you want the log to remember that you deleted 200 million rows, DELETE is NOT the way to go...
TRUNCATE is absolutely the fastest way to empty a table, without...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 6, 2006 at 7:28 pm
Sounds a little whacked but with 250 columns, might not be as whacked as you think...
copy the columns in the SELECT list...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 6, 2006 at 7:18 pm
Just a reminder to everyone that may try... ISQL is deprecated when compared to OSQL. OSQL gives you the full functionality of SQL Server... ISQL does not. Recommend that you...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 6, 2006 at 7:14 pm
CS,
Post the table schema and some example data (hopefully in the form of INSERTs) and I'll give you a dog'n'pony...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 6, 2006 at 7:07 pm
The problem is that carriage returns mean nothing in HTML... your app has to capture user induced line breaks as <br> in order for them to mean anything in HTML.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 6, 2006 at 6:56 pm
Michael,
That means that, using Sreejith's fine example, your code should look something like this...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 6, 2006 at 6:51 pm
I'm just gonna take a guess and say that you didn't actually try it Gopi... works fine from what I can see...
stor_id stor_name stor_address city state zip
-------...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 6, 2006 at 6:46 pm
Sorry... missed the fact that you used "9" as the starting point in the CHARINDEX...
Works great if the prefix is always "Watch" or some other combo of 5 letters... if...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 6, 2006 at 6:14 pm
Shoot... these type of paging routines are so much easier in 2005 with TOP @variable...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 6, 2006 at 6:06 pm
I see what you mean, now... I gotta do some tweekin' because page 0 now sets ROWCOUNT = 0 and the last page takes forever... I'll let you know what...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 6, 2006 at 5:31 pm
Haven't tried any of this using a temp table... what changes do you suggest?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 6, 2006 at 7:22 am
Almost forgot... the routine starts with PAGE 0... you can certainly "fix" that by subtracting 1 for the page parameter or by passing in a pre-decremented page number.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 6, 2006 at 6:26 am
Viewing 15 posts - 57,736 through 57,750 (of 59,101 total)