DBA Sensation

October 9, 2009

enable a disabled sql agent service

Filed under: 3. MS SQL Server Tags: enable sys.sp_configure, sql agent, sql server 2005, xp disabled zhefeng @
10:03 am

When SQL Server 2005 Management Studios Object Browser

shows the SQL Server Agent service with a red down arrow and
the text Agent XPs disabled, the service is not started or
disabled.
i had this issue on my sql 2005 active-active cluster even with
sql agent resource started in my cluster admin interface, the
agent actually was not running.
To fix this, you need to open the sql server advance
configuration and enable sql agent, then close the advance
configuration option again:
step 1. open advanced configuration option
exec sys.sp_configure @configname = Nshow advanced
options, @configvalue = 1
reconfigure with override
step 2. change value from 0 to 1 which means enable
exec sys.sp_configure @configname = NAgent XPs,
@configvalue = 1
reconfigure with override
step 3. close advanced configuration option
exec sys.sp_configure @configname = Nshow advanced
options, @configvalue = 0
reconfigure with override
Leave a Comment

May 26, 2009

How to make user to view they jobs in sql 2005

Filed under: 3. MS SQL Server Tags: job, sql server 2005, sqlagent zhefeng @ 2:25 pm

i tried to make user able to see their own jobs in sql 2005. First
thing you need to assign job owner as users account.
Second thing, sql 2005 server has some new server roles (on
MSDB database user only!) for managing sql agent stuff. Here is
the screenshot:

With SQL Server 2005, a user must be a member of one of the

new fixed database roles or a member of the sysadmin fixed
server role to use SQL Server Agent. When users who are not
members of one of these roles are connected to SQL Server in
SQL Server Management Studio, the SQL Server Agent node in
Object Explorer is not visible. After this basic introduction let us
identify what are the specific uses of each role.

SQLAgentUserRole
This is the least privileged role among new three new fixed
server roles. This role has permissions only on operators, local
jobs, and job schedules. These types of users can only view the
operator but they cant create, modify or delete operators. They

cannot change job ownership to gain access to jobs that they

do not already own. SQLAgentUserRole members can view a list
of available proxies only in the Job Step Properties dialog box of
SQL Server Management Studio. These users cannot delete job
history.

SQLAgentReaderRole
SQLAgentReaderRole has all the options that SQLAgentUserRole
has. In addition, it does have permissions to view the list of
available multiserver jobs, their properties, and their history.
Members of this role can also view the list of all available jobs
and job schedules and their properties, not just those jobs and
job schedules that they own.

SQLAgentOperatorRole
SQLAgentOperatorRole is the most privileged of the SQL Server
Agent fixed database roles. It includes all the permissions of
SQLAgentUserRole and SQLAgentReaderRole. Members of this
role can also view properties for operators and proxies, and
enumerate available proxies and alerts on the server.
SQLAgentOperatorRole members have additional permissions
on local jobs and schedules. They can execute, stop, or start all
local jobs, and they can delete the job history for any local job
on the server.
Link: http://www.sqlservercentral.com/articles/Administration/
sqlserveragent2005/2376/
Leave a Comment

April 27, 2009

How to connection sql server named instance SSIS service

Filed under: 3. MS SQL Server Tags: named instance, sql server 2005, ssis zhefeng @ 1:52 pm

Ive occasionally run into the following error when attempting to

connect to SSIS from Management Studio:

"Failed

to retrieve data for this request.

(Microsoft.SqlServer.SmoEnum)
The SQL Server specified in Integration
Services service configuration is not
present or is not available. This might
occur when there is no default instance of
SQL Server on the computer. For more
information, see the topic "Configuring the

Integration Services Service" in SQL Server

2008 Books Online.
Login Timeout Expired
An error has occurred while establishing a
connection to the server. When connecting to
SQL Server 2008, this failure may be caused
by the fact that under the default settings
SQL Server does not allow remote
connections.

Named Pipes Provider: Could not open a

