Hi,

Hopefully someone can help me answer a few quick questions I have regarding
transitioning over to SQL Server 2005.

1) Forms Authentication Extension
----------------------------------------
Is the installation and configuration the same for SQL Server 2005 RS?
Does a new extension need to be developed or can I use the existing
extension we have written for SQL Server 2000 RS.

2) Delivery Extensions
----------------------------------------
Has the API or configuration of delivery extensions changed in SQL Server
2005 delivery extensions? I have a fax delivery extension I have written and
I'd hate to have to go back and rework that code.

3) Web Service Methods
----------------------------------------
Have the web service methods changed in SQL Server 2005? I have report
written a report manager/viewer and batch report genarator/scheduler (think
point + click subscriptions, its pretty slick ;) ) that relies heavily on the
web services exposed in SQL Server 2000 RS and would like to know if I can
just point this at a SQL 2005 RS installation or if I am going to have to go
back in write a new version for SQL 2005 RS.

I just installed SQL Server 2005 today so I am off to read the FAQ and see
if I can answer some of my own questions. I find answers before getting any
replies I will add the answers to this thread to help others in similar
situations.

Thanks,

Hey Nick,

I can attempt to shed some light on the Delivery Extension part of your
question. I'm not sure of all the reasons for it, but I had some
trouble when we upgraded to 2005. We did a fresh install of 2005, so
I cannot answer in terms of the 'upgradability'.

When we first got 2005 installed, I copied the dll from RS to my
solution directory and attempted to build the solution. I couldn't due
to a .NET framework conflict. I'm not entirely sure if I could have
used the old interfaces dll, but I didn't try. I couldn't build the
solution because vs2003 can't use the .NET 2.0 framework. I resorted
to building the solution from the command line. vs2005 would work too.

The good news, is that after I got the command line compile to work,
following the instructions for referencing my dll and configuring CAS,
there weren't any other changes (maybe minor changes) that I had to
make to allow my code to work. I suppose there is always the
possibility that .NET 2.0 could have made something you use obsolete,
but unlikely. I received warnings since I was using the smtp email
class and it appears that it may not be supported in the near future.

Feel free to contact me offline and I can try to explain in more detail
if you have questions about my post. daniel dot lenz at qg dot com .

Regards,

Dan