Importing existing .net sql server site to Sharepoint 2010
-
It looks like an existing ASP.NET site can be imported into Sharepoint 2010. http://www.expertsupdates.com/sharepoint-articles/Converting-an-ASP-Dot-NET-site-into-a-SharePoint-site-2.aspx[^] However, is it possible to import the existing sql server or oracle database to be part of the sharepoint database?
-
It looks like an existing ASP.NET site can be imported into Sharepoint 2010. http://www.expertsupdates.com/sharepoint-articles/Converting-an-ASP-Dot-NET-site-into-a-SharePoint-site-2.aspx[^] However, is it possible to import the existing sql server or oracle database to be part of the sharepoint database?
SharePoint is an ASP.NET based application, so yes, with some modification, existing ASP.NET pages can be added. SharePoint uses several databases, up to 20, depending on the level and license, plus the content databases for each site collection. These databases contain many tables, 114 for the WSS_Content database, with proprietary structures that can easily destroy a SharePoint farm if inappropriately modified. So the short answer is, don't mess with the SharePoint databases directly. You would be better off leaving the existing databases and connecting to it within your pages, or perhaps using them as external lists via BDC.
I know the language. I've read a book. - _Madmatt
-
SharePoint is an ASP.NET based application, so yes, with some modification, existing ASP.NET pages can be added. SharePoint uses several databases, up to 20, depending on the level and license, plus the content databases for each site collection. These databases contain many tables, 114 for the WSS_Content database, with proprietary structures that can easily destroy a SharePoint farm if inappropriately modified. So the short answer is, don't mess with the SharePoint databases directly. You would be better off leaving the existing databases and connecting to it within your pages, or perhaps using them as external lists via BDC.
I know the language. I've read a book. - _Madmatt
Thanks for the input. I guess what I was trying to get at was after I import my ASP.net site to Sharepoint 2010, I would like the appropriate users to be able to make modifications themselves to the content, etc. If I am still pointed to an external database and have not created lists using BDC the wouldn't be able to modify the content (users who don't have permissions to the database). The only option would be to import the site and create the lists using BDC. But at that point would I have to go back to all my .net pages to have them read from those lists and not directly the database?
-
Thanks for the input. I guess what I was trying to get at was after I import my ASP.net site to Sharepoint 2010, I would like the appropriate users to be able to make modifications themselves to the content, etc. If I am still pointed to an external database and have not created lists using BDC the wouldn't be able to modify the content (users who don't have permissions to the database). The only option would be to import the site and create the lists using BDC. But at that point would I have to go back to all my .net pages to have them read from those lists and not directly the database?
Civic06 wrote:
If I am still pointed to an external database and have not created lists using BDC the wouldn't be able to modify the content
Why not? You use a connection string just like your existing application. How are you restricting access right now? Another question is why are you trying to migrate this application to SharePoint? If the data is external and you will continue to use it there, plus its ASP.NET, then what are your hoping to gain from SharePoint?
I know the language. I've read a book. - _Madmatt
-
Civic06 wrote:
If I am still pointed to an external database and have not created lists using BDC the wouldn't be able to modify the content
Why not? You use a connection string just like your existing application. How are you restricting access right now? Another question is why are you trying to migrate this application to SharePoint? If the data is external and you will continue to use it there, plus its ASP.NET, then what are your hoping to gain from SharePoint?
I know the language. I've read a book. - _Madmatt
To be able to use Sharepoints Workflow tools, etc for any changes made by users. An approval process before it goes live. This is one the requirements as well to have all existing sites we have built to be imported into the corporate sharepoint instance. So whether i have a list or not, any user should be able to make modifications to the site...without directly going into the database to make changes.
-
To be able to use Sharepoints Workflow tools, etc for any changes made by users. An approval process before it goes live. This is one the requirements as well to have all existing sites we have built to be imported into the corporate sharepoint instance. So whether i have a list or not, any user should be able to make modifications to the site...without directly going into the database to make changes.
Sorry, but this sounds more like a jump on the bandwagon project to force something into SharePoint that isn't appropriate or necessary. Workflows on what? Approval for what? Do you understand how this works in SharePoint?
I know the language. I've read a book. - _Madmatt