ERROR :

Error Message 1 :

Executed as user: Domain\UserName. SSIS error. Component name: DFT – Upload collection snapshot, Code: -1071636372, Subcomponent: RFS – Read Current Upload Data [1], Description: String too long. The adapter read a string that was 50331648 bytes long, and expected a string no longer than 129 bytes, at offset 12901. This could indicate a damaged input file. The file shows a string length that is too large for the buffer column. . SSIS error. Component name: DFT – Upload collection snapshot, Code: -1073450952, Subcomponent: SSIS.Pipeline, Description: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on component "RFS – Read Current Upload Data" (1) returned error code 0x80004005. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure. .The master package exited with error, previous error messages should explain the cause. Process Exit Code 5.

Error Message 2 :

Executed as user: : Domain\UserName. SSIS error. Component name: DFT – Collect Query 0, Code: -1071636383, Subcomponent: Raw File Destination [57], Description: The file had bad version and flags information. The file is damaged or not a SSIS-produced raw data file. . SSIS error. Component name: DFT – Collect Query 0, Code: -1071636383, Subcomponent: Raw File Destination [48], Description: The file had bad version and flags information. The file is damaged or not a SSIS-produced raw data file. .SSIS error. Component name: DFT – Collect Query 0, Code: -1073450982, Subcomponent: SSIS.Pipeline, Description: component "Raw File Destination" (57) failed the pre-execute phase and returned error code 0xC0202061. . SSIS error. Component name: DFT – Collect Query 0, Code: -1073450982, Subcomponent: SSIS.Pipeline, Description: component "Raw File Destination" (48) failed the pre-execute phase and returned error code 0xC0202061. .The master package exited with error, previous error messages should explain the cause. Process Exit Code 5. The step failed.

REASON : Cache files is having issue. When Collection jobs trying to upload cache files, job is getting failed.

SOLUTION :

1. Start SQL Server Management Studio, and connect to the instance of SQL Server where the error occurs.

2. Expand the Management folder, right-click Data Collection, and select Properties.

3. Cache directory displayedis the location of the Data Collector cache files. Go to step 5.

4. If a directory is not displayed for Cache directory, the default cache directory is the local temporary directory of the account that executes the collection set. This account may be the SQL Server Agent service account. For example, on Windows Server 2008, if the collection set was executed by an account that is named "SQLSERVICEACCOUNT," this account’s temporary directory is located in a path that resembles the following: C:\Users\ SQLSERVICEACCOUNT\AppData\Local\Temp.

5. Find all files that have a *.CACHE file name extension, and move the files to a different directory.

6. Now wait for next run of collection set jobs.

Reference Article : https://support.microsoft.com/en-us/kb/2019126

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

You can find and follow MSSQLFUN :-

http://www.facebook.com/mssqlfun

http://mssqlfun.com/feed

https://twitter.com/Rgarg86

Other Linked Profiles :-

http://www.sqlservercentral.com/blogs/mssqlfun/

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

http://www.toadworld.com/members/rohit-garg/blogs/default.aspx

http://beyondrelational.com/members/RohitGarg/default.aspx

Data Compression

Data Compression is feature of Microsoft SQL Server to reduce the size of table on the basis of Duplicates, Null & Zeroes. It’s a process of reducing size of database & its objects by increasing CPU cycle and reducing I/O effort.

Types of Database Compression

· Row Compression

· Page Compression

You can download Data Compression SQL Server white Paper – https://mssqlfun.files.wordpress.com/2015/10/data-compression-sql-server-white-paper1.pdf

Implementation of Data Compression

Row Compression	Page Compression
T-SQL Command
ALTER TABLE <TABLE_NAME> WITH (DATA_COMPRESSION=ROW)	ALTER TABLE <TABLE_NAME> WITH (DATA_COMPRESSION=PAGE)
SSMS
Step 1 – Open Data Compression wizard. Right Click on Table > Storage > Manage Compression
Step 2 – Select Compression Type & you can click on calculate to check the impact
You can use below system store procedure to estimate the compression results
EXEC sp_estimate_data_compression_savings ‘Schema’,’Table_Name’,Null,Null,’Type_of_Compression’
Step 3 – Select Option if you want to run it immediately or later by generating script
Step 4 – Final Configuration window before you give final go ahead
Step 5 – Compression implemented successfully

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

You can find and follow MSSQLFUN :-

http://www.facebook.com/mssqlfun

http://mssqlfun.com/feed

https://twitter.com/Rgarg86

Other Linked Profiles :-

