Archive for ‘SQL Server 2005’

October 27, 2013

SQL Server Client Network Utitily

If you are working with a number of SQL Server instances or have really complex server/instance names, its good to use aliases with easy naming conventions. The same can be used to connect to SQL Server instancess. For you to create these aliases you can use the SQL Server Client Network utitily programs (cliconfg). Aliases would secure the real instance names of the SQL Server in any case if its exploited by an external hacker.

cliconfg

Launch “cliconfg” by Start > Run > CliConfg. Then go to Alias tab and click the add button to add the alias.

Advertisements
February 20, 2012

SQL Server 2005 Management Studio : Cannot parse script.

I was trying to run a script which i got it from our one of live server. So as usual i tried to run the scripts (file size 112 MB) which i got with the data. Ohhh what the hell, was getting the error  “Cannot parse script.” 😦


was finding a way to sort out this matter. As per that in some of the forum posts it says the SQL Server Management studio is having some limitations with the Query Parser. Just refer this post for more details.

Finally found out we can execute using the sqlcmd prompt as below:

you can find the SQLCMD.exe in the following path:

C:\Program Files\Microsoft SQL Server\90\Tools\Binn

and after that execute the command as below:

sqlcmd -S YOURSQLSERVER\INSTANCENAME -d DataBaseName -i C:\Your Script.sql

By the way the SQLCMD also uses the usual SQL Server 2005 query parser. So it means the above mentioned error is not related to the SQL Server 2005 Parser instead its related to some bug in SQL Server 2005 Management Studio. 🙂

April 25, 2011

Microsoft SQL Server Sample Databases

you can download the sample databases for SQL Server from codeplex.

http://sqlserversamples.codeplex.com

March 15, 2009

Failed to retrieve data for this request Microsoft.Sqlserver.SmoEnum

when i tried to expand the MSDB folder in SQL 2005 Integration Services i got the following error.

“Failed to retrieve data for this request. Microsoft.Sqlserver.SmoEnum”

SQLIntergratoinServices

without any problem Management Studio successfully connects to the Notification Services and was sure too that i have allowed remote connections via named pipes and TCP/IP. But 😦 when i tried to expand the MSDB folder i m getting that error. so i was thinking and trying to find a solution for this.

finally, Hurrah!

the solution is to update a configuration file with the proper servername\instancename.

you have to update the MsDtsSrvr.ini.xml located in the path : C:\Program Files\Microsoft SQL Server\90\DTS\Binn\ MsDtsSrvr.ini.xml as below :

Original file without the modification :

<?xml version=”1.0″ encoding=”utf-8″?>
<DtsServiceConfiguration xmlns:xsd=”http://www.w3.org/2001/XMLSchema” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”>
<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>

file with the updated values :

<?xml version=”1.0″ encoding=”utf-8″?>
<DtsServiceConfiguration xmlns:xsd=”http://www.w3.org/2001/XMLSchema” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”>
<StopExecutingPackagesOnShutdown>true

</StopExecutingPackagesOnShutdown>
<TopLevelFolders>
<Folder xsi:type=”SqlServerFolder”>
<Name>MSDB</Name> <ServerName>MACHINENAME\SQLINSTANCENAME</ServerName>
</Folder>
<Folder xsi:type=”FileSystemFolder”>
<Name>File System</Name>
<StorePath>..\Packages</StorePath>
</Folder>
</TopLevelFolders>
</DtsServiceConfiguration>

more details :

http://msdn.microsoft.com/en-us/library/ms137789(SQL.90).aspx

March 2, 2009

The instance name must be the same as computer name.

when you changed the Computer Name when there is already a SQL Server 2005 instance running (exists) in your system, then you may have to face “The instance name must be the same as computer name” at the time of installing the Microsoft CRM 4.0 Server.

As the solution you have to make sure the exact name of the SQL Server instance running in your computer. for that execute the following command in Query Analyzer :

select @@Servername

if the above commands gives you the output as the old server name

Then execute the following command:

sp_dropserver ‘old_sql_server_instance_name’, ‘droplogins’
GO
sp_addserver ‘new_sql_server_instance_name’, ‘local’
GO

March 1, 2009

The report server cannot decrypt the symmetric key used to access sensitive or encrypted data in a report server database.

Ooops what is this error!!!

when i was configuring MS SQL Reporting Services 2005 on the way to installing Microsoft CRM Server i had to encounter for the error:

"The report server cannot decrypt the symmetric key used to access sensitive or encrypted data in a report server database. You must either restore a backup key or delete all encrypted content. Check the documentation for more information. (rsReportServerDisabled) (rsRPCError)"

the solution for that error is to delete the Encryption Key in the Reporting Services Configuration.

the step is :

Start => Programs => Microsoft SQL Server2005 => Configuration Tools => Reporting Services Configuration => Encryption Keys.

SQLReporting