SQL Server 2014 Bug - with Clustered Index On Temp Table with Identity Column

Hi,
Here's a stored procedure.  (It could be shorter, but this will show the problem.)
          CREATE PROCEDURE dbo.SGTEST_TBD_20141030 AS
          IF OBJECT_ID('TempDB..#Temp') IS NOT NULL
             DROP TABLE #Temp
          CREATE TABLE #Temp
           Col1        INT NULL
          ,Col2        INT IDENTITY NOT NULL
          ,Col3        INT NOT NULL
          CREATE CLUSTERED INDEX ix_cl ON #Temp(Col2)
          SET IDENTITY_INSERT #Temp ON;
          RAISERROR('Preparing to INSERT INTO #Temp...',0,1) WITH NOWAIT;
          INSERT INTO #Temp (Col1, Col2, Col3)
          SELECT 1,2,3
          RAISERROR('Insert Success!!!',0,1) WITH NOWAIT;
          SET IDENTITY_INSERT #Temp OFF;
In SQL Server 2014, If I execute this (EXEC dbo.SGTEST_TBD_20141030)   It works.   If I execute it a second time - It fails hard with: 
        Msg 0, Level 11, State 0, Line 0
        A severe error occurred on the current command.  The results, if any, should be discarded.
        Msg 0, Level 20, State 0, Line 0
        A severe error occurred on the current command.  The results, if any, should be discarded.
In SQL Server 2012, I can execute it over and over, with no problem.  I've discovered two work-a-rounds:   
1) Add "WITH RECOMPILE" to the SP CREATE/ALTER statement, or 
2) Declare the cluster index in the TABLE CREATE statement, e.g. ",UNIQUE CLUSTERED (COL2)" 
This second option only works though, if the column is unique.    I've opted for the "WITH RECOMPILE" for now.  But, thought I should share.

Hi,
I did not get any error Message:
         CREATE TABLE #Temp
           Col1        INT NULL
          ,Col2        INT IDENTITY NOT NULL
          ,Col3        INT NOT NULL
          CREATE CLUSTERED INDEX ix_cl ON #Temp(Col2)
          SET IDENTITY_INSERT #Temp ON;
          RAISERROR('Preparing to INSERT INTO #Temp...',0,1) WITH NOWAIT;
          INSERT INTO #Temp (Col1, Col2, Col3)
          SELECT 1,2,3
          RAISERROR('Insert Success!!!',0,1) WITH NOWAIT;
          SET IDENTITY_INSERT #Temp OFF;
SELECT * FROM #Temp
OUTPUT:
Col1 Col2
Col3
1 2 3
1 2 3
1 2 3
Select @@version
--Microsoft SQL Server 2012 (SP1) - 11.0.3000.0 (X64) 
Oct 19 2012 13:38:57 
Copyright (c) Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
Thanks Shiven:) If Answer is Helpful, Please Vote

