Sharepoint 2007 is built on top ASP.NET 2.0, and subsequent versions will follow this path - read more about it on [url=http://weblogs.asp.net/scottgu/archive/2006/04/30/SharePoint-2007-_2D002D00_-Built-on-ASP.NET-2.0-.aspx]ScottGu's blog[/url]. Since MonoX uses standard Web part architecture ([url=http://msdn.microsoft.com/en-us/library/e0s9t4ck.aspx]more on ASP.NET Web parts[/url]). To quote Scott,

... you can now use ASP.NET 2.0 features (Forms Authentication, Master Pages, Membership, Site Navigation, New Data Controls, etc) when building SharePoint sites. This is true for both the new Windows SharePoint Services 3.0 version (which will be a free download) as well as Microsoft Office SharePoint Server 2007 (which costs money).

One of the cool developer scenarios is the ability to create your own Web Part controls that can be used in both SharePoint sites, as well as regular vanilla ASP.NET 2.0 applications. This allows you to re-use all of the built-in SharePoint features for collaboration, document sharing, and content management - while also adding your own custom UI and behaviors (for example: if you want to integrate custom data editing and reporting to a site).

[url=http://www.codeguru.com/csharp/.net/net_asp/webforms/article.php/c12293/]Sahil Malik[/url] and [url=http://weblog.vb-tech.com/nick/archive/2006/05/10/1563.aspx]Nick Swan[/url] wrote two nice articles with practical tips on how to use ASP.NET 2.0 Web parts in SharePoint 2007.

Hi all,

I have a question,

I am busy with implementing a sharepoint website (portal) for various clients, to let them login to the portal and view files which are ment for them. As a database I use SQL Server. My question is :

I can back-up the sharepoint farm using the admin panel in moss2007
I can backup the SQL Server db from sql studio

What if the sql server is not available ? If it's out or offline ? Since all the files are directly written on the database. This is strange, because if something happens to the SQL Server, the clientts won't be able to download their data , I am right ??

What can I do to prevent this ? And is this the best way to backup the site ?

It would be great to have your views on this,

Best Regards ,

zarba

Hi Zarba,
You will need to have at least one additional SQL Server to implement one of the failover techniques:
- log shipping (see [url=http://www.sql-server-performance.com/articles/clustering/log_shipping_70_p1.aspx]http://www.sql-server-performance.com/articles/clustering/log_shipping_70_p1.aspx[/url] for more info)
- mirroring ([url=http://searchsqlserver.techtarget.com/news/interview/0,289202,sid87_gci1167863,00.html]http://searchsqlserver.techtarget.com/news/interview/0,289202,sid87_gci1167863,00.html[/url])
- failover clustering ([url=http://www.databasejournal.com/features/mssql/article.php/3444181/SQL-Server-2005-Part-3---High-Availability-and-Scalability-Enhancements---Failover-Clustering.htm]http://www.databasejournal.com/features/mssql/article.php/3444181/SQL-Server-2005-Part-3---High-Availability-and-Scalability-Enhancements---Failover-Clustering.htm[/url])

Each of these techniques is suited to different usage scenarios; we had good experiences with both log shipping (probably the simplest solution) and database mirroring.

Regards,

Denis