Viewing 15 posts - 646 through 660 (of 1,183 total)
Changing the compatibility level is in fact that easy. Whether you'll have bugs in the procs or elsewhere is a separate question, but if you're just transferring data manually or...
December 21, 2007 at 4:36 am
karthikeyan,
Now that was a fun little exercise! Below is a function that will return a table.
CREATE FUNCTION [dbo].[fnCountCharacterOccurrence]
(@String NVARCHAR(4000))
RETURNS @Results TABLE (item NCHAR(1), itemCount INT)
AS
BEGIN
...
December 21, 2007 at 4:29 am
Can you please explain what you want with a bit more detail?
Please read the following post, and then try again. 😀
December 20, 2007 at 4:13 pm
😀
Those replies just show how much I know, but then again, I haven't had any experience with large DBs.
😀
December 20, 2007 at 9:21 am
I would guess this would be a question to help determine your ability in writing optimized queries/procs. As the size of the DB grows so would the need for optimized...
December 20, 2007 at 8:10 am
SELECT TABLE_NAME FROM information_schema.columns WHERE COLUMN_NAME = '.....'
December 19, 2007 at 9:44 am
robert@robertspencer.com (12/18/2007)
Too bad a proc can't return more than one dataset.
Thanks,
Robert
Actually a proc CAN return more than one dataset. :w00t: We're doing it in our .NET application. Now I'm not...
December 18, 2007 at 10:59 pm
I'm not sure if your performing the calculations in your code in in the report itself. If you're doing the calcs in the report, move them into the procedures instead....
December 18, 2007 at 8:25 pm
It's 1.02 to the 36th power or
1.02*1.02*1.02*1.02*1.02*1.02*1.02*1.02
*1.02*1.02*1.02*1.02*1.02*1.02*1.02*1.02
*1.02*1.02*1.02*1.02*1.02*1.02*1.02*1.02
*1.02*1.02*1.02*1.02*1.02*1.02*1.02*1.02
*1.02*1.02*1.02*1.02
=2.039887
Which in your example has been rounded up.
😀
December 18, 2007 at 8:20 pm
...and there's always the possibility of rewriting the query. Can you post it so we can take a look to see if there's something to be done there?
December 18, 2007 at 4:58 am
Matt Miller (12/17/2007)
Using that proprietary thing right there is the reason you're jammed up. Looks to...
December 17, 2007 at 11:08 am
Being that your procedure does all of that, IMHO you are stuck with looping of some sort.
You can always use a temp table and loop through an IDENTITY column...
December 17, 2007 at 11:00 am
Viewing 15 posts - 646 through 660 (of 1,183 total)