jump to navigation

Purge WSS_Logging July 11, 2016

Posted by juanpablo1manrique in Best Practices, SharePoint2013, SQL SERVER, SQL SERVER 2008.
Tags: ,
add a comment

Hola,

Liberar espacio de WSS_Logging
Set-SPUsageDefinition -Identity “Analytics Usage” -DaysRetained 1 -Enable
Set-SPUsageDefinition -Identity “App Statistics.” -DaysRetained 1 -Enable
Set-SPUsageDefinition -Identity “Bandwidth Monitoring” -DaysRetained 1 -Enable
Set-SPUsageDefinition -Identity “Content Export Usage” -DaysRetained 1 -Enable
Set-SPUsageDefinition -Identity “Content Import Usage” -DaysRetained 1 -Enable
Set-SPUsageDefinition -Identity “Feature Use” -DaysRetained 1 -Enable
Set-SPUsageDefinition -Identity “File IO” -DaysRetained 1 -Enable
Set-SPUsageDefinition -Identity “Page Requests” -DaysRetained 1 -Enable
Set-SPUsageDefinition -Identity “REST and Client API Action Usage” -DaysRetained 1 -Enable
Set-SPUsageDefinition -Identity “REST and Client API Request Usage” -DaysRetained 1 -Enable
Set-SPUsageDefinition -Identity “Sandbox Request Resource Measures” -DaysRetained 1 -Enable
Set-SPUsageDefinition -Identity “Sandbox Requests” -DaysRetained 1 -Enable
Set-SPUsageDefinition -Identity “SQL Exceptions Usage” -DaysRetained 1 -Enable
Set-SPUsageDefinition -Identity “SQL IO Usage” -DaysRetained 1 -Enable
Set-SPUsageDefinition -Identity “SQL Latency Usage” -DaysRetained 1 -Enable
Set-SPUsageDefinition -Identity “SQL IO Usage” -DaysRetained 1 -Enable
Set-SPUsageDefinition -Identity “Task Use” -DaysRetained 1 -Enable
Set-SPUsageDefinition -Identity “Tenant Logging” -DaysRetained 1 -Enable
Set-SPUsageDefinition -Identity “Timer Jobs” -DaysRetained 1 -Enable
Set-SPUsageDefinition -Identity “User Profile ActiveDirectory Import Usage” -DaysRetained 1 -Enable
Set-SPUsageDefinition -Identity “Definition of usage fields for Education telemetry” -DaysRetained 1 -Enable
Set-SPUsageDefinition -Identity “Definition of usage fields for microblog telemetry” -DaysRetained 1 -Enable
Set-SPUsageDefinition -Identity “Definition of usage fields for service calls” -DaysRetained 1 -Enable
Set-SPUsageDefinition -Identity “Definition of usage fields for SPDistributedCache calls” -DaysRetained 1 -Enable
Set-SPUsageDefinition -Identity “Definition of usage fields for workflow telemetry” -DaysRetained 1 -Enable
Set-SPUsageDefinition -Identity “User Profile to SharePoint Synchronization Usage” -DaysRetained 1 -Enable
Como lo supe

Get-SPUsageDefinition | select Name

 

AND
Sharepoint Central Administration -> Monitoring -> Configure Usage and health data collection-> Log Collection Schedule.

Execute 2 timer jobs “Run Now”

  • Microsoft SharePoint Foundation Usage Data Import
  • Microsoft SharePoint Foundation Usage Data Processing

Saludos

Advertisements

Base de datos en estado Suspect SQL SERVER 2008 September 5, 2011

Posted by juanpablo1manrique in SQL SERVER, SQL SERVER 2008.
Tags:
6 comments

Que hacer cuando una base de datos de SQL SERVER 2008 reporta que esta en estado SUSPECT, (Sin muchas explicaciones … )

  • Apagar servicios de SQL
  • Sacar copia de los archivos .mdf y ldf
  • Subir los servicios de SQL
  • Borrar la base de datos
  • Crear nueva base de datos completamente nueva pero con el mismo nombre de la anterior
  • Detener servicios de SQL
  • Sobreescribir el archivo .mdf con la versión anterior de la base de datos
  • Correr el comando: ALTER DATABASE SharePoint_Config SET EMERGENCY;
  • Correr el comando: ALTER DATABASE SharePoint_Config SET SINGLE_USER;
  • Correr el comando: DBCC checkdb (‘SharePoint_Config’, repair_allow_data_loss);
  • Correr el comando: ALTER DATABASE SharePoint_Config SET ONLINE;
  • Correr el comando: ALTER DATABASE SharePoint_Config SET MULTI_USER;