connection to SQL Server [2]. (MsDtsSvr)."
The problem, as it turns out, is that when I installed SQL Server
2005/2008 on a machine, that a default instance was already
installed. In my case SQL Server 2000 was already installed as
the default instance. The initial posts I read (and heard about in
talking to other colleagues who had the same problem) said
that SQL Server 2005/2008 had to be installed as the default
instance if you wanted to be able to use SSIS.
The problem is that unlike the database engine, which can have
many running named instances running, SSIS can only run one
instance on a server at a time. When SQL Server 2005/2008 is
installed there is no option to specify which SQL Server instance
should be used to r
un SSIS. Instead the default configuration is always applied and
SSIS tries to start under the default instance. If the default
instance is SQL Server 2000, you have a problem. You can only
run SSIS on SQL Server 2005 or higher.
Since a server can only run one instance of SSIS you need to
make sure that the config file points to the correct instance of
SQL Server. Locate the MsDtsSrvr.ini.xml configuration fileand
open it with a text or xml editor.
SQL 2005 location:
C:\Program Files\Microsoft SQL
Server\90\DTS\Binn\MsDtsSrvr.ini.xml
SQL 2008 location:
C:\Program Files\Microsoft SQL
Server\100\DTS\Binn\MsDtsSrvr.ini.xml

The default contents of the file:

<?xml version=1.0 encoding=utf-8?>
<DtsServiceConfiguration
xmlns:xsd=http://www.w3.org/2001/XMLSchema&#8221;
xmlns:xsi=http://www.w3.org/2001/XMLSchemainstance&gt;
<StopExecutingPackagesOnShutdown>true
</StopExecutingPackagesOnShutdown>
<TopLevelFolders>
<Folder xsi:type=SqlServerFolder>
<Name>MSDB</Name>

<ServerName>.</ServerName>
</Folder>
<Folder xsi:type=FileSystemFolder>
<Name>File System</Name>
<StorePath>..\Packages</StorePath>
</Folder>
</TopLevelFolders>
</DtsServiceConfiguration>
Notice the ServerName element points to the default instance of
SQL Server (when connecting to the local machine . is the
same as (local) they both use NamedPipes to connect).
Modify the configuration file to point to the named instance as
follows.
<?xml version=1.0 encoding=utf-8?>
<DtsServiceConfiguration
xmlns:xsd=http://www.w3.org/2001/XMLSchema&#8221;
xmlns:xsi=http://www.w3.org/2001/XMLSchemainstance&gt;
<StopExecutingPackagesOnShutdown>true
</StopExecutingPackagesOnShutdown>
<TopLevelFolders>
<Folder xsi:type=SqlServerFolder>
<Name>MSDB</Name>

<ServerName>.\SQL2005</ServerName>
</Folder>
<Folder xsi:type=FileSystemFolder>
<Name>File System</Name>
<StorePath>..\Packages</StorePath>
</Folder>

</TopLevelFolders>
</DtsServiceConfiguration>
After making the change you MUST restart the SSIS service for
the change to take effect.
Another normal issue to connect to SSIS in sqlserver 2005 is
access is denied. The following workground can resolve this
issue(http://msdn.microsoft.com/enus/library/aa337083.aspx):
1.

If the user is not a member of the local Administrators group, add the user to the Distributed COM
Users group. You can do this in the Computer Management MMC snap-in accessed from
theAdministrative Tools menu.

2.

Open Control Panel, double-click Administrative Tools, and then double-click Component Services to
start the Component Services MMC snap-in.

3.

Expand the Component Services node in the left pane of the console. Expand the Computers node,
expand My Computer, and then click the DCOM Config node.

4.

Select the DCOM Config node, and then select MsDtsServer in the list of applications that can be
configured.

5.

Right-click on MsDtsServer and select Properties.

6.

In the MsDtsServer Properties dialog box, select the Security tab.

7.

Under Launch and Activation Permissions, select Customize, then click Edit to open the Launch
Permission dialog box.

8.

In the Launch Permission dialog box, add or delete users, and assign the appropriate permissions to
the appropriate users and groups. The available permissions are Local Launch, Remote Launch, Local
Activation, and Remote Activation. The Launch rights grant or deny permission to start and stop the
service; the Activation rights grant or deny permission to connect to the service.

9.

Click OK to close the dialog box.

10. Under Access Permissions, repeat steps 7 and 8 to assign the appropriate permissions to the
appropriate users and groups.
11. Close the MMC snap-in.
12. Restart the Integration Services service.