Solutions build in Visual Web Developer and SQL Server 2005

[Søren D]

I have build a small solution in Visual Web Developer, but I have recently
found out that my ISP only supports SQL Server 2005.

They dont support User instance databases either, so I have to find a more
complex way to deploy.

But still, should I expect runtime problems that could be caused by the fact
that my ASP.NET solution uses features in SQL Server 2008 that is not
supported in SQL Server 2005?

Thanks in advance

 

[Guest]

I have build a small solution in Visual Web Developer, but I have recently
found out that my ISP only supports SQL Server 2005.

They dont support User instance databases either, so I have to find a more
complex way to deploy.

But still, should I expect runtime problems that could be caused by the fact
that my ASP.NET solution uses features in SQL Server 2008 that is not
supported in SQL Server 2005?

Thanks in advance

Søren, correct me if I am wrong, you have 2005 Express Edition, right?
Did you deploy your database to ISP server already? What error do you
get in your application? It most likely you need to change connection
string in your application from Integrated Security=SSPI.... to
uid=xxx;pwd=xxx...

 

[sloan]

I'm going to infer
//User instance databases either//
as "They don't support Express Version of databases".
That might be the wrong assumption, but that is how I'm interpretting it.
--That's ok. It means your connection string will be different.

Are you using stored procedures? Or using the built in stuff?

I wouldn't be super concerned. The only issue I foresee is if you use
SqlServer 2008 ~~specific syntax~~ in your stored procedures.

You ~can set the compatability level of the 2008 db "down to" sql server
2005.
http://www.google.com/search?hl=en&q=sql+server+set+compatibility+level&aq=1&oq=Sql+Server+Set+Com

I would do that...you can do it per database. And then you should be in the
clear.

If you're looking for a Membership helper look here:
http://sholliday.spaces.live.com/Blog/cns!A68482B9628A842A!160.entry

You might already have a membership database ...... and you're not
recognizing it as a membershp database.
Follow the blog url above.....and find the scottgu article ... it'll provide
some more hints.