http://www.sqlservercentral.com/blogs/mssqlfun/

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

http://www.toadworld.com/members/rohit-garg/blogs/default.aspx

http://beyondrelational.com/members/RohitGarg/default.aspx

ERROR :

Error Message 1 :

Executed as user: Domain\UserName. SSIS error. Component name: DFT – Upload collection snapshot, Code: -1071636372, Subcomponent: RFS – Read Current Upload Data [1], Description: String too long. The adapter read a string that was 50331648 bytes long, and expected a string no longer than 129 bytes, at offset 12901. This could indicate a damaged input file. The file shows a string length that is too large for the buffer column. . SSIS error. Component name: DFT – Upload collection snapshot, Code: -1073450952, Subcomponent: SSIS.Pipeline, Description: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on component "RFS – Read Current Upload Data" (1) returned error code 0x80004005. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure. .The master package exited with error, previous error messages should explain the cause. Process Exit Code 5.

Error Message 2 :

Executed as user: : Domain\UserName. SSIS error. Component name: DFT – Collect Query 0, Code: -1071636383, Subcomponent: Raw File Destination [57], Description: The file had bad version and flags information. The file is damaged or not a SSIS-produced raw data file. . SSIS error. Component name: DFT – Collect Query 0, Code: -1071636383, Subcomponent: Raw File Destination [48], Description: The file had bad version and flags information. The file is damaged or not a SSIS-produced raw data file. .SSIS error. Component name: DFT – Collect Query 0, Code: -1073450982, Subcomponent: SSIS.Pipeline, Description: component "Raw File Destination" (57) failed the pre-execute phase and returned error code 0xC0202061. . SSIS error. Component name: DFT – Collect Query 0, Code: -1073450982, Subcomponent: SSIS.Pipeline, Description: component "Raw File Destination" (48) failed the pre-execute phase and returned error code 0xC0202061. .The master package exited with error, previous error messages should explain the cause. Process Exit Code 5. The step failed.

REASON : Cache files is having issue. When Collection jobs trying to upload cache files, job is getting failed.

SOLUTION :

1. Start SQL Server Management Studio, and connect to the instance of SQL Server where the error occurs.

2. Expand the Management folder, right-click Data Collection, and select Properties.

3. Cache directory displayedis the location of the Data Collector cache files. Go to step 5.

4. If a directory is not displayed for Cache directory, the default cache directory is the local temporary directory of the account that executes the collection set. This account may be the SQL Server Agent service account. For example, on Windows Server 2008, if the collection set was executed by an account that is named "SQLSERVICEACCOUNT," this account’s temporary directory is located in a path that resembles the following: C:\Users\ SQLSERVICEACCOUNT\AppData\Local\Temp.

5. Find all files that have a *.CACHE file name extension, and move the files to a different directory.

6. Now wait for next run of collection set jobs.

Reference Article : https://support.microsoft.com/en-us/kb/2019126

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

You can find and follow MSSQLFUN :-

http://www.facebook.com/mssqlfun

http://mssqlfun.com/feed

https://twitter.com/Rgarg86

Other Linked Profiles :-

http://www.sqlservercentral.com/blogs/mssqlfun/

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

http://www.toadworld.com/members/rohit-garg/blogs/default.aspx

http://beyondrelational.com/members/RohitGarg/default.aspx

Thanks every one for loving me, joining me & providing you extreme support.

I am very happy to share that we reach to 500+ milestone.

Please keep supporting us & liking us.

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

You can find and follow MSSQLFUN :-

http://www.facebook.com/mssqlfun

http://mssqlfun.com/feed

https://twitter.com/Rgarg86

Other Linked Profiles :-

http://www.sqlservercentral.com/blogs/mssqlfun/

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

http://www.toadworld.com/members/rohit-garg/blogs/default.aspx

http://beyondrelational.com/members/RohitGarg/default.aspx

ISSUE : Today, My Friend is facing issue with SQL Server error logs on one of my production server. SQL Server is not able to read SQL server error log files. We have checked that SQL Server Error log files are accessible on file system.

1) When we are running SP_readerrorlog, XP_readerrorlogs or XP_enumerrorlogs, query keeps running without showing results.

2) When We try to browse error logs from SQL Server GUI, the wizard is also hanging.

FINDINGS :

1) We found all sessions running & stuck on waittype “PREEMPTIVE_OS_GETPROCADDRESS”