Si desean ver la versión del procedimiento para SQL SERVER 2005 pueden ingresar a:

http://www.myitforum.com/articles/18/view.asp?id=7381

Migrar usuarios SQL SERVER September 6, 2010

Posted by juanpablo1manrique in DAtabase, Seguridad, SQL SERVER, SQL SERVER 2008, Uncategorized.
Tags:
add a comment

Para migrar usuarios entre servidores de SQL SERVER se Puede seguir este maravilloso Post que encontre:

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

Hacer backups que incluyan los usuarios de base de datos y recuperarlo en la instancia destino, esto solo aplica de 2005 a 2008.

Crear este SP en el Master:

USE master
GO
IF OBJECT_ID (‘sp_hexadecimal’) IS NOT NULL
  DROP PROCEDURE sp_hexadecimal
GO
CREATE PROCEDURE sp_hexadecimal
    @binvalue varbinary(256),
    @hexvalue varchar (514) OUTPUT
AS
DECLARE @charvalue varchar (514)
DECLARE @i int
DECLARE @length int
DECLARE @hexstring char(16)
SELECT @charvalue = ‘0x’
SELECT @i = 1
SELECT @length = DATALENGTH (@binvalue)
SELECT @hexstring = ‘0123456789ABCDEF’
WHILE (@i <= @length)
BEGIN
  DECLARE @tempint int
  DECLARE @firstint int
  DECLARE @secondint int
  SELECT @tempint = CONVERT(int, SUBSTRING(@binvalue,@i,1))
  SELECT @firstint = FLOOR(@tempint/16)
  SELECT @secondint = @tempint – (@firstint*16)
  SELECT @charvalue = @charvalue +
    SUBSTRING(@hexstring, @firstint+1, 1) +
    SUBSTRING(@hexstring, @secondint+1, 1)
  SELECT @i = @i + 1
END

SELECT @hexvalue = @charvalue
GO
 
IF OBJECT_ID (‘sp_help_revlogin’) IS NOT NULL
  DROP PROCEDURE sp_help_revlogin
GO
CREATE PROCEDURE sp_help_revlogin @login_name sysname = NULL AS
DECLARE @name sysname
DECLARE @type varchar (1)
DECLARE @hasaccess int
DECLARE @denylogin int
DECLARE @is_disabled int
DECLARE @PWD_varbinary  varbinary (256)
DECLARE @PWD_string  varchar (514)
DECLARE @SID_varbinary varbinary (85)
DECLARE @SID_string varchar (514)
DECLARE @tmpstr  varchar (1024)
DECLARE @is_policy_checked varchar (3)
DECLARE @is_expiration_checked varchar (3)

DECLARE @defaultdb sysname
 
IF (@login_name IS NULL)
  DECLARE login_curs CURSOR FOR

      SELECT p.sid, p.name, p.type, p.is_disabled, p.default_database_name, l.hasaccess, l.denylogin FROM
sys.server_principals p LEFT JOIN sys.syslogins l
      ON ( l.name = p.name ) WHERE p.type IN ( ‘S’, ‘G’, ‘U’ ) AND p.name <> ‘sa’
ELSE
  DECLARE login_curs CURSOR FOR
      SELECT p.sid, p.name, p.type, p.is_disabled, p.default_database_name, l.hasaccess, l.denylogin FROM
sys.server_principals p LEFT JOIN sys.syslogins l
      ON ( l.name = p.name ) WHERE p.type IN ( ‘S’, ‘G’, ‘U’ ) AND p.name = @login_name
OPEN login_curs

FETCH NEXT FROM login_curs INTO @SID_varbinary, @name, @type, @is_disabled, @defaultdb, @hasaccess, @denylogin
IF (@@fetch_status = -1)
BEGIN
  PRINT ‘No login(s) found.’
  CLOSE login_curs
  DEALLOCATE login_curs
  RETURN -1
