Home » 2012 » November

Monthly Archives: November 2012

SQL Server 2012 SP1 CU1 Is Now Available !


The 1st cumulative update release for SQL Server 2012 Service Pack 1 is now available for download at the Microsoft Support site.

SQL Server 2012 SP1 CU1 contains fixes released in SQL Server 2012 RTM CU 3 & 4. For those who are upgrading to Service Pack 1 from SQL Server 2012 RTM CU3 or CU4 should consider applying SQL Server 2012 SP1 CU1 to ensure fixes resident on the system are available post upgrade to Service Pack 1.

For CU1 of SQL Server 2012 SP1

Obtain SQL Server 2012 SP1

· Microsoft® SQL Server® 2012 SP1

· Microsoft® SQL Server® 2012 SP1 Express

· Microsoft® SQL Server® 2012 SP1 Feature Pack

· http://mssqlfun.com/2012/11/08/sql-server-2012-sp1-is-now-available/

SQL Server 2008 SP3 CU8 Is Now Available !


The 8th cumulative update release for SQL Server 2008 Service Pack 3 is now available for download at the Microsoft Support site. Cumulative Update 8 contains all the hotfixes released since the initial release of SQL Server 2008 SP3.

Those who are facing severe issues with their environment, they can plan to test CU8 in test environment & then move to Production after satisfactory results.

To other, I suggest to wait for SP4 final release to deploy on your production environment, to have consolidate build.

For CU8 of SQL Server 2008 SP3

Previous Cumulative Update KB Articles:

Restoring a SQL Server 2005 Full-Text Catalog to SQL Server 2012


Upgrading fulltext data from a SQL Server 2005 database to SQL Server 2012 is to restore a full database backup to SQL Server 2012.

The full database backup will include the full-text catalog is required for upgrading & importing a SQL Server 2005 full-text catalog.

Backup from SQL Server 2005

When the database is restored on SQL Server 2012, a new database file will be created for the full-text catalog. The default name of this file is ftrow_catalog-name.ndf. For example, if you catalog-name is userdetails, the default name of the SQL Server 2012 database file would be ftrow_Userdetails.ndf. But if the default name is already being used in the target directory, the new database file would be named ftrow_Userdetails-name{GUID}.ndf, where GUID is the Globally Unique Identifier of the new file.

After the catalogs have been upgraded, the sys.database_files and sys.master_files are updated to remove the catalog entries and the path column in sys.fulltext_catalogs is set to NULL.

File details after restore on SQL 2012

Reference : Rohit Garg (http://mssqlfun.com/)

SSMS 2012 || Connect to Server (Additional Connection Parameters Page)


The Connect to SQL Server Management Studio presents a new Additional Connection Parameters Page. Use the Additional Connection Parameters page to add more connection parameters to the connection string.

Steps to get Additional Connection Parameters page

  1. In Management Studio, on the Query menu, point to Connection, and then click Connect.
  2. In the Connect to dialog box, click Options, and then click the Additional Connection Parameters tab.

What is the use of Additional Connection Parameters page ?

· Additional connection parameters can be any ODBC connection parameter.

· Additional connection parameters should be added in the format ;parameter1=value1;parameter2=value2.

· Parameters added using the Additional Connection Parameters page are added to the parameters selected using the Connect to dialog box options.

· The last instance of each parameter provided overrides any previous instances of the parameter. Parameters added using the Additional Connection Parameters page follow and replace the parameters provided in the Login or Connection Properties tabs. For example, if the Login tab provides SERVER1 as the Server name, and the Additional Connection Parameters page contains ;SERVER=SERVER2, the connection will be made to SERVER2.

· Parameters added using the Additional Connection Parameters page are always passed as plain text.

· Do not include login credentials and passwords in the Additional Connection Parameters page. They will not be encrypted when they are passed across the network. Use the Login tab instead.

· You can use it for both Database engine Services or Analysis Services.

Example :-

1) We have not mention user password in login page