PREEMPTIVE_OS_GETPROCADDRESS is a new wait type that was introduced in SQL Server 2008 to track time taken by GetProcAddress to load the entrypoint in the DLL when Extended Stored Procedure calls are made by the SQL Server instance.

2) We check what is actually SP_readerrorlog, XP_readerrorlogs or XP_enumerrorlogs trying to execute. As we all know, all this 3 store procedures are extended store procedure. Moreover, running same xpstart.dll

3) Other extended store procedures are working fine.

RESOLUTION :We have rebooted the server so that call to xpstar.dll will work properly.

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

You can find and follow MSSQLFUN :-

http://www.facebook.com/mssqlfun

http://mssqlfun.com/feed

https://twitter.com/Rgarg86

Other Linked Profiles :-

http://www.sqlservercentral.com/blogs/mssqlfun/

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

http://www.toadworld.com/members/rohit-garg/blogs/default.aspx

http://beyondrelational.com/members/RohitGarg/default.aspx

The 16th cumulative update release for SQL Server 2012 Service Pack 1 is now available for download at the Microsoft Support site. Cumulative Update 16 contains all the hotfixes released since the initial release of SQL Server 2012 SP1.

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

Although, I prefer to have SP2 with latest CU in your environment.

NOTE: This is the final Cumulative Update for SQL Server 2012 Service Pack 1. SQL Server 2012 SP1 exits service pack support on July 14, 2015.

KB Article For CU16 of SQL Server 2012 SP1

• CU#16 KB Article: http://support.microsoft.com/kb/3052476

Previous Cumulative Update KB Articles:

• CU#15 KB Article: http://support.microsoft.com/kb/3038001
• CU#14 KB Article: http://support.microsoft.com/kb/3023636
• CU#13 KB Article: http://support.microsoft.com/kb/3002044

· CU#12 KB Article: http://support.microsoft.com/kb/2991533

· CU#11 KB Article: http://support.microsoft.com/kb/2975396

· CU#10 KB Article: http://support.microsoft.com/kb/2954099

· CU#9 KB Article: http://support.microsoft.com/kb/2931078

· CU#8 KB Article: http://support.microsoft.com/kb/2917531

· CU#7 KB Article: http://support.microsoft.com/kb/2894115

· CU#6 KB Article: http://support.microsoft.com/kb/2874879

· CU#5 KB Article: http://support.microsoft.com/kb/2861107

· CU#4 KB Article: http://support.microsoft.com/kb/2833645

· CU#3 KB Article: http://support.microsoft.com/kb/2812412

· CU#2 KB Article: http://support.microsoft.com/kb/2790947

· CU#1 KB Article: http://support.microsoft.com/kb/2765331

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

You can find and follow MSSQLFUN :-

http://www.facebook.com/mssqlfun

http://mssqlfun.com/feed

https://twitter.com/Rgarg86

Other Linked Profiles :-

http://www.sqlservercentral.com/blogs/mssqlfun/

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

http://www.toadworld.com/members/rohit-garg/blogs/default.aspx

http://beyondrelational.com/members/RohitGarg/default.aspx

The 6th cumulative update release for SQL Server 2012 Service Pack 2 is now available for download at the Microsoft Support site. Cumulative Update 6 contains all the hotfixes released since the initial release of SQL Server 2012 SP2.

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

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

KB Article For CU6 of SQL Server 2012 SP2

• CU#6 KB Article: http://support.microsoft.com/kb/3052468

Previous Cumulative Update KB Articles:

• CU#5 KB Article: http://support.microsoft.com/kb/3037255
• CU#4 KB Article: http://support.microsoft.com/kb/3007556
• CU#3 KB Article: http://support.microsoft.com/kb/3002049
• CU#2 KB Article: http://support.microsoft.com/kb/2983175
• CU#1 KB Article: http://support.microsoft.com/kb/2976982

Download Link of SQL Server 2012 SP2 :

SQL Server 2012 SP2 : http://www.microsoft.com/en-us/download/details.aspx?id=43340

SQL Server 2012 SP2 EXPRESS : http://www.microsoft.com/en-us/download/details.aspx?id=43351

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

You can find and follow MSSQLFUN :-

http://www.facebook.com/mssqlfun

http://mssqlfun.com/feed

https://twitter.com/Rgarg86

Other Linked Profiles :-

http://www.sqlservercentral.com/blogs/mssqlfun/

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

http://www.toadworld.com/members/rohit-garg/blogs/default.aspx

http://beyondrelational.com/members/RohitGarg/default.aspx