END
SET @tmpstr = ‘/* sp_help_revlogin script ‘
PRINT @tmpstr
SET @tmpstr = ‘** Generated ‘ + CONVERT (varchar, GETDATE()) + ‘ on ‘ + @@SERVERNAME + ‘ */’
PRINT @tmpstr
PRINT ”
WHILE (@@fetch_status <> -1)
BEGIN
  IF (@@fetch_status <> -2)
  BEGIN
    PRINT ”
    SET @tmpstr = ‘– Login: ‘ + @name
    PRINT @tmpstr
    IF (@type IN ( ‘G’, ‘U’))
    BEGIN — NT authenticated account/group

      SET @tmpstr = ‘CREATE LOGIN ‘ + QUOTENAME( @name ) + ‘ FROM WINDOWS WITH DEFAULT_DATABASE = [‘ + @defaultdb + ‘]’
    END
    ELSE BEGIN — SQL Server authentication
        — obtain password and sid
            SET @PWD_varbinary = CAST( LOGINPROPERTY( @name, ‘PasswordHash’ ) AS varbinary (256) )
        EXEC sp_hexadecimal @PWD_varbinary, @PWD_string OUT
        EXEC sp_hexadecimal @SID_varbinary,@SID_string OUT
 
        — obtain password policy state
        SELECT @is_policy_checked = CASE is_policy_checked WHEN 1 THEN ‘ON’ WHEN 0 THEN ‘OFF’ ELSE NULL END FROM sys.sql_logins WHERE name = @name
        SELECT @is_expiration_checked = CASE is_expiration_checked WHEN 1 THEN ‘ON’ WHEN 0 THEN ‘OFF’ ELSE NULL END FROM sys.sql_logins WHERE name = @name
 
            SET @tmpstr = ‘CREATE LOGIN ‘ + QUOTENAME( @name ) + ‘ WITH PASSWORD = ‘ + @PWD_string + ‘ HASHED, SID = ‘ + @SID_string + ‘, DEFAULT_DATABASE = [‘ + @defaultdb + ‘]’

        IF ( @is_policy_checked IS NOT NULL )
        BEGIN
          SET @tmpstr = @tmpstr + ‘, CHECK_POLICY = ‘ + @is_policy_checked
        END
        IF ( @is_expiration_checked IS NOT NULL )
        BEGIN
          SET @tmpstr = @tmpstr + ‘, CHECK_EXPIRATION = ‘ + @is_expiration_checked
        END
    END
    IF (@denylogin = 1)
    BEGIN — login is denied access
      SET @tmpstr = @tmpstr + ‘; DENY CONNECT SQL TO ‘ + QUOTENAME( @name )
    END
    ELSE IF (@hasaccess = 0)
    BEGIN — login exists but does not have access
      SET @tmpstr = @tmpstr + ‘; REVOKE CONNECT SQL TO ‘ + QUOTENAME( @name )
    END
    IF (@is_disabled = 1)
    BEGIN — login is disabled
      SET @tmpstr = @tmpstr + ‘; ALTER LOGIN ‘ + QUOTENAME( @name ) + ‘ DISABLE’
    END
    PRINT @tmpstr
  END

  FETCH NEXT FROM login_curs INTO @SID_varbinary, @name, @type, @is_disabled, @defaultdb, @hasaccess, @denylogin
   END
CLOSE login_curs
DEALLOCATE login_curs
RETURN 0
GO

Luego ejecutar desde el master  el procedimiento EXEC sp_help_revlogin, el resultado de este procedimiento ejecutarlo en la instancia destino. Y Listo !!

 

The log shipping primary database INSNAME\DBNAME has backup threshold of 60 minutes and has not performed a backup log operation for 60459 minutes. Check agent log and logshipping monitor information. July 13, 2010

Posted by juanpablo1manrique in Alto Desempeño, Best Practices, Cluster, SQL SERVER, SQL SERVER 2008.
Tags:
add a comment

Realizando estrategias de Logshipping sobre las bases de datos se registró el siguiente error sobre el log de eventos,

The log shipping primary database INSNAME\DBNAME has backup threshold of 60 minutes and has not performed a backup log operation for 60459 minutes. Check agent log and logshipping monitor information.

La base de datos en cuestión yo la borre a mano, así que se perdió y el Job se siguió ejecutando a una base de datos que no existe. Una manera que encontré para solucionar este problema es acceder a las tablas de sistema y eliminar el registro.

La tabla a borrar es,

select * from msdb.dbo.log_shipping_monitor_primary

Asegúrese de borrar solo los registros correctos o eliminara toda la configuración de logshipping de su servidor.

Lo correcto es que antes de borrar la base de datos se elimine la configuración de logshipping

Saludos

Login failed for user ‘NT AUTHORITY\SYSTEM’. Reason: Failed to open the explicitly specified database. March 26, 2010