Similar Messages

  • MS SQL Server 2014: Error inserting into Temp table with index and identity field

    In this thread, I mentioned a problem with SQL Server 2014:
    SQL Server 2014: Bug with IDENTITY INSERT ON
    The question was answered, it is a bug. To keep you informed on this issue, I open this discussion.
    Problem:
    The code below works perfectly fine on MS SQL Server 2008 R2 and MS SQL Server 2012, but gives an error every second time the proc is executed on MS SQL Server 2014. If I do not define any index on the temp table, the problem disappears. Defining the index
    after the insert, does not help.
    SET NOCOUNT ON
    GO
    IF EXISTS (SELECT 1 FROM sys.procedures WHERE name = 'usp_Test') DROP PROC dbo.usp_Test;
    GO
    CREATE PROC dbo.usp_Test AS
    BEGIN
    SET NOCOUNT ON
    CREATE TABLE #Source(ID integer NOT NULL);
    INSERT INTO #Source VALUES (1), (2), (3);
    CREATE TABLE #Dest (ID integer IDENTITY(1,1) NOT NULL);
    CREATE INDEX #IDX_Dest ON #Dest (ID);
    PRINT 'Check if the insert might cause an identity crisis';
    SELECT 'Source' AS SourceTable, * FROM #Source;
    SELECT 'Destination' AS DestTable, * FROM #Dest;
    SET IDENTITY_INSERT #Dest ON;
    PRINT 'Do the insert';
    INSERT INTO #Dest (ID) SELECT ID FROM #Source;
    PRINT 'Insert ready';
    SET IDENTITY_INSERT #Dest OFF;
    SELECT * FROM #Dest;
    DROP TABLE #Source;
    DROP TABLE #Dest;
    END;
    GO
    PRINT 'First execution of the proc, everything OK';
    EXEC dbo.usp_Test;
    PRINT '';
    PRINT 'Second execution of the proc, the insert fails.';
    PRINT 'Removing the index #IDX_Dest causes the error to disappear.';
    EXEC dbo.usp_Test;
    GO
    DROP PROC dbo.usp_Test;
    GO

    There is some progress. Communication from a former Microsoft employee tells us this:
    Shivendra Vishal
    Engineer at Microsoft
    I am no longer with MS, and I do not have code access, however from the public symbols, I could make out following:
    sqlmin!SetidentI2I4+0x1f3:
    000007fe`f4d865d3 488b10 mov rdx,qword ptr [rax] ds:00000000`00000000=????????????????
    ExceptionAddress: 000007fef4d865d3 (sqlmin!SetidentI2I4+0x00000000000001f3)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 0000000000000000
    Parameter[1]: 0000000000000000
    Attempt to read from address 0000000000000000
    This is a read AV and from registers it is clear that we were trying to move the value of location pointed by qword of register rax which is not valid:
    rax=0000000000000000 rbx=0000000000000038 rcx=0000000000001030
    rdx=0000000000000006 rsi=00000001f55def98 rdi=00000000106fd070
    rip=000007fef4d865d3 rsp=00000000106fcf40 rbp=00000000106fcfe9
    r8=0000000000000000 r9=00000001f55def60 r10=00000001f55defa0
    r11=00000000106fcd20 r12=0000000000000000 r13=0000000000000002
    r14=00000001f49c3860 r15=00000001f58c0040
    iopl=0 nv up ei pl nz na po nc
    cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010206
    The stack is:
    # Child-SP RetAddr Call Site
    00 00000000`106fcf40 000007fe`f30c1437 sqlmin!SetidentI2I4+0x1f3
    01 00000000`106fd050 000007fe`f474e7ce sqlTsEs!CEsExec::GeneralEval4+0xe7
    02 00000000`106fd120 000007fe`f470e6ef sqlmin!CQScanUpdateNew::GetRow+0x43d
    03 00000000`106fd1d0 000007fe`f08ff517 sqlmin!CQueryScan::GetRow+0x81
    04 00000000`106fd200 000007fe`f091cebe sqllang!CXStmtQuery::ErsqExecuteQuery+0x36d
    05 00000000`106fd390 000007fe`f091ccb9 sqllang!CXStmtDML::XretDMLExecute+0x2ee
    06 00000000`106fd480 000007fe`f08fa058 sqllang!CXStmtDML::XretExecute+0xad
    07 00000000`106fd4b0 000007fe`f08fb66b sqllang!CMsqlExecContext::ExecuteStmts<1,1>+0x427
    08 00000000`106fd5f0 000007fe`f08fac2e sqllang!CMsqlExecContext::FExecute+0xa33
    09 00000000`106fd7e0 000007fe`f152cfaa sqllang!CSQLSource::Execute+0x86c
    0a 00000000`106fd9b0 000007fe`f152c9e8 sqllang!CStmtExecProc::XretLocalExec+0x25a
    0b 00000000`106fda30 000007fe`f152a1d8 sqllang!CStmtExecProc::XretExecExecute+0x4e8
    0c 00000000`106fe1e0 000007fe`f08fa058 sqllang!CXStmtExecProc::XretExecute+0x38
    0d 00000000`106fe220 000007fe`f08fb66b sqllang!CMsqlExecContext::ExecuteStmts<1,1>+0x427
    0e 00000000`106fe360 000007fe`f08fac2e sqllang!CMsqlExecContext::FExecute+0xa33
    0f 00000000`106fe550 000007fe`f0902267 sqllang!CSQLSource::Execute+0x86c
    10 00000000`106fe720 000007fe`f0909087 sqllang!process_request+0xa57
    11 00000000`106feee0 000007fe`f2bf49d0 sqllang!process_commands+0x4a3
    12 00000000`106ff200 000007fe`f2bf47b4 sqldk!SOS_Task::Param::Execute+0x21e
    13 00000000`106ff800 000007fe`f2bf45b6 sqldk!SOS_Scheduler::RunTask+0xa8
    14 00000000`106ff870 000007fe`f2c136ff sqldk!SOS_Scheduler::ProcessTasks+0x279
    15 00000000`106ff8f0 000007fe`f2c138f0 sqldk!SchedulerManager::WorkerEntryPoint+0x24c
    16 00000000`106ff990 000007fe`f2c13246 sqldk!SystemThread::RunWorker+0x8f
    17 00000000`106ff9c0 000007fe`f2c13558 sqldk!SystemThreadDispatcher::ProcessWorker+0x3ab
    18 00000000`106ffa70 00000000`775d59ed sqldk!SchedulerManager::ThreadEntryPoint+0x226
    19 00000000`106ffb10 00000000`7780c541 kernel32!BaseThreadInitThunk+0xd
    1a 00000000`106ffb40 00000000`00000000 ntdll!RtlUserThreadStart+0x21
    Unassembling the function:
    000007fe`f4d8658e 4c8b10 mov r10,qword ptr [rax]
    000007fe`f4d86591 4533e4 xor r12d,r12d
    000007fe`f4d86594 410fb7d5 movzx edx,r13w
    000007fe`f4d86598 4533c9 xor r9d,r9d
    000007fe`f4d8659b 4533c0 xor r8d,r8d
    000007fe`f4d8659e 488bc8 mov rcx,rax
    000007fe`f4d865a1 4489642420 mov dword ptr [rsp+20h],r12d
    000007fe`f4d865a6 41ff5230 call qword ptr [r10+30h]
    000007fe`f4d865aa 8b5597 mov edx,dword ptr [rbp-69h]
    000007fe`f4d865ad 4c8b10 mov r10,qword ptr [rax]
    000007fe`f4d865b0 4489642438 mov dword ptr [rsp+38h],r12d
    000007fe`f4d865b5 4489642430 mov dword ptr [rsp+30h],r12d
    000007fe`f4d865ba 458d442401 lea r8d,[r12+1]
    000007fe`f4d865bf 4533c9 xor r9d,r9d
    000007fe`f4d865c2 488bc8 mov rcx,rax
    000007fe`f4d865c5 c644242801 mov byte ptr [rsp+28h],1
    000007fe`f4d865ca 4488642420 mov byte ptr [rsp+20h],r12b
    000007fe`f4d865cf 41ff5250 call qword ptr [r10+50h]
    000007fe`f4d865d3 488b10 mov rdx,qword ptr [rax] <=================== AV happened over here
    000007fe`f4d865d6 488bc8 mov rcx,rax
    000007fe`f4d865d9 4c8bf0 mov r14,rax
    000007fe`f4d865dc ff5268 call qword ptr [rdx+68h]
    000007fe`f4d865df 488d55e7 lea rdx,[rbp-19h]
    000007fe`f4d865e3 4c8b00 mov r8,qword ptr [rax]
    000007fe`f4d865e6 488bc8 mov rcx,rax
    000007fe`f4d865e9 41ff5010 call qword ptr [r8+10h]
    000007fe`f4d865ed f6450a04 test byte ptr [rbp+0Ah],4
    I remember few issues with scan2ident function, I am not sure if they have fixed it however it appears that this is intoduced to SQL 2014 and we need help from MS to get this resolved as it needs code analysis.
    It is not getting simulated for other versions of SQL apart from SQL 2014.
    Also to add, interestingly, the value of rax is not visibly changed and it was successfully passed on to rcx, which has a valid value, so something should have changed the value of rax inside call to function using call qword ptr [r10+50h], and looking at this
    it appears that it might be a list of functions and we are going at particular offset [50h]. So, bottom line is that the call to function qword ptr [r10+50h], should be changing something in rax, and debugging/analyzing this code might give us some more idea.

  • SQL Server 2014 - Columnstore Incorrect Results

    Hello,
    we are running into a problem with SQL Server 2014 and the columnstore index. We have a partitioned table with about 300 Million records in it. With SQL Server 2012 this has been in use without problems.
    Since we upgraded to SQL Server 2014, the exact same queries on exactly the same data return incorrect results. We can only bypass the problem by either dropping the CS Index or adding a maxdop = 1 query hint.
    I thought this was an old bug in SQL Server 2012? We have not installed the CU Pack 4 for SQL Server 2014, yet but will it solve the problem (assuming others have faced the same problem)
    We are running: Microsoft SQL Server 2014 Enterprise Edition - 12.0.2000.8 (X64) on a 2x6Core Machine
    Thanks in advance!

    SQL Server 2012 only featured non-clustered columnstore indexes which were separate structures.  Have you changed to a clustered columnstore (cs) index in SQL Server 2014?  (ie dropped your non-clustered cs, created a cs)
    There are a number of fixes that reference columnstore indexes in the current CUs (
    CU1,
    CU2, CU3,
    CU4 ), but none which sound exactly like your problem. 
    This sounds similar and is fixed in CU1.  You should review the CU documents yourself to see if any of them mention a similar problem and then consider applying the CU.  You might also try applying them to a test environment, or a temporary Azure
    VM for example to see if one of them solves your problem.
    If you can create a reliable "repro" of the problem, consider raising a
    connect item which is a Microsoft bug report.

  • How to install SQL Server 2014 Documentation

    I installed the SQL Server 2014 Management Studio (64bit of course), that came with an empty product help. So I went to
    http://www.microsoft.com/en-us/download/details.aspx?id=42557 and downloaded the file from there. Upon opening the file I got an error that the file is corrupt (after several downloads
    from different machines). With 7zip I could open the file without any problem. So I copied it to a folder. Now when I want to add the folder to the helper, get error messages:
    - You do not have permissions to modifiy content under that location specified for help content store 
       (C:\Program Data\Microsoft\HelpLibrary2\Catalog\SQL2014)
    - Local help store cannot be in folders that should not be accessed by all user accounts on this computer.
    Where should I copy this folder that this thing finally works. We live in 2014 and I waist already 30 minutes to get the documentation up and running that should come with the product in the first place.
    Please advise (and maybe give me some insight what the people responsible for the SQL 2014 help had in mind with this concept ?)

    Hi ErnestoMawan,
    According to your description, you have downloaded the documentation file and you want to add that documentation for SQL Server, right?
    So please follow steps below to add the documentation for SQL Server:
    Double-click the self-extracting EXE to extract its contents.
    Specify the location for the extracted contents. For example, a network share that is accessible to your destination computer or server.
    Run Manage Help Settings. In Windows 7, launch Help Library Manager from Start, All Programs, SQL Server 2014, Help & Community and then clicking Manage Help Settings. Or, launch SQL Server Management Studio, click the Help menu, and select Manage Help
    Settings.
    In Help Library Manager, click Choose online or local help.
    Select I want to use local help and then click OK.
    Click Install content from disk and browse to the directory where you unpacked the downloaded EXE.
    Select the HelpContentSetup.msha file and then click Open.
    Click Next.
    Click Add next to the documentation you want to install.
    Click Update.
    Once Help Library Manager has completed the installation process, click Finish and then click Exit to close Help Library Manager.
    For more information about Add or Remove Product Documentation for SQL Server, please refer to the following article:
    http://msdn.microsoft.com/en-us/library/ms166022.aspx
    If you have any question, please feel free to let me know.
    Regards,
    Jerry Li

  • SQL Server 2014 - ColumnStore index Clustered with Merge Join

    Hi All,
    I would like to know in SQL Server 2014, the new feature "Clustered Columnstore". I had inserted 9 millions of records in to a clustered columnstore table.
    Then i do a merge join query to insert and update to another table. The Merge join query is as below :
    MERGE [dbo].[Temp_FactSales] AS TARGET
    USING [dbo].[FactSales_9m] AS SOURCE
    ON
    TARGET.SALESID = SOURCE.SALESID
    WHEN NOT MATCHED BY TARGET
    THEN INSERT
    [listid],
    [sellerid],
    [buyerid],
    [eventid],
    [dateid],
    [qtysold],
    [pricepaid],
    [commission],
    [saletime]
    VALUES
    SOURCE.[listid],
    SOURCE.[sellerid],
    SOURCE.[buyerid],
    SOURCE.[eventid],
    SOURCE.[dateid],
    SOURCE.[qtysold],
    SOURCE.[pricepaid],
    SOURCE.[commission],
    SOURCE.[saletime]
    WHEN MATCHED THEN
    UPDATE
    SET
        TARGET.[listid] = SOURCE.[listid],
    TARGET.[sellerid] = SOURCE.[sellerid],
    TARGET.[buyerid] = SOURCE.[buyerid],
    TARGET.[eventid] = SOURCE.[eventid],
    TARGET.[dateid] = SOURCE.[dateid],
    TARGET.[qtysold] = SOURCE.[qtysold],
    TARGET.[pricepaid] = SOURCE.[pricepaid],
    TARGET.[commission] = SOURCE.[commission],
    TARGET.[saletime] = SOURCE.[saletime]
    The total execute time is  about 10 mins. However if i removed the Columnstore index in the table which using normal primary key. Then the execution time is less than 1 mins.  
    My question is when using "merge join", is this the behavior for columnstore index ? As from what i read, Columnstore index is great performance in read the data but not doing "Insert, update and Delete"?
    Hope anyone can help.
    Thanks a lot.

    Hi TTL1964,
    How's everything going?
    If there is any progress from your side, feel free to share it in the forum. 
    Thanks.
    Tracy Cai
    TechNet Community Support

  • Can SQL server 2014 instance be introduced into SQL server 2012 clustering

    Hello, everyone,
    We have SQL server clustering set up in place (it is actually windows clustering), I am wondering if it is possible to introduce SQL server 2014 instance
    into this clustering. Please share us your thoughts and experiences.
    Thanks

    if you are talking about SQL clustering -(FAILOVER CLUSTERED  INSTANCES) , yes, you can do that.
    you have windows cluster with nodea,nodeb....and you can install two different instances of failover clustered sql - sql 2012 and sql 2014.
    Hope it Helps!!

  • Sharepoint Foundation 2010 compatibility with SQL Server 2014

    Due to a requirement to use Sharepoint without Active Directory access.  I am trying to find explicit confirmation whether Sharepoint Foundation 2010 is compatible with SQL Server 2014.  I have seen that Sharepoint Server 2010 and 2013 are compatible
    with SQL Server 2014 as of CU 1 (released in April).  But there is no mention of Sharepoint Foundation.
    This chart is great except it doesn't mention whether the Foundation versions are supported.
    http://msdn.microsoft.com/en-us/library/gg492257.aspx
    Thanks.

    Note that that is for the Reporting Services component, but not necessarily for the SQL Database Engine component (which comes from the SharePoint Product Group, rather than the SQL Product Group). I haven't seen any confirmation that SharePoint 2010 is
    supported at all with SQL 2014 as a Database Engine.
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Sql server 2005 reports with sql server 2014

    Can i upload SSRS 2005 reports as it is on SSRS 2014 and use it without doing anything extra or without changing anything ??
    I can use SSRS 2005 reports as it is with SSRS 2012. But for SSRS 2014 not sure.
    h2007

    You can upgrade the the RDL schema will be upgraded.
    Report definition (.rdl) files are automatically upgraded in the following ways:
    When you open a report in Report Designer in SQL Server Data Tools (SSDT), the report definition is upgraded to the currently supported RDL schema. When you specify a SQL Server 2008 or SQL Server 2008 R2 report server in the project properties, the report
    definition is saved in a schema that is compatible with the target server.
    When you upgrade a Reporting Services installation to a SQL Server 2014 Reporting Services (SSRS) installation, existing reports and snapshots that have been published to a report server are compiled and automatically upgraded to the new schema the first
    time they are processed. If a report cannot be automatically upgraded, the report is processed using the backward-compatibility mode. The report definition remains in the original schema.
    Reports are not upgraded when you upload a report definition file directly to the report server or SharePoint site. Upgrading a report definition in SQL Server Data Tools is the only way to upgrade the .rdl file.
    After a report is upgraded locally or on the report server, you might notice additional errors, warnings, and messages. This is the result of changes to the internal report object model and processing components, which cause messages to appear when underlying
    problems in the report are detected. For more information, see Reporting Services Backward Compatibility.
    For more information about new features for SQL Server 2014 Reporting Services (SSRS), see
    What's New (Reporting Services).
    Check the below Microsoft link for more information
    http://msdn.microsoft.com/en-us/library/ms143674.aspx
    Mudassar

  • SQL Server 2005 replaced with SQL Server 2014 trying to connect front end Access as guest (read only ODBC)

    We have replaced a SQL Server 2005 with a SQL Server 2014 (new physical server.)  Have the new server set up to use SQL Server login OR Windows user login. Had old server connecting (for a particular DB) to front end Access (2010 or 2013) as guest for
    anyone logged into the Windows NT Network with a read only ODBC connection. Have the DB in the new server set to include guest as db_datareader (with only SELECT permission for the securables of each table and view being linked) but when any Windows user not
    specifically listed as a SQL DB user tries to use the front end they get an error of:
    Microsoft SQL Server Login
    Connection failed:
    SQL State: '28000'
    SQL Server Error: 18456
    [Microsoft][OCBC SQL Server Driver][SQL Server] Login failed for user {domain\user}.
    After closing that pop-up window a server login window appears. Of course, since the guest user is not specifically listed as a user in the DB that fails also. It seems like there should be a very simple solution to this, but I can't seem to find it. I want
    to allow anyone logged in on the Windows system (locally) to be able to open the MS Access file (on their work station machine) and run their own (read only; select) queries on the SQL Server database. Any suggestions?
    Thanks a billion in advance ----

    Thanks for the response Olaf. I have now spent weeks researching this. I realize that using the guest account in most situations is not advised. As mentioned, I have restricted the guest account to allow the db_datareader role only, and have explicitly denied
    all other roles, as well as allowing select only, and still have no access for the guest account.
    The suggested fix in the second link you provided, of using Windows groups is not plausible for my situation either. We are a scientific field research institution, with a few long term users and lots of users that may have Windows accounts for a few months,
    and then they are gone. It would be a nightmare for the network tech to try to keep a group account up to date, and we need to give access (read only, of course) to anyone logged into the system. Realize that the ONLY access of any kind to this database is
    thru MS Access ACCDB, using a (by default) read only OCDB connection.
    This type of access is used particularly because researchers need to be able to set up their own queries, and the MS Access query interface is particularly convenient for people who are not themselves SQL experts, yet are trying to get some very advanced
    levels of output. Putting the database online is not practical because then we are back to the need for a comprehensive query interface, and just picking up general subsets of the data online (from a basic web page search feature) would be out of the question,
    since the result set would involve hundreds of thousands if not millions of records.
    So - that said - what exactly would you suggest, assuming we don't have the funds to buy a whole new system, and have spent plenty of money with Microsoft's Enterprise level MS Office so that all work stations have MS Access, and Microsoft's SQL Server,
    as well as running our network on Microsoft's network software.

  • Unexpected Termination SSIS package - Issue with SSIS packages after upgrading to SQL Server 2014

    Hello everyone.
    We performed an upgrade of SQL Server 2012 installation to SQL Server 2014 (with last CU5 update). We found that all SSIS packages (even the simplest with just Execute SQL tasks) fail with Unexpected termination message. The issue reproduces with both new
    packages (that are created from scratch with SSDT 2014) and old packages (migrated from SQL 2012).
    Any ideas, please? We googled and found that it is a known issue that should have fixed with CU4. But we use CU5 and the issue is still here.
    MCP

    Hi. Yes...
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="SQLISServer" /> 
      <EventID Qualifiers="0">1</EventID> 
      <Level>2</Level> 
      <Task>0</Task> 
      <Keywords>0x80000000000000</Keywords> 
      <TimeCreated SystemTime="2015-02-12T07:41:56.000000000Z" /> 
      <EventRecordID>469950</EventRecordID> 
      <Channel>Application</Channel> 
      <Computer>abtru1a11.oneabbott.com</Computer> 
      <Security /> 
      </System>
    - <EventData>
      <Data>The SSIS Execution Process could not write to the IS catalog: ABTRU1A11\DEV:SSISDB Error details: Cannot find the symmetric key 'MS_Enckey_Proj_Param_5', because it does not exist or you do not have permission.; at System.Data.SqlClient.SqlConnection.OnError(SqlException
    exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior
    runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData()
    at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream,
    Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion,
    Int32 timeout, Task& task, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
    behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader() at Microsoft.SqlServer.IntegrationServices.Server.Shared.ExecutionParameterLoader.GetExecutionParameter() at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ProjectOperator.StartPackage()
    at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ProjectOperator.PerformOperation()</Data> 
      </EventData>
      </Event>
    MCP

  • Why can't I log into my "Local" sql server (sql server 2014) with my Sql Server Authentication UID ?

    I just got a new work station (win7 Pro) which has the following sql server
    SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')
    returns
    12.0.2254.0     RTM     Developer Edition (64-bit)
    Select @@version
    returns
    Microsoft SQL Server 2014 - 12.0.2254.0 (X64)
     Jul 25 2014 18:52:51
     Copyright (c) Microsoft Corporation
     Developer Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
    I added/created a new (random) user account to this server [joe123] and made him sa and mapped him to everything, the password never expires, ...
    when I try to login to this local server the login fails, but I can log into this server with my windows integrated account (also sa).  What do I need to do so that the joe123 account can login to the server
    Rich P

    Check if both "SQL Server and Windows Authentication mode" is set (not just Windows Authentication mode). Server-->right click and select properties -->  Security
    Satish Kartan http://www.sqlfood.com/

  • Trouble Turneing on FileStream/Ad Hoc Query with new SQL Server 2014 64-BIt Version

    SQL Server Help,
    I have recently installed SQL SERVER 2014 on my Window 7 SP1 Acer laptop.
    I am trying to do a simple upload of an Excel file into SQL Server using the OPENROWSET command:
    Which I found requires some configuration change I attempted below.
    When I execute this:
    execute sp_configure 'show advanced options', 1;
    RECONFIGURE;
    execute sp_configure 'Ad Hoc Distributed Queries', 1;
    RECONFIGURE;
    GO
    I get this message
    Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
    Msg 5593, Level 16, State 1, Line 2
    FILESTREAM feature is not supported on WoW64. The feature is disabled.
    Msg 15123, Level 16, State 1, Procedure sp_configure, Line 62
    The configuration option 'Ad Hoc Distributed Queries' does not exist, or it may be an advanced option.
    Msg 5593, Level 16, State 1, Line 4
    FILESTREAM feature is not supported on WoW64. The feature is disabled.
    When I go to the SQL Server Services and Properties on the Server and try to change the FileStream options to be on..I get the error:
    "There was an unknown error applying the FILESTREAM settings.  Check the parameters are valid (0x80070002)."
    Perhaps my issue is with the Windows Share Name:  .  I have put in a local driver C:\A_Excel....also the computer name, my user ID.   Is there a special format or way to define a Share Name that I am unaware of?
    Is there a way to fix this?  Can I not load Excel files with a 64-Bit system?  Or what is the easiest way that I can do this with my configuration?
    Thanks for any help.

    FILESTREAM feature is not supported on WoW64. The feature is disabled.
    By the error message it seems you have a 64 bit OS, but have installed a 32 bit SQL Server and here in WoW64 mode filestream seems to be not supported. Install a 64 bit SQL Server instead.
    Olaf Helper
    [ Blog] [ Xing] [ MVP]

  • Upgrade DTSX packages from VS 2010 with SQL Server 2008 to VS 2013 and SQL Server 2014

    Hello everyone,
    I’m very new to SSIS world. I’ve been assigned a task to upgrade the existing packages running in VS 2010 with SQL Server 2008 to VS 2013 and SQL Server 2014. And then submit the migration report to my client.
    On very quick search at Google, I've found the following link. It seems like I just need to open the existing SSIS project in VS 2013 and follow the wizard.
    https://msdn.microsoft.com/en-us/library/cc280547.aspx
    Can anybody please advise, are there any other things need to be taken care while doing this up gradation process?
    Please share your experience.
    Any help would be much appreciated.
    Thanks, <b>Ankit Shah</b> <hr> Inkey Solutions, India. <hr> Microsoft Certified Business Management Solutions Professionals <hr> http://ankit.inkeysolutions.com

    Hello Arthur,
    Thank you for the response.
    I just got an access of the packages. They are of VS 2008 and not 2010.
    Do you know how to upgrade VS 2008 packaged to VS 2013?
    When I tried to open the solution file in VS 2013, it says "incompatible".
    Any help would be much appreciated.
    Thanks,
    Ankit
    Thanks, <b>Ankit Shah</b> <hr> Inkey Solutions, India. <hr> Microsoft Certified Business Management Solutions Professionals <hr> http://ankit.inkeysolutions.com

  • Can't connect to remote SQL Server 2014 Standard with VS 2012

    Hi all,
    I am trying to create a development environment using SQL Server 2014 (not Express).  The SQL server instance is on a Windows 8.1 Pro machine in a non-domain environment.  I have Visual Studio 2012 installed on the same machine which can connect
    to the SQL server instance without problems.  I have another machine with VS 2012 that cannot connect.  SQL server is configured for mixed authentication.  The SSDT on the remote machine can see the SQL server networked instance, but will not
    connect with SQL authentication. 
    I have rounded up all the usual suspects;
    - The SQL server service is running
    - Remote connections are enabled on SQL server and the relevant firewall ports are open.
    - TCP/IP and named pipes are enabled
    - Remote connections are enabled in Management Studio
    - SQL Server Browser service in enabled and running
    What am I missing?  I have been out of developer mode for a few years and all of the tools have changed, but I seem to be missing something obvious.
    Many thanks in advance,
    Tim
    Tim in Dublin

    Hello,
    Have you configured the Windows Firewall on the Visual Studio computer too? Is there any other security software on those
    2 computers?
    Can you ping between both computers by computer name? If not, try connecting using the IP address. For example:
    10.0.0.10,1433
    1433 is the default SQL Server port number.
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • DB-Library BCP issue with SQL Server 2014

    Hello,
    My application uses DB-Library (ntwdblib.dll) to communicate with SQL Server 2014. We are having issues calling bcp related functions like bcp_init which always returns FAIL status. Our application was working fine with SQL Server 2012 and all other previous
    SQL releases. But we are getting below error in SQL 2014,
    msg 4801, state 1, severity 16 : Insert bulk is not supported over this access protocol.
    Can anyone please help ?
    Thanks,
    Himanshu

    Hi Himanshu_kus,
    Is this still an issue, or can we close the thread?
    [Personal Site] [Blog] [Facebook]

Maybe you are looking for