The report server has encountered a configuration error. Logon failed for the unattended execution account. (rsServerConfigurationError)
Log on failed. (rsLogonFailed)
The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. (rsInternalError)
Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.

I did not understand this as I have checked the same report 10 minutes ago. So checked the databases and all the connections. Everything seems fine. Now checked the application logs on the server and the errors came up indicating the service accounts access is denied. I was surprised and asked the System Administrator if the permissions were changed on the Active Directory account. The permissions seems to be fine but for some reason the account is locked out. Upon investigation I realised that one of the administrators was trying to use the SQL service account for installing a new SQL server box and typed the password wrong as many a times to make the lockout happen.

Lessons Learnt
a. create a seperate SQL server account for each Live SQL Server Instance
b. Make sure you dont type the password wrong for the Service accounts

select
OBJECT_NAME(ps.object_id) as TableName
,si.Name
,ps.Avg_Fragmentation_in_percent
,STATS_DATE(ss.object_id,ss.stats_id) as LastUpdatedStatistics
from
sys.dm_db_index_physical_stats(DB_ID(DB_NAME()),null,null,null,null) ps
join
sysindexes si
on
ps.object_id = si.id
and
ps.index_id = si.indid
left outer join
sys.stats ss
on
ss.object_id = ps.object_id
and
ss.name = si.name
where
ps.avg_fragmentation_in_percent > 10
order by
ps.avg_fragmentation_in_percent desc

I published the above query in my Reporting services suite of Operational Reports and check it daily morning. The report shows all the Indexes with more than 10% percent fragmentation along with Last updated Statistics time . If you want to go further.You may want to rebuild all the indexes that are above 20% fragmented in TSQL. If there is a better way of doing it please comment.

@Vivekserou

DECLARE @spid VARCHAR(3000)

PRINT @spid

There are 2 ways

a. xp_fixeddrives — The Easy way

b. Ftsutil(xp_cmdshell) — If I want to know the percentage of free space in harddisk use FTSUTIL . The only thing you need to enable is the xp_cmdshell.

Click here to read how to enable XP_cmdshell

Here is the proc

CREATE PROCEDURE [dbo].[usp_GetDiskSpace]
– Add the parameters for the stored procedure here
AS
BEGIN
– SET NOCOUNT ON added to prevent extra result sets from
– interfering with SELECT statements.
SET NOCOUNT ON;

GO

http://msdn.microsoft.com/en-us/library/ms143729.aspx

Created the following Table

Table

Created the Following procedure to enter the current Date

Procedure

and Ran the Job every minute from March 28th 2009 22:50 to Mar 29th 2009 3:00 AM

Results:

daylightsaving-results

There was no 01:00 AM on March 29th !!!!. So any jobs scheduled at 01:00 AM will not run. Sql Agent cannot handle it!!!

select Convert(Varchar(25),server_name) as ‘Server Name’
,convert(varchar(25),database_name) as ‘Database’
,max(backup_finish_date) as ‘Last_backup_date’
from msdb..backupset
Where database_name
in
(select name from master..sysdatabases)
and server_name = @@servername
group by server_name,database_name order by Last_backup_date DESC

I was trying to configure the backups on Sql Server using the Maintenace Plan.

When I opened it . I got the following error

TITLE: Microsoft SQL Server Management Studio

——————————

Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

——————————
ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

——————————

Invalid column name ‘from_msx’.
Invalid column name ‘has_targets’. (Microsoft SQL Server, Error: 207)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.4035&EvtSrc=MSSQLServer&EvtID=207&LinkId=20476

——————————
BUTTONS:

OK
——————————

Analysis:

The resource DB has not been Upgraded to  SP2 version 9.00.3042.00.

The following Script should prove it.

SELECT SERVERPROPERTY(‘ResourceVersion’) as ResourceDB, SERVERPROPERTY(‘ResourceLastUpdateDateTime’) as ResourceDBLastUpdate,

SERVERPROPERTY(‘ProductVersion’) as Ver, SERVERPROPERTY (‘ProductLevel’) as SP;

GO

A specific “msx” table found in the master database, that holds details of maintenance jobs, did not have certain additional columns added to it after the upgrade to SP2.

Solution :

There are 2 solutions to the problem depending on the risk .

Solution 1

Creating the jobs instead of Maintenance Plans for important Tasks

Solution 2

Go to the SQL Install Folder

“C:\Program Files\Microsoft SQL Server\<instance-installation -folder>MSSQL\Install”

like

C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install

and run the sysdbupg.sql script.

That should add the colums to the maintenance tables and the maintenance tasks can be created.

]]> http://www.sqlserver007.com/2009/02/19/problem-with-maintenance-plan-in-sql-server-2005-after-installing-sp3/feed/ 1 http://www.sqlserver007.com/2009/02/15/policy-based-management/ http://www.sqlserver007.com/2009/02/15/policy-based-management/#comments Sun, 15 Feb 2009 23:32:46 +0000 Vivek http://sqlserver007.wordpress.com/?p=3 Policy-Based Management(PBM) is the expansion of advanced DDL trigger mechanisms on the Server. Think of the following things

a. How do I allow the users to create the table in specific naming conditions like starting only with ‘T’?

b. How about checking the availability of the latest Sql Server backups?

c. How about limiting the number of CPU in a sql server?

Yes there are countless of server management applications with the PBM.Each POLICY is based on a CONDITION and each CONDITION decides the state of a specific target(like databases,tables,stored procedures etc.) with respect to a particular FACET.

There are a list of builtin policies available on the Sql server 2008 by default. They can be imported from the following location C:\Program Files\Microsoft SQL Server\100\Tools\Policies. All the policies can be imported and exported as they are configured in XML.The Developers can themselves create their own facets depending on their Organisation policies.

More on application of policies coming soon..