| Author |
Topic |
|
shabazz5th
Starting Member
13 Posts |
 Posted - 2009-01-28 : 10:46:28
|
| Hey Guys,We have a web app that runs a stored procedure. In SQL 2000 it works like a charm.But when we upgrade to 2005, it throws an extra single quote around the dates:declare @p10 intset @p10=97exec OCRCMOrdersByStoreOnlyOrders_s @StoreId='3-3024100',@ProductList='',@StartDt=' '2008-11-16 00:00:00:000' ',@EndDt=' '2008-12-27 00:00:00:000' ',@ItemsPerPage=128,@CurrentPageIndex=1,@BeginPageIndex=-1,@EndPageIndex=-1,@CultureCd='en-US',@Count=@p10 outputselect @p10Like I said, in 2000 it works perfect.The regional settings are fine (Canada)We are running SQL2005 sp2 |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2009-01-28 : 11:18:41
|
| How did you upgrade? |
 |
|
|
shabazz5th
Starting Member
13 Posts |
Posted - 2009-01-28 : 11:57:12
|
quote:
Originally posted by sodeep
How did you upgrade?
Hey sodeep, thanks for replying.We performed an upgrade. Is that an issue? |
|
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2009-01-28 : 12:01:32
|
| I am asking 'HOW'? What happens if you put compatability to 80? |
|
|
|
shabazz5th
Starting Member
13 Posts |
Posted - 2009-01-28 : 12:05:08
|
quote:
Originally posted by sodeep
I am asking 'HOW'? What happens if you put compatability to 80?
How? We have a server, it was 2000, we upgraded it to 2005. I guess I'm missing something in your question.As for compatibility, what does that mean? Is there an option to set it to 80? |
|
|
|
revdnrdy
Posting Yak Master
220 Posts |
Posted - 2009-01-28 : 12:13:24
|
quote:
Originally posted by shabazz5th
quote:
Originally posted by sodeep
I am asking 'HOW'? What happens if you put compatability to 80?
How? We have a server, it was 2000, we upgraded it to 2005. I guess I'm missing something in your question.As for compatibility, what does that mean? Is there an option to set it to 80?
Yes you simply go to the database properties and look under the options setting. You can change the compatibility mode therer&r |
|
|
|
shabazz5th
Starting Member
13 Posts |
Posted - 2009-01-28 : 12:34:48
|
quote:
Originally posted by revdnrdy
quote:
Originally posted by shabazz5th
quote:
Originally posted by sodeep
I am asking 'HOW'? What happens if you put compatability to 80?
How? We have a server, it was 2000, we upgraded it to 2005. I guess I'm missing something in your question.As for compatibility, what does that mean? Is there an option to set it to 80?
Yes you simply go to the database properties and look under the options setting. You can change the compatibility mode therer&r
I see, yes, it is set to 80 (SQL 2000) compatible |
|
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2009-01-28 : 12:37:12
|
then change it to 90EXEC sp_dbcmptlevel yourdbname,90 |
|
|
|
koolkeith19
Starting Member
14 Posts |
Posted - 2009-01-28 : 12:38:53
|
| Shabazz I think you need to set your options to EAD |
|
|
|
revdnrdy
Posting Yak Master
220 Posts |
Posted - 2009-01-28 : 12:40:28
|
| In case your interested..Here is a website that lists the differences between the compatibility modes. It was taken from BOL (Books Online) and reproduced.[url]http://geekswithblogs.net/influent1/archive/2007/01/04/102774.aspx[/url]hope that helps !r&R |
|
|
|
shabazz5th
Starting Member
13 Posts |
Posted - 2009-01-28 : 12:42:37
|
quote:
Originally posted by visakh16
then change it to 90EXEC sp_dbcmptlevel yourdbname,90
OK, will do...will post results back here shortly.Thx, |
|
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2009-01-28 : 12:45:17
|
| ok...cheers |
|
|
|
shabazz5th
Starting Member
13 Posts |
Posted - 2009-01-28 : 12:59:44
|
quote:
Originally posted by visakh16
ok...cheers
It WORKED! Thanks guys!!!!!! |
|
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2009-01-28 : 13:04:56
|
Cheers  |
|
|
|
|
SQL 2005 adding extra single quote around dates???