I had created a multi site SharePoint application using MOSS 2007. My hard drive went south. However, I was able to make an Acronis Image of the drive. I have all the SQL 2005 Server files. I have rebuilt the SharePoint Environment Using Win2k3 Enterprise Server, SQL 2005 Server, WSS 3.0 SP2, and MOSS 2007. I don't want to rebuild the entire site over again.
The original site was in a laptop environment. The new infrastructure is running on a Dell 2970 server.
I was able to restore the SQL Server files from the Acronis image to a USB drive and a DVD. Is there a way to salvage the SQL databases/data to the new server so Sharepoint can access them?
Try this:
Create a new web application on your newly built SharePoint Server.
From Central Admin site, select content database. Select and remove the content database of this new site created in step 1.
Frpm SQL Server Management Strudio create new database with same name as that of your 'salvaged' content database.
Then restore database from your 'salvaged' content database file. Choose 'overwrite' from options..
Back to your Central Admin site, select 'Add Content database' to the new web application you created in step 1 and specify the name of the restored database.
Repeat the process for each web application.
Related
I created a default ASP.NET web form web site using Visual Studio. By default it contains a .mdf database file, Registration page, Login page and some other pages. Then I host this web application on Azure as a web app.
After that I did several registrations for the web site and I need to see the data (data which i used on registration) on the hosted application.
Is there any way to connect to the database file in Azure? In Azure, I did not set up a connection string. I just publish the app and it manages the database connection itself.
There is nothing inside the "Database" section
It seems that you do not publish your asp.net to Azure with Sql Database correctly. So, you could refer to this article to check if you have deploy database correctly.
As you have published, you could go to the database on Azure portal and choose query editor(preview). Click Login and enter the username and password you have set in Azure Sql server.
Also, you could open Microsoft SQL Server Management Studio to get your database. And you also need to login into the Sql Server as above.
After logining into the sql database, you will see all the data you have insert.
BTY, make sure you have synced the data in local database to Azure Sql Database. For more details, you could refer to this article.
I have developed SSIS Package to fetch data from SharePoint Lists and importing to the SQL Server Tables. I am going to deploy this package as a Project Deployment Model.
From these SQL Tables, I have built SSRS Reporting Solution including few reports and Deployed it on my Development SharePoint Site.
But now, I have no idea how to send this solution with reports to the Client Side.
I have checked below utilities but not getting the exact idea of what I should do.
http://rsbuild.codeplex.com/
http://msdn.microsoft.com/en-us/library/ms162839%28v=sql.110%29.aspx
SQL Server version I am using is SQL Server 2012 and Data tools version is also 2012.
Please guide me here.
Thank you,
Mittal.
To deploy your reporting objects, you right-click on the project in Visual Studio then select deploy and configure the server to deploy to.
If you are trying to get an already deployed package, you can use the import wizard:
e.g.
http://msdn.microsoft.com/en-us/library/hh270294.aspx
Then the report server can be accessed by the client browser - e.g. in internet explorer, browse to to: http:
//reportserver/reports
Where "reportserver" can either be the server's ip address or reporting server name.
You can also modify these reports using the report builder tool, that will allow you to edit the rdl files on the server - e.g. when you browse to the reports, you can select edit with report builder.
If you are using sharepoint, you can use sharepoint authentication mode or you can set up access based on active directory groups at the folder level, if the client is browsing to the reports using the web browser.
I am looking for a free DNN community edition website Backup and restore procedure working with DNN 7 and SQL server express 2008 r2.
I usually design and develop website in local PC as my connection speed to the actual server is low. And then I want to publish (deploy) the result in the server. I may need to repeat this procedure a few times as our website is always under development and I need to add new pages or update the existing ones.
I use DNN 7 community edition. I have already googled and have found plenty of commercial tools for this backup and restore. But the free methods seems to be 1.
old or
not working properly or
not a straight forward procedure or
very buggy.
I have gone e.g. through the 4 links given in
http://www.dnnsoftware.com/community-blog/cid/134680/HOW-TO-Move-a-DotNetNuke-installation
without any success.
Could you please help me 1.
how I could develop my website in local PC and then upload the
result in the server?
And later after adding a few new pages in the local PC how I could sync the result with the server?
Thank you very much in advance for your help and consideration.
.
.
.
"when using SQL express, if I simply copy the entire local folder to production (including the APP_DATA folder, which contains the database)." ... How I could just save the newly registered users data in the website's database before copying entire local folder to production and restore this data after copying. In other way, I want to update the page contents and added designs but I don't want to loose newly registered users data between two consecutive website updates. I hope could find a working procedure for this because working online with server is very slow due to my connection speed and I have to keep a replica of the website in the local PC and add new pages or programs in the local PC and then update the result to the server when required. The specs of two systems are as follows:
local PC: Windows 8 Pro (with admin access)
Server (VPS): Windows web server 2008 (with admin access)
1) The easiest way to do this, when using SQL express, is to simply copy the entire local folder to production (including the APP_DATA folder, which contains the database)
2) Repeat step 1, but you'll lose any changes you made in production since the last time you pushed things up.
DNN doesn't really support this type of synchronization as a platform. They tried to offer it in their Enterprise product, but it worked so poorly they scrapped the feature.
I had a SharePoint server, now i want to move this from one machine to another machine.
This is what i did for the migration.
I have just installed sharepoint server in my new machine and i have removed the Sharepoint_config and wss_content databased from the new server. and i have restored both the databases from the old server. Then i tried to run the Central Admin and i got Unable to connect to content database error.
Is replacing the DB is wrong. is there any other way to migrate SP server from one machine to another. I have tried my taking Farm backup and restore i had many problem with that. so i feel replacing DB would be better for me. any suggestions please?
Move SharePoint between servers is a huge effort.
Data in databases are very depends on the SharePoint install and its environments. So, I suggest just re-install the SharePoint on the new server, and then restore site collection backups to the new install.
Install SharePoint Server on the new server machine
Backup site collections from the old server, follow this guide: http://technet.microsoft.com/en-us/library/cc263441(v=office.12).aspx
Create Web Applications on the new server
Restore site collections from the prev. backups, follow this guide: http://technet.microsoft.com/en-us/library/cc262087(v=office.12).aspx
Be aware, if you have farm level customize solutions (developed by Visual Studio) or css files deployed in the LAYOUT folder, don't forget to re-deploy them on the new server.
I guess this question is too old and my answer will not help topicstarter... However, I was looking to refresh my own knowledge on this topic and I feel it will be useful to share it here.
This solution is not good for every SharePoint deployments, of course, it's just a general idea.
And I don't think it suits production environments well... but if you are brave and foolish as myself, you can do it there as well, with some additional precautions like backups and so on.
Here are prerequisites:
SharePoint was initially installed in Farm mode (not in Single Server mode)
Both old and new servers are in the same domain
You know Farm Passphrase used for initial installation
Old server is still intact and accessible from the new server
Steps to do
Skip steps 2-6 if you don't want to move databases to new location
Install SharePoint on the new server and join to existing farm. See
https://technet.microsoft.com/en-us/library/cc261752.aspx for details on joining procedure.
Ensure that the SharePoint is read-only. You can just shut down MS SQL DBEngine service if it's ok for your users.
Install MSSQL Server on the new server or other location you want. Remember, that it's not a good idea to keep SharePoint and MSSQL on the same server if it's not a demo/dev environment
Move all SharePoint databases to the new MSSQL Server. You can simply copy all DB files and attach it to the new SQL, or go full backup and restore way.
Important: Create an SQL client alias on the new server with cliconfg tool. See blogs.msdn.com/b/priyo/archive/2013/09/13/sql-alias-for-sharepoint.aspx for details.
Use your old SQL instance name as alias name. E.g. if your old server had SQL installed alongside with SharePoint on SharePoint.mydomain.com, alias name should be "SharePoint.mydomain.com"
Set Server name for alias to the new SQL location. Something like "NewServer.mydomain.com"
Ensure that you specify correct port number for SQL connection or configure network for default dynamic port. It is not necessary only if you have local SQL server on the same machine.
Create identical SQL client alias on the old server (this is needed to correctly remove old server from farm)
Remove old server from the farm. See this technet article for details
Update DNS settings or whatever you use to point users to the new server.
That's it. Hope it will help someone
I have written an asp.net mvc application that is connected to a Microsoft SQL Server Management Studio database and I want to deploy the application to the webhosting server now. I have managed to get the published code onto the server easily. However, I want to ftp the database I created in Microsoft SQL Server Management Studio to the server. Where are these created databases saved and is it possible to ftp the database to the server. The other issue is the web hosting server is using MS SQL Server Express is that a problem?
Normally shared hosts expect you to place the database in the App_Data folder and use it directly from there.
Here is a page to explain connecting to the database
http://msdn.microsoft.com/en-us/library/ms247257.aspx
To find the database on your system open sql management studio right click the Database and click Properties on the Properties windows click on the Files section to show all associated files with your database.
I would recommend checking your providers documentaion though they might have specific requirments for database deployments