Finally after a long waiting period, Microsoft release SQL Server 2014 Service Pack 1 (SP1), Same is now available for download at the Microsoft Support site. SQL Server 2014 Service Pack 1 (SP1) contains all the hotfixes released since the initial release of SQL Server 2014 RTM.

I suggest to test SQL Server 2014 Service Pack 1 (SP1) in test environment & then move to Production after satisfactory results.

KB Article For SQL Server 2014 Service Pack 1 (SP1) – https://support.microsoft.com/en-us/kb/3058865

Download Link – http://www.microsoft.com/en-us/download/details.aspx?id=46694

Express Edition Download Link – http://www.microsoft.com/en-us/download/details.aspx?id=46697

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

You can find and follow MSSQLFUN :-

http://www.facebook.com/mssqlfun

http://mssqlfun.com/feed

https://twitter.com/Rgarg86

Other Linked Profiles :-

http://www.sqlservercentral.com/blogs/mssqlfun/

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

http://www.toadworld.com/members/rohit-garg/blogs/default.aspx

http://beyondrelational.com/members/RohitGarg/default.aspx

Steps of Moving MSDB & Model SQL Server system Database to new locaation:-

1) Check current location of MSDB & Model Databases by executing below query

SELECT name, physical_name AS CurrentLocation, state_desc

FROM sys.master_files

WHERE database_id in (DB_ID(‘MODEL’),DB_ID(‘MSDB’));

You can also use “Execc SP_HelpDB ‘<DBNAME>’ for these details.

2) Execute Alter Database command with mofigy file option to set file loccation for dataabase

USE MASTER;

GO

ALTER DATABASE MSDB MODIFY FILE (NAME = MSDBDATA,

FILENAME=’E:\SQL2K5_1\Model\model.mdf’);

GO

ALTER DATABASE MSDB MODIFY FILE (NAME = MSDBLOG,

FILENAME=’E:\SQL2K5_1\Model\modellog.ldf’);

GO

USE MASTER;

GO

ALTER DATABASE MODEL MODIFY FILE (NAME = MODELDEV,

FILENAME=’E:\SQL2K5_1\Model\MSDBDATA.mdf’);

GO

ALTER DATABASE MODEL MODIFY FILE (NAME = MODELLOG,

FILENAME=’E:\SQL2K5_1\Model\MSDBLOG.ldf’);

GO

OUTPUT :-

The file “MSDBDATA” has been modified in the system catalog. The new path will be used the next time the database is started.

The file “MSDBLOG” has been modified in the system catalog. The new path will be used the next time the database is started.

The file “MODELDEV” has been modified in the system catalog. The new path will be used the next time the database is started.

The file “MODELLOG” has been modified in the system catalog. The new path will be used the next time the database is started.

3) Stop SQL Services

4) Manually Move MSDB & Model Databases files to new location

5) Start SQL Services

6) Check MSDB & Model Databases file location after movement

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

You can find and follow MSSQLFUN :-

http://www.facebook.com/mssqlfun

http://mssqlfun.com/feed

https://twitter.com/Rgarg86

Other Linked Profiles :-

http://www.sqlservercentral.com/blogs/mssqlfun/

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

http://www.toadworld.com/members/rohit-garg/blogs/default.aspx

http://beyondrelational.com/members/RohitGarg/default.aspx

Question : Database snapshot captures only data changes or it will also save real database from DDL changes (like table structure, store procedure etc.)

Answer : Yes.

So here we explian how :-

Databse snapshot is read only databse. It’s a static view database on which only read only operaton can be performed. Database snapshot works on data page level. Before a page of the source database is modified for the first time, the original page is copied from the source database to the snapshot. The snapshot stores the original page, preserving the data records as they existed when the snapshot was created. The same process is repeated for every page that is being modified for the first time.

So DB snapshot works page level & page is the smallest unit database engine can understand. Page contains the actual data, transactions and schema details. So here, I say snapshot works on page (not only data pages) and any change in page will move page to DB snapshot.

Break up of complete storage cycle :- Windows Server > SQL Instance > Database > Database Files > Extends > Pages

Source : https://msdn.microsoft.com/en-us/library/ms175158.aspx

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

You can find and follow MSSQLFUN :-

http://www.facebook.com/mssqlfun

http://mssqlfun.com/feed

https://twitter.com/Rgarg86

Other Linked Profiles :-

http://www.sqlservercentral.com/blogs/mssqlfun/

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

http://www.toadworld.com/members/rohit-garg/blogs/default.aspx

http://beyondrelational.com/members/RohitGarg/default.aspx