Hardware requirements - Database servers 2013

Component                      Minimum requirement

Processor -                      64-bit, 4 cores for small deployments (fewer than 1,000 users)

                                       64-bit, 8 cores for medium deployments (between 1,000 to 10,000 users)

RAM -                           8 GB for small deployments (fewer than 1,000 users)

                                     16 GB for medium deployments (between 1,000 to 10,000 users)

Hard disk -                    80 GB for system drive

Cannot add an existing SharePoint 2007 list to a Office Access 2007 database

One of my users had this issue .

The user was trying to add an existing list to a access 2007 db . and was getting an error .

Error : You do not have the necessary permissions to use the '<ListName>' object. Have your system administrator or the person who created this object establish the appropriate permissions for you .

After we did some research i found a KB article for the same .

http://support.microsoft.com/kb/924739

In this the Cause is mentioned as

This problem occurs because the Access 2007 database engine disallows columns that have names that contain more than 64 characters

To work around this problem, use only column names that contain less than 64 characters in Windows SharePoint Services lists

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section

Please check out the Steps to reproduce the problem in the KB article (link) provided.

Cannot connect to the configuration database after installing SP2

*** Problem Description ***
BEHAVIOR/SYMPTOMS:
====================

PSConfigUI failing after installing WSS 3.0 SP2

Environment:

===============

Wss 3.0 on a stand alone system

Customer is using the windows internal database

Issue :

After the installation of the sp2 which is included as a critical update in the windows update we face connection issues with Sql

 Error message :

Access to table dbo.spt_values is blocked because the signature is not valid.

Access to table dbo.spt_values is blocked because the signature is not valid.

Access to table dbo.spt_values is blocked because the signature is not valid.

Access to table dbo.spt_values is blocked because the signature is not valid.

 When we run the psconfig

Symptoms:

======

It will start creating n number of sharepoint_config databases without any tables

We will not be able to access the dbo.versions when we try checking the version of the database

We might be able to check for the version of the config database

Resolution :

Download management studio express
Set SQL express to allow tcp/ip and named pipes

Open the connection with the following address

\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query

Backup all the databases from the sql server management studio .

Check with the customization as it will be lost

Tak e a screen shot of

Solution management
AAM
Topology
Databases in the Sql server management studio
Uninstall windows internal database from the add remove programs

Uninstall SharePoint and reboot the server

Install back SharePoint with windows internal database (standalone installation )

Restore all the databases

Attach the database back to the farm

The server should be up and running

Backup of an individual database, Web application, or the entire farm Using Powershell command

Backup-SPFarm -BackupMethod <String> -Directory <String> [-AssignmentCollection <SPAssignmentCollection>] [-BackupThreads <Int32>] [-ConfigurationOnly <SwitchParameter>] [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-Item <String>] [-Percentage <Int32>] [-WhatIf [<SwitchParameter>]]

Or

Backup-SPFarm -ShowTree <SwitchParameter> [-AssignmentCollection <SPAssignmentCollection>] [-ConfigurationOnly <SwitchParameter>] [-Confirm [<SwitchParameter>]] [-Item <String>] [-WhatIf [<SwitchParameter>]]

BackupMethod - Specifies the type of backup file to be created.If a backup is performed with the

–ShowTree parameter, then the BackupMethod parameter is not used.

A full backup is a backup of all the selected data. A differential backup is a backup of all the selected data that has changed since the last full backup. If an item does not support differential backup, then a full backup is performed for that item instead.

The type must be either of the following:

- Full

- Differential

Directory  - Specifies the path where SharePoint 2010 Products stores the backup package it generates. If you have a computer on which Microsoft SQL Server 2008 and an instance of SharePoint 2010 Products are installed, you can use local drive paths. This includes a basic installation. However, if SQL Server 2008 and SharePoint 2010 Products are installed on multiple computers or if you have multiple servers running SharePoint 2010 Products, you must use Universal Naming Convention (UNC) share paths so that the SQL Server database and search components are written to the same location; for example, \\computer_name\volume\Backup).

Multiple backup packages can be stored in the same location. This is the same path that you pass to the Directory parameter of the Restore-SPFarm cmdlet.
The type must be either of the valid paths:
- C:\folder_name

Other parameters are optional .

In the Second command

ShowTree - Displays which objects in the farm will be backed up based on the other parameters passed to the Backup-SPFarm cmdelt, namely the Item parameter. Items that will be excluded from the backup based on the other parameters passed to the Backup-SPFarm cmdlet will be preceded with an asterisk character (*). Items that cannot be backed up will be enclosed in square brackets ([ ]). A backup will not be performed if the ShowTree parameter is present.

Source - http://technet.microsoft.com/en-us/library/ff607881.aspx