2) We have enter, Server Name, database name, User Name & password like parameter in Additional Connection Parameters Page & we connect successfully on MSDB database with test user.

Helpful Link from MSDN

Reference : Rohit Garg (http://mssqlfun.com/)

Become Microsoft Community Contributor …..


Become Microsoft Community Contributor.

I am very happy after receiving this affiliation from Microsoft last month.

My MCC badge is visible now on MSDN.

Profile Page : http://social.msdn.microsoft.com/profile/rohitgarg/

MCC

 

 

 

 

Reference : Rohit Garg (http://mssqlfun.com/)

SQL Server || Compress & UnComprees Backups in one Media\File


Today, We try to check of SQL server when trying to take Compress & UnCcomprees Backups in one Media\File.

Query No. 1

BACKUP DATABASE DB2

TO DISK = ‘D:\DB2_FULL.BAK’ WITH COMPRESSION

GO

BACKUP DATABASE DB2

TO DISK = ‘D:\DB2_FULL.BAK’ WITH NOINIT

Result : Run Successfully

Explanation : Backup file is formatted to take compressed backup. So without mention COMPRESSION keyword. SQL server process this backup request as COMPRESSED backup.

Query No. 2

BACKUP DATABASE DB2

TO DISK = ‘D:\DB2_FULL2.BAK’ WITH COMPRESSION

GO

BACKUP DATABASE DB2

TO DISK = ‘D:\DB2_FULL2.BAK’ WITH INIT

Result : Run Successfully

Explanation : Backup set is overwritten but file header is intact. Due to which without mention COMPRESSION keyword, SQL server process this backup request as COMPRESSED backup.

Query No. 3

BACKUP DATABASE DB2

TO DISK = ‘D:\DB2_FULL3.BAK’

GO

BACKUP DATABASE DB2

TO DISK = ‘D:\DB2_FULL3.BAK’ WITH INIT,COMPRESSION

Result : Failed

Msg 3098, Level 16, State 2, Line 1

The backup cannot be performed because ‘COMPRESSION’ was requested after the media was formatted with an incompatible structure. To append to this media set, either omit ‘COMPRESSION’ or specify ‘NO_COMPRESSION’. Alternatively, you can create a new media set by using WITH FORMAT in your BACKUP statement. If you use WITH FORMAT on an existing media set, all its backup sets will be overwritten.

Msg 3013, Level 16, State 1, Line 1

BACKUP DATABASE is terminating abnormally.

Explanation : Backup file is formatted to take Uncompressed backup but backup is mention to take in compressed form.

Query No. 4

BACKUP DATABASE DB2

TO DISK = ‘D:\DB2_FULL4.BAK’

GO

BACKUP DATABASE DB2

TO DISK = ‘D:\DB2_FULL4.BAK’ WITH NOINIT,COMPRESSION

Result : Failed

Msg 3098, Level 16, State 2, Line 1

The backup cannot be performed because ‘COMPRESSION’ was requested after the media was formatted with an incompatible structure. To append to this media set, either omit ‘COMPRESSION’ or specify ‘NO_COMPRESSION’. Alternatively, you can create a new media set by using WITH FORMAT in your BACKUP statement. If you use WITH FORMAT on an existing media set, all its backup sets will be overwritten.

Msg 3013, Level 16, State 1, Line 1

BACKUP DATABASE is terminating abnormally.

Explanation : Backup set is overwritten but file header is intact. Due to COMPRESSION keyword, SQL server tried to process this backup request as COMPRESSED backup in Uncompressed file format & got failed.

Happy Diwali………….


Wishing You a Very Happy Diwali…………….

KAHI TIMTIMAHAT HAIN DIYO KI, KAHI SHOR HAAN ATHISBAZI KA

CHAMAK HAAN DIL MAIN, UMEEDO KI KHANAK HAAN

MITHAIYO KA ANAND HAAN, PATHAKO KI JHADI HAAN

YE JEET HAAN SACH KI, YE JASAN HAAN DIWALI KA

Follow

Get every new post delivered to your Inbox.

Join 231 other followers