Tag Archives: Administration - Page 8

Is SAC removed in SQL Server 2008?

Posted by on October 13, 2008 No comments

SAC (Surface Area Configuration) is a new tool introduced in SQL Server 2005 to enable, disable, start, or stop the features, services, and remote connectivity of your SQL Server 2005 installations. You can use SQL Server Surface Area Configuration on local and remote servers. The two main operations are performed by SAC are as below

Surface Area Configuration for Services and Connections.

Use Surface Area Configuration for Services and Connections to enable or disable Windows services and remote connectivity

Surface Area Configuration for Features.

Use Surface Area Configuration for Features to enable and disable features of the Database Engine, Analysis Services, and Reporting Services.

In SQL Server 2008 this tool has been moved under SSMS itself, you won’t be able to lauch this tool as a seperate applicaton or from start menu. Lets see how to open SAC in SQL Server 2008.

  • Launch SSMS and connect to the server. (It can be local or remote server)
  • Right click on the servername and selec facet as shown below

  • In the window click on the drop down menu “Facet” and select “Surface Area Configuration” to view SAC.

Here in SQL 2008, SAC provides only feature configuration operation. To perform SQL services related tasks you need to go to SQL server Configuration Manager (SCM) only!

VN:F [1.9.17_1161]
Rating: 4.0/5 (1 vote cast)
VN:F [1.9.17_1161]
Rating: 0 (from 0 votes)

SQL Server 2008 CU1 Released

Posted by on September 23, 2008 No comments

Today the first update for SQL Server 2008 has been released. Cumulative update 1 for SQL Server 2008 is released. For more details check the KB article “Cumulative update package 1 for SQL Server 2008“. Once you applied the package, version for SQL Server 2008 will be updated to 10.00.1763.00.

APPLIES TO

• Microsoft SQL Server 2008 Analysis Services
• Microsoft SQL Server 2008 Community Technology Preview
• Microsoft SQL Server 2008 Developer
• Microsoft SQL Server 2008 Enterprise
• Microsoft SQL Server 2008 Express
• Microsoft SQL Server 2008 Express with Advanced Services
• Microsoft SQL Server 2008 Reporting Services
• Microsoft SQL Server 2008 Standard
• Microsoft SQL Server 2008 Standard Edition for Small Business
• Microsoft SQL Server 2008 Web
• Microsoft SQL Server 2008 Workgroup

VN:F [1.9.17_1161]
Rating: 0.0/5 (0 votes cast)
VN:F [1.9.17_1161]
Rating: 0 (from 0 votes)

SQL Server 2008 Installation errors & Solutions

Posted by on September 4, 2008 2 comments

Question : While installing SQL Server 2008 I’m getting the below error Y? How can I rectify.

Description:
Microsoft .NET Framework 3.5 SP1 has encountered a problem during setup.  Setup did not complete correctly.
Problem signature:
Problem Event Name:    VisualStudio8Setup
Problem Signature 01:    35101
Problem Signature 02:    3.5.30729.01_ORCAS_X86_NET
Problem Signature 03:    CBS
Problem Signature 04:    INST
Problem Signature 05:    F
Problem Signature 06:    gencomp750,{61040379-156d-4ece-b126-ea395a3b2
Problem Signature 07:    BASERET_UNKNOWN
Problem Signature 08:    -
Problem Signature 09:    1058
Problem Signature 10:    WUSA
OS Version:    6.0.6001.2.1.0.256.1
Locale ID:    1033
Additional information about the problem:
LCID:    1033
Read our privacy statement:

http://go.microsoft.com/fwlink/?linkid=50163&clcid=0×0409

Solution: .Net 3.5 is required and its mandatory as part of SQL Server 2008 Installation, hence when you start SQL Server 2008 setup it will first install .Net 3.5. Actually when .Net 3.5 installs it will start downloading the CAB file from the installation location (say your SQL setup folder), for this you need to enable windows update service else it will fail. To correct this problem make sure you have not disabled windows update service.

Read more »

VN:F [1.9.17_1161]
Rating: 0.0/5 (0 votes cast)
VN:F [1.9.17_1161]
Rating: +1 (from 1 vote)

Compatibility Level supported in SQL Server 2008

Posted by on August 19, 2008 No comments

Compatibility Level is the propery set for databases which tells SQL Server how to interpret T-SQL statements. In each compatibility level Microsoft has removed or added some features of T-SQL statements, setting this would allow SQL server to interpret those T-SQL commands and work properly. In SQL server 2008 the following are the compatibility levels supported.

  • 80 (SQL Server 2000)
  • 90 (SQL Server 2005)
  • 100 (SQL Server 2008)

Hence those who are planning to migrate to SQL Server 2008 should change their T-SQL statements (i.e in procedures or functions) if they have any database with compatibility level less than 80 to work well and good in SQL 2008.You can change compatibility level of the database either in GUI under database properties or else using the below system SP “sp_dbcmptlevel".

VN:F [1.9.17_1161]
Rating: 0.0/5 (0 votes cast)
VN:F [1.9.17_1161]
Rating: 0 (from 0 votes)

Moving all databases from one server to another server

Posted by on July 23, 2008 No comments

Introduction

In most of the forums I’m seeing a thread how to move databases from one server to another server. Seeing those things I’ve written this article to simple the task. Here in this article I’m going to provide you some steps to move all the databases (including system db) from one server to another server (hope no error should happen).

Steps to Move the database

Step1: Before detaching the db you need to script default database for all the logins, because if the user db is default db for logins then after detaching the db the login will point NULL and hence when the user logs in he will be in trouble. You can use the script “Script Default Database” to script all the default databases for the logins. Execute the script and save the output.

Step2: Once the above step completed you can detach all the user databases except system db’s (master, msdb, tempdb & model) in the source server. You can use the script “Detach User Databases” to detach all the user databases in the source server.

Step3: Stop SQL Service in the source server and copy all physical files (mdf, ldf & ndf) of the dbs to the destination server

Step4: Once the above step completed successfully, you need to first attach the system databases databases from the new path (i.e the path where you have copied the physical files). You can make use the articles “Moving System Databases – SQL Server 2005” or “Moving system databases — SQL Server 2000” to attach the system databases from new path.

NOTE: For moving system dbs you need to have same SQL edition, version and build in both source and destination servers. If you are not planning to move system db’s just skip this step.

Step5: Attach all the databases in the destination server from the new path.
Step6: Once the above steps completed successfully, start sql services, check errorlog for any errors.
Step7: Once you find everything perfect execute the script (saved in step1) to map all the logins back to its default databases and start using the applications with the respective FIDs.

Discussion

All your healthy discussion in this topic are most welcomed @ FORUMS section.

VN:F [1.9.17_1161]
Rating: 0.0/5 (0 votes cast)
VN:F [1.9.17_1161]
Rating: 0 (from 0 votes)