Tag Archives: SQL SERVER

How to Install SQL Server 2014 and a SQL Server 2014 Service Pack1 (SP1) at same time using slipstream

With the release SQL Server 2014, I have compiled the list of steps to create a slipstream drop. Once you have created this slipstream drop, you can install the original release of SQL Server 2014  and SP1 at the same time.The slipstream functionality performs a single installs that is quicker when compared to installing the original release and then applying the service pack. Additionally this slipstream drop fixes any Setup issues that prevent a successful installation or upgrade that has been addressed in SP1.To patch existing SQL Server 2014 features, download SP1 from the download center or obtain from Microsoft Update when available.

When you are installing a new instance of SQL Server, you want to perform as few steps as possible. SQL Server 2014 setup is much better about slipstreaming both service packs and cumulative updates.

Here are the steps:

1. Mount your original SQL Server 2014 source media.

2. Download the SQL Server 2014  SP1 packages with the file name [...]_zip.exe and Extract each of the SQL Server 2014 SP1 packages to C:\AllUpdatesFolder as follows. For example, when you first download Service Pack 1.the download folder will look like this:


3.Now when you run the below command line, when you get to the Product Updates screen in setup,

D:\setup.exe /Action=Install /UpdateSource=C:\AllUpdatesFolder

you should see that it has included both SP1 and CU1.


Note that you can keep all of your Service Packs and Cumulative Updates over time in the same folder – if you use the /UpdateSource argument, SQL Server Setup will be smart enough to choose the latest SP and its latest CU, regardless of what else might exist in that folder.

1 Comment

Posted by on March 4, 2015 in slipstreaming, SQL SERVER


Tags: ,

SQL script for rebuild/reindex indexes for Dynamics AX 2012

This script will evaluate each index in the database, and determine if it should be reindexed or rebuilt based on how fragmented they are.

I have very good experience in doing this, and it really increases performance the Dynamics AX 2012 databases.

-- Ensure a USE <databasename> statement has been executed first.
Use MicrosoftDynamicsAX
DECLARE @objectid int;
DECLARE @indexid int;
DECLARE @partitioncount bigint;
DECLARE @schemaname nvarchar(130); 
DECLARE @objectname nvarchar(130); 
DECLARE @indexname nvarchar(130); 
DECLARE @partitionnum bigint;
DECLARE @partitions bigint;
DECLARE @frag float;
DECLARE @command nvarchar(4000); 
-- Conditionally select tables and indexes from the sys.dm_db_index_physical_stats function 
-- and convert object and index IDs to names.
    object_id AS objectid,
    index_id AS indexid,
    partition_number AS partitionnum,
    avg_fragmentation_in_percent AS frag
INTO #work_to_do
FROM sys.dm_db_index_physical_stats (DB_ID(), NULL, NULL , NULL, 'LIMITED')
WHERE avg_fragmentation_in_percent > 10.0 AND index_id > 0;

-- Declare the cursor for the list of partitions to be processed.
DECLARE partitions CURSOR FOR SELECT * FROM #work_to_do;

-- Open the cursor.
OPEN partitions;

-- Loop through the partitions.
WHILE (1=1)
        FETCH NEXT
           FROM partitions
           INTO @objectid, @indexid, @partitionnum, @frag;
        IF @@FETCH_STATUS < 0 BREAK;
        SELECT @objectname = QUOTENAME(, @schemaname = QUOTENAME(
        FROM sys.objects AS o
        JOIN sys.schemas as s ON s.schema_id = o.schema_id
        WHERE o.object_id = @objectid;
        SELECT @indexname = QUOTENAME(name)
        FROM sys.indexes
        WHERE  object_id = @objectid AND index_id = @indexid;
        SELECT @partitioncount = count (*)
        FROM sys.partitions
        WHERE object_id = @objectid AND index_id = @indexid;

-- 30 is an arbitrary decision point at which to switch between reorganizing and rebuilding.
        IF @frag < 30.0
            SET @command = N'ALTER INDEX ' + @indexname + N' ON ' + @schemaname + N'.' + @objectname + N' REORGANIZE';
        IF @frag >= 30.0
            SET @command = N'ALTER INDEX ' + @indexname + N' ON ' + @schemaname + N'.' + @objectname + N' REBUILD';
        IF @partitioncount > 1
            SET @command = @command + N' PARTITION=' + CAST(@partitionnum AS nvarchar(10));
        EXEC (@command);
        PRINT N'Executed: ' + @command;

-- Close and deallocate the cursor.
CLOSE partitions;
DEALLOCATE partitions;

-- Drop the temporary table.
DROP TABLE #work_to_do;

Tags: , , , , ,

Ax error " A user session on the server could not be created. Try to start the client again. If the problem continues contact Ax Administrator



today we are having trouble with logging onto our Ax system.  The following errors occurs:

A user session on the server could not be created.  Try to start the client again.  If the problem continues contact Ax Administrator


this error is coming because of  AOS has no access to createusersessions stored procedure in the database.


finally got the conclusion that  the transaction log of the dbase is full, which will cause your login session to fail as well and throw the error

” A user session on the server could not be created. Try to start the client again. If the problem continues contact Ax Administrator”



the solution of this problem for


SQl Server 2008

EXEC sp_helpdb [DatabaseName]
Alter Database [Database Name] Set Recovery Full

EXEC sp_helpdb [DatabaseName]



SQL Server 2005

USE [DatabaseName];
SELECT file_id, name FROM

Backup log [DatabaseName] with Truncate_only;

DBCC Shrinkfile(DatabaseName_log)


SQL SERVER – Find Current Location of Data and Log File of All the Database

SELECT name, physical_name AS current_file_location

FROM sys.master_files


Posted by on October 9, 2012 in Microsoft Dynamics AX, SQL SERVER


Tags: ,