Posted by juanpablo1manrique in DAtabase, event viewer, IT, SQL SERVER, SQL SERVER 2008, Windows 2008.
Tags:
add a comment

A veces por alguna razon todo esta bien y pumm uno no se conecta y sale un error come este en el eventviewer

Login failed for user ‘NT AUTHORITY\SYSTEM’. Reason: Failed to open the explicitly specified database. [CLIENT: x.x.x.x]

Entonces toca iniciar una sesión por consola, y cambiar el dafault_database

 – Sql autentication

 sqlcmd -S ISQLSHP -d TableroControlDW -U sa -P *******

 – windows autentication

sqlcmd -S CSQLSHP\ISQLSHP -d TableroControlDW

Luego ejecutar

1>ALTER LOGIN sa WITH DEFAULT_DATABASE = availableDB

2>GO

ó

1>ALTER LOGIN [domain\user] WITH DEFAULT_DATABASE = availableDB

 2>GO

Luego Enter Cuando se ejecuta el comando se le cambia la clave a sa Entonces en bueno ejecutar la sentencia

ALTER LOGIN sa WITH PASSWORD = ”

Activity Monitor SQL SERVER 2008 March 12, 2010

Posted by juanpablo1manrique in Activity Monitor, Developer, SQL SERVER, SQL SERVER 2008.
Tags:
add a comment

Para inicar el ACTIVITY MONITOR en SQL SERVER 2008, se da click derecho sobre el SERVER NAME y luego se da click sobre el activity monitor.

Creo que SQL 2008 se olvido de los developers ya que la administración de nosotros es bastante diferente.

Tomado de:

http://social.msdn.microsoft.com/Forums/en/sqlsecurity/thread/288d6f28-5c29-4f2d-8abe-a1ca9a57fc3c

Download AdventureWorks 2008 R2 November CTP February 23, 2010

Posted by juanpablo1manrique in Best Practices, BI, Business Inteligent, Developer, Install, OLAP, SQL SERVER, SQL SERVER 2008, Windows 2008.
add a comment

Recordando que en el isntalador de SQL 2008 no viene incluida la base de datos de AdventureWorks para realizar pruebas y para carga los ejemplos como los de BI con los proyectos de Analysis Services listos para ejecutar me encontre este link donde lo pueden desacargar.

http://msftdbprodsamples.codeplex.com/releases/view/24854#DownloadId=91938

El instalador incluye

AdventureWorks OLTP 2008 R2
AdventureWorks Data Warehouse 2008 R2
AdventureWorks LT 2008 R2
AdventureWorks OLAP Standard 2008 R2
AdventureWorks OLAP Enterprise 2008 R2
AdventureWorks OLTP

AdventureWorks Data Warehouse
AdventureWorks LT
AdventureWorks OLAP Standard
AdventureWorks OLAP Enterprise

Installing a SQL Server 2008 Failover Cluster Using Advanced/Enterprise Installation February 21, 2010

Posted by juanpablo1manrique in Alta Disponibilidad, Alto Desempeño, Cluster, SQL SERVER.
add a comment

Advanced/Enterprise Failover Cluster Install Step 1: Prepare

