Viewing 15 posts - 50,956 through 50,970 (of 59,102 total)
Lemme ask again... what's in the TEXT column?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 28, 2008 at 5:09 pm
virgo (4/28/2008)
:w00t: ok Jeff....just in some cases i need to do that way....am using sql server 2005....thanks much for ur reply
Ian's method using ROW_NUMBER() OVER will work just fine, then.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 28, 2008 at 5:06 pm
Zactly...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 28, 2008 at 7:15 am
Heh... thanks Grant... I'm just a wee bit embarrased that I didn't pick up on that before I posted the question. 😛 More COFFEE!:hehe:
--Jeff Moden
Change is inevitable... Change for the better is not.
April 28, 2008 at 7:02 am
So use Robert's function as part of a derived table, join it, and pivot it.
It really would help if the OP would post exactly what output is expected from the...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 28, 2008 at 6:33 am
Never mind...
Master.sys.dm_Exec_SQL_Text is a system table-valued function... I thought it was a system view.
:blush:
--Jeff Moden
Change is inevitable... Change for the better is not.
April 28, 2008 at 6:14 am
Why bother? If you want to update a table with an IDENTITY column, then just do it.
If you're trying to create a query that returns a numbered list, then...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 27, 2008 at 9:01 am
Some have tried to come up with a formula... I've not been very successful at it because it really isn't database size dependent. It's impacted more by what the...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 26, 2008 at 11:30 pm
You bet... let us know how you make out on this problem.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 26, 2008 at 10:57 pm
As with so many types of testing, you must also test your "made up" questions as well. This question actually has two correct answers... made up or not... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
April 26, 2008 at 12:09 pm
It orders by data_id assuming that you want to know the next one. Your example data was not in order by data_id, but I think you may have meant...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 26, 2008 at 11:45 am
Lynn (4/24/2008)
I can't put these tables in a separate db because the application will break.
Oh, yes you can... put the tables in a different DB and either make "surrogate views"...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 26, 2008 at 11:31 am
Just alter the table to add the ID column making sure that it has the IDENTITY property included.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 26, 2008 at 11:28 am
The first 3 things I'd do is...
1. Update to sp2 and apply the latest cumulitive update (#7, I believe).
2. Turn off autoshrink. If it keeps growing, it's...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 26, 2008 at 11:27 am
Thanks for the feedback, Gene, and good luck on your efforts! Let us know if anything comes up... maybe give us some feedback on what you ended up doing....
--Jeff Moden
Change is inevitable... Change for the better is not.
April 26, 2008 at 11:08 am
Viewing 15 posts - 50,956 through 50,970 (of 59,102 total)