When I moving database files to another LUN (one for MDF file, and another for LDF file) on storage system (NetApp N5300 Series)
causes PAGEIOLATCH_SH locks. How to solve this problem?
View Complete Post
Hello,I created a ASP.NET project under Visual Web Developer 2008. Under that project I had a Database (along with ASPNETDB.MDF) which has about 3/4 tables (I had SQL server 2008). Everything was working fine (like insert, delete, etc.). And I was able to view the tables in database explorer view.
Then I had to format my computer for some reason and I copied the whole project in a USB drive and then after formatting the computer I copied the folder and tried to open it in Visual Web Developer (now I have VWD 2010). I can see the both Database under App_Data folder (ASPNETDB.mdf and the DB I created). ASPNETDB has all the tables and data as expected. But I do not see the tables under the DB I created.
I also tried in one of my friends computer who has Visual Web Developer 2008. But same result.I am just wondering if anyone can help me with retreiving the table. I have a bad feeling that I might needed to do something to backup the data (not sure though). But the tables should be still there ... isn't it ?Any help will be appreciated. Thank you in advance.
I have successfully followed the white paper for upgrading SharePoint Services 3.0 to SharePoint Foundation 2010. Other than an authentication link problem all went smoothly.
I do have two small problems. The Small Business Server console reports that SharePoint is not functioning (it is functioning as I can connect to the site), this is more a nussance as my daily reports are inaccurate and I hope if this is normal there is
or will be a hotfix to repair the reporting. This also comes to the second more serious problem.
In upgrading the process moved the database from it's own drive back to the system drive. I should have payed more attention to the directories in the upgrade process. Live and learn. Since the reporting is wrong in the console the move database wizard
also does not work. Knowing that SBS gets cranky when things aren't done with a wizard or in a super specific order, is there a proper way to move the database? I am beging to get the long list of warnings as the drive fills up.
Any help would be appreciated. Thank you.
I have a SharePoint 2007 database that is 16GB in size and I want to know why, and how I can reduce the size. Ideally I would like a trimmed replica to use as a developer workstation that retains a good sample data set, and has the ability to be
Can you please tell me if there are any third party tools or other methods to accomplish this? I have found the Microsoft tool (stsadm) to be very limited in this regard.
We have SharePoint and SQL server in a extranet domain. We would like move the SQL server databases for SharePoint to our corporate SQL server (on the corporate domain).
The Corporate domain does not trust the extranet domain, and thus the web farm account cannnot be specified on the corportare SQL instance. If it possible to migrate the databases to a non tusted domain?
I've seen the script to create a new Config database using SQL authentication
psconfig -cmd configdb -create -server <SQL server name> -database <database name> -dbuser <SQL account> -dbpassword <SQL password> -user <AD user account> -password <AD user password>
Can I edit the config of SharePoint to point to the new SQL server, or do I need to create the entire sharepoint enviromnent again and attach the content databases?
I also have a SSP database that's heavily customised for searcvhing and the BDC. Will this need recreating again or can I move the BDC database to the new server and attach?