If you want see this post whit images of the instalatión you can do, download the manual of enterprise cluster here.

  1. Insert the SQL Server installation media, and from the root folder, double-click Setup.exe. To install from a network share, browse to the root folder on the share, and then double-click Setup.exe. For more information about how to install prerequisites, see Before Installing Failover Clustering (http://msdn.microsoft.com/en-us/library/ms189910.aspx). You may be asked to install the prerequisites, if they are not previously installed.

 

Install Windows Installer 4.5. Windows Installer 4.5 is required, and it can be installed by the Installation Wizard. If you are prompted to restart your computer, restart it, and then start SQL Server 2008 Setup again.

  1. After the prerequisites are installed, the Installation Wizard starts the SQL Server Installation Center. To prepare the node for clustering, move to the Advanced page and then click Advanced cluster preparation.

 

  1. The System Configuration Checker runs a discovery operation on your computer. To continue, click OK. You can view the details on the screen by clicking Show Details, or as an HTML report by clicking View detailed report.

 

  1. On the Setup Support Files page, click Install to install the setup support files.

 

  1. The System Configuration Checker verifies the system state of your computer before Setup continues. After the check is complete, click Next to continue. You can view the details on the screen by clicking Show Details, or as an HTML report by clicking View detailed report.

 

  1. On the Product Key page, indicate whether you are installing a free edition of SQL Server or you have a PID key for a production version of the product.

Note: The Product Key and License Terms pages show up after the Setup Support Files page if you already installed the setup support files during a previous installation.

Note: You must specify the same product key on all the nodes that you are preparing for the same failover cluster. 

  1. On the License Terms page, read the license agreement, and then select the check box to accept the license terms and conditions.

 

Click Next to continue. To end Setup, click Cancel.

  1. On the Feature Selection page, select the components for your installation.

 

A description for each component group appears in the right pane after you select the feature name. You can select any combination of check boxes, but only the Database Engine and Analysis Services support failover clustering. Other components will run on a single failover cluster node as a stand-alone feature without failover capability.

You can specify a custom directory for shared components by using the field at the bottom of this page. To change the installation path for shared components, either update the path in the field provided at the bottom of the dialog box, or click the ellipsis button to browse to an installation directory. The default installation path is C:\Program Files\Microsoft SQL Server\.

Note: When you select the Database Engine Services feature, both replication and full-text search are selected automatically. Unselecting any of these subfeatures also unselects the Database Engine Services feature.

  1. On the Instance Configuration page, specify whether to install a default or a named instance.

 

Instance ID — By default, the instance name is used as the Instance ID. This is used to identify installation directories and registry keys for your instance of SQL Server. This is the case for default instances and named instances. For a default instance, the instance name and instance ID would be MSSQLSERVER. To use a non-default instance ID, select the Instance ID text box and provide a value.

Note: Typical stand-alone instances of SQL Server 2008, whether default or named instances, do not use a non-default value for the Instance ID text box.

Important: Use the same InstanceID for all the nodes that are prepared for the failover cluster.

Instance root directory — By default, the instance root directory is C:\Program Files\Microsoft SQL Server\. To specify a nondefault root directory, use the field provided, or click the ellipsis button to locate an installation folder.

Installed instances – The box shows instances of SQL Server that are on the computer where setup is running. If a default instance is already installed on the computer, you must install a named instance of SQL Server 2008. Click Next to continue.

  1. The Disk Space Requirements page calculates the required disk space for the features that you specify, and it compares requirements to the available disk space on the computer where Setup is running.

 

  1. Specify the security policy for the cluster.

The following screenshot displays the cluster security policies for Windows Server 2003. In Windows Server 2003, you cannot leverage service SIDs. Specify domain groups for SQL Server services. All resource permissions are controlled by domain-level groups that include SQL Server service accounts as group members. This is displayed in the following screen shot.

The following screenshot displays the cluster security policies available for Windows Server 2008. In Windows Server 2008 and later versions, service SIDs (server security IDs) are the recommended and default setting. The option to specify domain groups is available but not recommended. For information about service SIDs functionality on Windows Server 2008, see Setting Up Windows Service Accounts (http://msdn.microsoft.com/en-us/library/ms143504.aspx). This is displayed in the following screen shot.

Click Next to continue.

Note: If you are installing a SQL Server 2008 failover cluster instance in a Windows 2000 Server mixed-mode domain, you must use domain global groups for SQL Server Clustered Services.

Note: Windows 2000 Server domain controllers can operate in mixed mode and native mode. Mixed mode enables down-level domain controllers in the same domain.

Work flow for the rest of this procedure depends on the features that you have specified for your installation. You might not see all the pages, depending on your selections.

  1. On the Server Configuration page, on the Service Accounts tab, specify login accounts for SQL Server services. The actual services that are configured on this page depend on the features that you selected to install.

 

You can assign the same login account to all SQL Server services, or you can configure each service account individually. The startup type is set to manual for all cluster-aware services, including full-text search and SQL Server Agent, and cannot be changed during installation. Microsoft recommends that you configure service accounts individually to provide least privileges for each service, where SQL Server services are granted the minimum permissions they have to have complete their tasks. For more information, see SQL Server Configuration – Service Accounts (http://technet.microsoft.com/en-us/library/cc281723.aspx) and Setting Up Windows Service Accounts (http://technet.microsoft.com/en-us/library/ms143504.aspx).

To specify the same login account for all service accounts in this instance of SQL Server, provide credentials in the fields at the bottom of the page.

Security note: Do not use a blank password. Use a strong password.

When you are finished specifying login information for SQL Server services, click Next.

  1. Use the Collation tab to specify nondefault collations for the Database Engine and Analysis Services.

 

  1. Use the FILESTREAM tab to enable FILESTREAM for your instance of SQL Server. Click Next to continue.

 

  1. Use the Reporting Services Configuration page to specify the kind of Reporting Services installation to create. For failover cluster installation, the option is set to “Install, but do not configure the report server.” You must configure Reporting Services after you complete the installation.

 

  1. On the Error and Usage Reporting page, specify the information that you want to send to Microsoft that will help improve SQL Server. By default, options for error reporting and feature usage are enabled.

 

  1. The System Configuration Checker runs one more set of rules to validate your configuration with the SQL Server features that you have specified.

 

  1. The Ready to Install page displays a tree view of installation options that you specified during setup. To continue, click Install.

 

  1. During installation, the Installation Progress page provides status so that you can monitor installation progress as Setup continues.

 

  1. After installation, the Complete page provides a link to the summary log file for the installation and other important notes.

 

  1. To complete the SQL Server installation process, click Close.
  2. If you are instructed to restart the computer, do so now. It is important to read the message from the Installation Wizard when you have finished with setup. For information about setup log files, see How To: View SQL Server Setup Log Files (http://msdn.microsoft.com/en-us/library/ms143702.aspx).
  3. Repeat the previous steps to prepare the other nodes for the failover cluster. You can also use the autogenerated configuration file to run prepare on the other nodes. For more information, see How to: Install SQL Server 2008 Using a Configuration File (http://msdn.microsoft.com/en-us/library/dd239405.aspx).
  4. After preparing all the nodes as described in step 1, run Setup on one of the prepared nodes, preferably the one that owns the shared disk. On the Advanced page of the SQL Server Installation Center, click Advanced cluster completion.

Advanced/Enterprise Failover Cluster Installation Step 2: Complete

 

  1. The System Configuration Checker runs a discovery operation on your computer. To continue, click OK. You can view the details on the screen by clicking Show Details, or as an HTML report by clicking View detailed report.

 

  1. On the Setup Support Files page, click Install to install the setup support files.

 

  1. The System Configuration Checker verifies the system state of your computer before setup continues. After the check is complete, click Next to continue. You can view the details on the screen by clicking Show Details, or as an HTML report by clicking View detailed report.

 

  1. Use the Cluster Node Configuration page to select the instance name prepared for clustering, and specify the network name for the new SQL Server failover cluster. This is the name that is used to identify your failover cluster on the network.

 

Note: This is known as the virtual SQL Server name in earlier versions of SQL Server failover clusters. 

  1. Use the Cluster Resource Group page to specify the cluster resource group name where SQL Server virtual server resources will be located. To specify the SQL Server cluster resource group name. You have two options:
  • Use the list to specify an existing group to use.
  • Type the name of a new group to create.

 

  1. On the Cluster Disk Selection page, select the shared cluster disk resource for your SQL Server failover cluster. The cluster disk is where the SQL Server data will be put. More than one disk can be specified. Available shared disks displays a list of available disks, whether each is qualified as a shared disk, and a description of each disk resource. Click Next to continue.

 

Note: The first drive is used as the default drive for all databases, but can be changed on the Database Engine or Analysis Services configuration pages. 

  1. On the Cluster Network Selection page, specify the network resources for your failover cluster instance:
  • Network settings — Specify the IP type and IP address for your failover cluster instance. On Windows Server 2008 failover clusters, SQL Server supports the use of DHCP addresses. Before choosing this option, make sure that any network security such as firewalls and IPsec in use between this SQL Server and its clients can accommodate server-side DHCP. For example, some firewalls will require a static port for proper configuration of the firewall.

 

Click Next to continue.

Work flow for the rest of this procedure depends on the features that you have specified for your installation. You might not see all the pages, depending on your selections.

  1. On the Database Engine Configuration page, use the Account Provisioning tab to specify the following:
  1.  
  1.  
    • SQL Server administrators – you must specify at least one system administrator for the instance of SQL Server. To add the account under which SQL Server Setup is running, click Add Current User. To add or remove accounts from the list of system administrators, click Add or Remove, and then edit the list of users, groups, or computers that will have administrator privileges for the instance of SQL Server. For more information, see Database Engine Configuration – Account Provisioning (http://technet.microsoft.com/en-us/library/cc281849.aspx).

 

When you are finished editing the list, click OK. Verify the list of administrators in the configuration dialog box. When the list is complete, click Next.

  1. Use the Data Directories tab to specify nondefault installation directories. To install to default directories, click Next.

 

Important: If you specify nondefault installation directories, make sure that the installation folders are unique to this instance of SQL Server. None of the directories in this tab should be shared with directories from other instances of SQL Server. The data directories should be located on the shared cluster disk for the failover cluster. 

  1. Use the Account Provisioning tab to specify users or accounts that will have administrator permissions for Analysis Services. You must specify at least one system administrator for Analysis Services. To add the account under which SQL Server Setup is running, click Add Current User. To add or remove accounts from the list of system administrators, click Add or Remove, and then edit the list of users, groups, or computers that will have administrator privileges for Analysis Services. For more information, see Analysis Services Configuration – Account Provisioning (http://technet.microsoft.com/en-us/library/cc281723.aspx).

 

When you are finished editing the list, click OK. Verify the list of administrators in the configuration dialog box. When the list is complete, click Next.

  1. Use the Data Directories tab to specify nondefault installation directories. To install to default directories, click Next.

 

Important: If you specify nondefault installation directories, make sure that the installation folders are unique to this instance of SQL Server. None of the directories in this tab should be shared with directories from other instances of SQL Server. The data directories should be located on the shared cluster disk for the failover cluster.

  1. The System Configuration Checker runs one more set of rules to validate your configuration with the SQL Server features that you have specified.

 

  1. The Ready to Install page displays a tree view of installation options that you specified during setup. To continue, click Install.

 

  1. During installation, the Installation Progress page provides status so that you can monitor installation progress as Setup continues.

 

  1. After installation, the Complete page provides a link to the summary log file for the installation and other important notes. To complete the SQL Server installation process, click Close.

 

With this step, all the prepared nodes for the same failover cluster are now part of the completed SQL Server failover cluster.

Appendix C: Add Node

Use this procedure to manage nodes for an existing SQL Server failover cluster instance.

Important: To update or remove a SQL Server failover cluster, you must be a local administrator with permission to log in as a service on all nodes of the failover cluster. For local installations, you must run Setup as an administrator. If you install SQL Server from a remote share, you must use a domain account that has read and execute permissions on the remote share.

Setup does not install .NET Framework 3.5 SP1 on a clustered operating system. You must install .NET Framework 3.5 SP1 before you run Setup.

You may need to apply cumulative updates to the original media before you install SQL Server 2008, if you are affected by a known issue in the Setup program. For more information about known issues and detailed instructions, see How to update or slipstream an installation SQL Server 2008 (http://support.microsoft.com/kb/955392).

Note that setup operations for SQL Server failover clustering have changed in this release. To install or upgrade a SQL Server failover cluster, you must run the Setup program on each node of the failover cluster.

To add a node to an existing SQL Server failover cluster, you must run SQL Server Setup on the node that is to be added to the SQL Server failover cluster instance. Do not run Setup on the active node.

To remove a node from an existing SQL Server failover cluster, you must run SQL Server Setup on the node that is to be removed from the SQL Server failover cluster instance.

To Add a Node to an Existing SQL Server 2008 Failover Cluster

  1. Insert the SQL Server installation media, and from the root folder, double-click Setup.exe. To install from a network share, navigate to the root folder on the share, and then double-click Setup.exe. You may be asked to install the prerequisites if they are not previously installed.

 

Install Windows Installer 4.5. Windows Installer 4.5 is required, and it can be installed by the Installation Wizard. If you are prompted to restart your computer, restart, and then start SQL Server 2008 Setup.exe again.

  1. When prerequisites are installed, the Installation Wizard will launch the SQL Server Installation Center. To add a node to an existing failover cluster instance, click Installation in the left-hand pane. Then, click Add node to a SQL Server failover cluster.

 

The System Configuration Checker will run a discovery operation on your computer. To continue, click OK. Setup log files have been created for your installation. For more information about log files, see How To: View SQL Server Setup Log Files (http://msdn.microsoft.com/en-us/library/ms143702.aspx).

  1. On the Product Key page, specify the PID key for a production version of the product. Note that the product key you enter for this installation must be for the same SQL Server 2008 edition as that which is installed on the active node.

Note: The Product Key and License Terms pages show up after the setup support files page if you already installed the setup support files during a previous installation.

  1. On the License Terms page, read the license agreement, and then select the check box to accept the licensing terms and conditions. To continue, click Next. To end Setup, click Cancel.

 

  1. On the Setup Support Files page, click Install to install the setup support files. To install prerequisites, click Install.

 

  1. The System Configuration Checker will verify the system state of your computer before Setup continues. After the check is complete, click Next to continue.

 

  1. On the Cluster Node Configuration page, use the SQL Server instance name box to specify the name of the SQL Server 2008 failover cluster instance that will be modified during this setup operation.

 

  1. On the Service Accounts page, specify login accounts for SQL Server services. The actual services that are configured on this page depend on the features you selected to install. For failover cluster installations, account name and startup type information will be prepopulated on this page based on settings provided for the active node. You must provide passwords for each account.

 

Security note: Do not use a blank password. Use a strong password.

When you are finished specifying login information for SQL Server services, click Next.

  1. On the Error and Usage Reporting page, specify the information to send to Microsoft that will help to improve SQL Server. By default, options for error reporting and feature usage are enabled.

 

  1. The System Configuration Checker will run one more set of rules to validate your computer configuration with the SQL Server features you have specified.

 

  1. The Ready to Add Node page displays a tree view of installation options that you specified during setup.

 

  1. The Add Node Progress page provides status so you can monitor add node progress as Setup proceeds.

 

  1. After installation, the Complete page provides a link to the summary log file for the installation and other important notes. To complete the SQL Server installation process, click Close.

 

  1. If you are instructed to restart the computer, do so now. It is important to read the message from the Installation Wizard when you are done with setup. For more information about setup log files, see How To: View SQL Server Setup Log Files (http://msdn.microsoft.com/en-us/library/ms143702.aspx).

 

Appendix D: Removing a Node

Removing a node makes that node unavailable to the specific instance of SQL Server the RemoveNode action was run against. If you must remove a node that is currently hosting your instance of SQL Server, note that your SQL instance will fail over to another node of the cluster. As a best practice, you should remove nodes that are not running the active SQL Server instance, to avoid this failover scenario. If the node to be removed is currently running the SQL Server failover cluster instance that RemoveNode is executed on, consider moving the group to a node that will not be removed from the cluster during a maintenance window. This can help maintain the maximum uptime and avoid unplanned failovers.

Note: Instances that did not have the RemoveNode part of setup run against them will not be affected by the operation.

To Remove a Node from an Existing SQL Server 2008 Failover Cluster

  1. Insert the SQL Server installation media. From the root folder, double-click Setup.exe. To install from a network share, navigate to the root folder on the share, and then double-click Setup.exe. The Installation Wizard will launch the SQL Server Installation Center. To remove a node from an existing failover cluster instance, click Maintenance in the left-hand pane, and then click Remove node from a SQL Server failover cluster.

 

  1. The System Configuration Checker will run a discovery operation on your computer. To continue, click OK. Setup log files have been created for your installation. For more information about log files, see How To: View SQL Server Setup Log Files (http://msdn.microsoft.com/en-us/library/ms143702.aspx).

 

  1. The System Configuration Checker will verify the system state of your computer before setup continues. After the check is complete, click Next to continue.

 

  1. On the Cluster Node Configuration page, use the drop-down box to specify the name of the SQL Server 2008 failover cluster instance that will be modified during this setup operation. The node that will be removed will be listed in Name of this node.

 

  1. The Ready to Remove page displays a tree view of options that will be removed during setup. To continue, click Remove.

 

  1. During the remove operation, the Remove Node Progress page provides status.

 

  1. The Complete page provides a link to the summary log file for remove node and other important notes. To complete the SQL Server remove node, click Close. For more information about setup log files, see How To: View SQL Server Setup Log Files (http://msdn.microsoft.com/en-us/library/ms143702.aspx).

Best Practices SharePoint – Database Schema Change February 20, 2010

Posted by juanpablo1manrique in Best Practices, Developer, SharePoint, SQL SERVER.
Tags: ,
add a comment

Indicates any change made to the structure or object types associated with a SharePoint database or to the tables included in it. This includes any change to the SQL processing of data, such as triggers or adding new user-defined functions.

Real World Example
A developer wants to store additional data in the SharePoint database by adding new tables or new columns to an existing table.

Technical Details
You can perform a schema change by using a SQL script, by making the change manually, or by using code that has appropriate permissions to access the SharePoint databases. Always scrutinize any custom code or installation script for the possibility that it modifies the SharePoint database.

Support Details
Important:
This type of customization is not supported.

Application of any schema change to the SharePoint database, except as part of a Microsoft-supplied service pack or hot fix, will make the SharePoint environment unsupportable. This type of change should never be applied.

Be sure to give special attention to any custom code you apply so that is does not introduce a database schema change into the environment.