Hi friends,

Anyway to name a primary key at the time the same is being declared? For example, using a query like:

ALTER TABLE LOANDETAILS.MTH_201408
ADD PRIMARY KEY (LG_CUST_ID, LG_ACC_ID, LG_SRC_SYS)

for a table, can an approach be made to name the PK right at this step, instead of finding the one named by the SQL Server unclearly, something as 'PK__MTH_20140__110E2E2DC4061AA3' and using sp_rename to name it much more clearly?

Thanx in advance, Best Regards, Faraz A Qureshi

Hi ,

which on is the best , all for the same query  but with different indexes structure

Microsoft SQL Server 2014 - 12.0.2000.8 (X64)
 Feb 20 2014 20:04:26
 Copyright (c) Microsoft Corporation
 Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)

Three SQL instances on this server.  Update statistics for all databases in all instances is run nightly and weekly index rebuilds.  The problem occurs in just one instance.  Instance contains Team Foundation Server (TFS) database 'Tfs_DefaultCollection'.  Problem started happening after the most recent weekly index rebuild. 

The problem that surfaced this past weekend appears to have occurred because of the following index rebuild (in Tfs_DefaultCollection database):   ALTER INDEX [PK_tbl_LocalVersion] ON [dbo].[tbl_LocalVersion] REBUILD PARTITION = ALL WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = ON, IGNORE_DUP_KEY = OFF, ONLINE = ON (WAIT_AT_LOW_PRIORITY (MAX_DURATION = 0 MINUTES, ABORT_AFTER_WAIT = NONE)), ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, DATA_COMPRESSION = PAGE)

The index re-build when run as stand-alone simply results in "Command(s) completed successfully". 

DBCC CHECKTABLE reports no problems on the table after index rebuild. DBCC CHECK DB also reports no problems.

However, 'UPDATE STATISTICS [tbl_LocalVersion]' reports 'Msg 0, Level 11, State 0, Line 16. A severe error occurred on the current command.  The results, if any, should be discarded.'

I have restored old backups to differently named DBs.  The older backups do not error when updating stats for this table.  However I can recreate the problem by doing the above index rebuild.  Following the rebuild,  the update stats fails with above error.

Using one of the old backups where update stats worked, I tried drop/create the index (even with 'drop existing').  The result of this gives me the following warning which I hope is not part of the problem because we didn't change the database design, it is TFS:  'Warning! The maximum key length is 900 bytes. The index 'PK_tbl_LocalVersion' has maximum length of 1609 bytes. For some combination of large values, the insert/update operation will fail.' 

I can stop rebuilding the indices weekly, but I would like to get it back to a state wherein the update statistics runs successfully.

I will post the dump file next if that will help solve this problem.

Thank you in advance for any help you can provide.

HI All,

I am facing this issue in my SQL server cluster.

2010-10-19 02:56:59.380 Logon Login failed for user <Server name>\User1'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: ]

I have two node cluster in active passive mode.

recently someone has truncated the transaction logs. After that, i am facing this issue. Also, noticed that before this error started i got one more error;

The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x2098, state: 15.

I have followed lot of articles, but no luck

Please help. 

Any help would be much appreciated. 

Regards,

Jina.

Hi ~ I know how to tune up the max no of Error Log for sql server

but I don't know how to tune the max no of sql agent log.

Any way ?

I wrote a WCF Data Access services using SQL Authentication to access SQL Server.

Here is my connection string

<add name="ClassroomOnlineEntitiesSa" connectionString="metadata=res://*/Model1.csdl|res://*/Model1.ssdl|res://*/Model1.msl;provider=System.Data.SqlClient;provider connection string=&quot;data source=SPDEVSERVER;initial catalog=ClassroomOnline;persist security info=True;user id=webservices;password=Password1;MultipleActiveResultSets=True;App=EntityFramework&quot;" providerName="System.Data.EntityClient" />

When I run on IIS 8.5 I het this error

m:error><m:code /><m:message xml:lang="en-US">An error occurred while processing this request.</m:message><m:innererror><m:message>The underlying provider failed on Open.</m:message><m:type>System.Data.EntityException</m:type><m:stacktrace>
    at System.Data.EntityClient.EntityConnection.OpenStoreConnectionIf(Boolean openCondition, DbConnection storeConnectionToOpen, DbConnection originalConnection, String exceptionCode, String attemptedOperation, Boolean& closeStoreConnectionOnFailure)

    at System.Data.EntityClient.EntityConnection.Open()

    at System.Data.Objects.ObjectContext.EnsureConnection()

    at System.Data.Objects.ObjectQuery`1.GetResults(Nullable`1 forMergeOption)

    at System.Data.Objects.ObjectQuery`1.System.Collections.Generic.IEnumerable
    <T>
      .GetEnumerator()

      at System.Data.Objects.ObjectQuery`1.GetEnumeratorInternal()

      at System.Data.Services.WebUtil.GetRequestEnumerator(IEnumerable enumerable)

      at System.Data.Services.QueryResultInfo.MoveNext()

      at System.Data.Services.DataService`1.SerializeResponseBody(RequestDescription description, IDataService dataService, IODataResponseMessage responseMessage)

      at System.Data.Services.DataService`1.HandleRequest()
  </m:stacktrace><m:internalexception><m:message>A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)</m:message><m:type>System.Data.SqlClient.SqlException</m:type><m:stacktrace>
      at System.Data.SqlClient.SqlInternalConnection.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.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, Boolean withFailover)

      at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)

      at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout)

      at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)

      at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData)

      at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)

      at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions)

      at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)

      at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)

      at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)

      at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)

      at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)

      at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)

      at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)

      at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)

      at System.Data.SqlClient.SqlConnection.Open()

      at System.Data.EntityClient.EntityConnection.OpenStoreConnectionIf(Boolean openCondition, DbConnection storeConnectionToOpen, DbConnection originalConnection, String exceptionCode, String attemptedOperation, Boolean& closeStoreConnectionOnFailure)</m:stacktrace><m:internalexception><m:message>The network path was not found</m:message><m:type>System.ComponentModel.Win32Exception</m:type><m:stacktrace /></m:internalexception></m:internalexception></m:innererror></m:error>

Dear Experts-

I had a very tough weekend with my Production sql server, the master database was corrupted and production was stopped, so I have to rebuild the master from cmd and then restores the back of the master and msdb database and boom it was back online. then after a day again the production was stopped and I received a phone call from a very pissed customer, you know that if you are a DBA, so I went to the event viewer and I see this errors- Please advise, thank you.

1. Script level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql' encountered error 5833, state 1, severity 16. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.

2. Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.

My database is 250 GB and before a patch deployment in application I have executed full backup and it is showing 5 hours in completion while generally it takes 2 hours.therfore I have cancelled the full backup after 30 percent.

I have weelkly full,daily diff and per hour log backup strategy.

I want to make sure after cancel full backup are my log backups can do the restoration?

Thanks

Hi All,

One of my production server every week reindex job is running. In that job there is 10 steps. in those steps one step failed .

)  DBCC DBREINDEX ("dbo.test", charge_pk,90) WITH NO_INFOMSGS [SQLSTATE 01000] (Message 0)  Incorrect syntax near 'No'. [SQLSTATE 42000] (Error 102)  Incorrect syntax near the keyword 'with'. If this statement is a common table expression, an xmlnamespaces clause or a change tracking context clause, the previous statement must be terminated with a semicolon.[SQLSTATE 42000] (Error 319)  DBCC DBREINDEX ("dbo.", Ship,90) WITH NO_INFOMSGS [SQLSTATE 01000] (Error 0)  DBCC DBREINDEX ("dbo.", Inv,90) WITH NO_INFOMSGS [SQLSTATE 01000] (Message 0)  DBCC DBREINDEX ("dbo.", Cust,90) WITH NO_INFOMSGS [SQLSTATE 01000] (Message 0).

The step failed.

Please suggest  to resolve this issue.

We have a 64-bit Enterprise server w/Svc pack 1.  Running SS 2008 64 bit (of course).  2 four-way CPU's.  56 GB of RAM. 

In the last month, it has froze 3 times at 11 am;  1PM & 2AM.  Each time the Log backup was seen to have entered a never-stop condition.  Normally the log backups run in 6 seconds.  Analysing wait states shows that PREEMPTIVE_OS_GETPROCADDRESS is the by-far highest waitstate.  I have been unable to find any documentation on PREEMPTIVE_OS_GETPROCADDRESS.

When not 'frozen' this sql machine has no issues.  There is one other OS issue i should mention:  three minutes before the last event (as identified by the log backup going to 6 hour duration) the os reported "VOLSNAP"...  "The description for Event ID '-1073348583' in Source 'VolSnap'cannot be found".  Could there be a connection there?

Two SQL servers, server A & B, Hardware information as below:
Server A: Clustered. Two physical processors (4 cores). RAM 64GB, SQL Server max memory: 58GB.
Server B: Standalone. One physical processor (4 cores). RAM 16GB, SQL Server max memory: 10GB.

The two databases on A & B are identical (using backup & restore method), same query execution CPU time are different, it is slower on the cluster server with more CPU & Mmeory. I tried many times and all same result, I also tried run DBCC DROPCLEANBUFFERS& DBCC FREEPROCCACHE before running the query.

When I run the query, on Server A (Slow one), CPU usage is at 20% ~30%. RAM usage is 14%. It is new set up environment so just me using it now.
When I run the query on Server B (Fast one), CPU usage is 40%, RAM usage is 85%.
Both two servers have SAN connected storage.

Query execution plan is exactly same on two serers.

Could someone give me some advise how to troubleshoot this problem? Any suggestion is appreciated a lot! Thanks a lot!

FYI, Below are the statistics when running same query in same DB on two servers:

Server A CPU & IO Statistics:
SQL Server parse and compile time: 
   CPU time = 109 ms, elapsed time = 297 ms.
(1005301 row(s) affected)
Table 'PODT'. Scan count 1, logical reads 55184, physical reads 3, read-ahead reads 55180, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.
Table 'MRICLDEFENT'. Scan count 0, logical reads 71898, physical reads 3, read-ahead reads 0, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.
Table 'POHD'. Scan count 1, logical reads 103154, physical reads 3, read-ahead reads 103150, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.

 SQL Server Execution Times:
CPU time = 7769 ms,  elapsed time = 16693 ms.

Server B CPU & IO Statistics:
SQL Server parse and compile time: 
   CPU time = 32 ms, elapsed time = 39 ms.
(1005301 row(s) affected)
Table 'PODT'. Scan count 1, logical reads 55184, physical reads 3, read-ahead reads 55180, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.
Table 'MRICLDEFENT'. Scan count 0, logical reads 71898, physical reads 3, read-ahead reads 0, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.
Table 'POHD'. Scan count 1, logical reads 103154, physical reads 3, read-ahead reads 103150, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.

 SQL Server Execution Times:
CPU time = 3931 ms,  elapsed time = 14387 ms.                             

Hi,

While analyzing a serverside trace, I sometimes see long runningLock:Aquires and/or Lock:Cancels, waiting for a resource that I could not identify. The value of ObjectID2 is 72057594529120256, but I could not find this.
The Statement causing this is running several times an hour without problems but sometimes it gets the locks.

I would like to know which resource is causing the problem - what does ObjectID2 contain?

The Resultset of
select*from sys.allocation_unitswhere allocation_unit_id=72057594529120256
is empty.

Kind Regards
Oliver.

I have a new mystery to solve.

Over the weekend i had to cancel the reindexing jobs on our BFSQL because what normally took less then 2 hours to do in the last 6 months was suddenly taking 8+ hours before i had to stop it.

I would like to know where i should start looking for clues.

It got stuck on the second biggest table in the DB

Fragmentation   TotalPages          TotalRows
100.00   115160  17610027

We are now entering peak season though that should not have effected the system this much.

This could be related to a clean up from a week earlier, though i don't see how, on our largest table which has no big relation to the table in question. Does freeing up space in one table really effect another tables reindexing?

Where else should i look?

All MSDN Friends,

I would like to implement the best practice for moving database objects from DEV server to QA/PROD in proper order for release with minimum manual intervention. My developer can save their db scripts and place in a central folder, if it helps.

Please let me know best practice for the release objects.

Thanks in advance.

Hi All,

We are using Sql Server 2005 Express , 

we got the below exception of Sql Server Assertion

2014-11-17 00:26:12.59 spid51      Error: 17066, Severity: 16, State: 1.
2014-11-17 00:26:12.59 spid51      SQL Server Assertion: File: <"logmgr.cpp">, line=5512 Failed Assertion = '!(minLSN.m_fSeqNo < lfcb->lfcb_fSeqNo)'. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
2014-11-17 00:26:12.61 spid51      Error: 3624, Severity: 20, State: 1.
2014-11-17 00:26:12.61 spid51      A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support. 
2014-11-17 00:27:34.81 Server      Using 'dbghelp.dll' version '4.0.5'
2014-11-17 00:27:34.81 Server      ***Unable to get thread context - no pss
2014-11-17 00:27:34.81 Server      * *******************************************************************************
2014-11-17 00:27:34.81 Server      *
2014-11-17 00:27:34.81 Server      * BEGIN STACK DUMP:
2014-11-17 00:27:34.81 Server      *   11/17/14 00:27:34 spid 0
2014-11-17 00:27:34.81 Server      *
2014-11-17 00:27:34.81 Server      * Non-yielding Scheduler
2014-11-17 00:27:34.81 Server      *
2014-11-17 00:27:34.81 Server      * *******************************************************************************
2014-11-17 00:27:34.81 Server      Stack Signature for the dump is 0x000003E6
2014-11-17 00:27:35.75 Server      External dump process return code 0x20000001.
External dump process returned no errors.

2014-11-17 00:27:35.75 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 99%. Interval: 75000 ms.
2014-11-17 00:28:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 98%. Interval: 135953 ms.
2014-11-17 00:29:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 98%. Interval: 195953 ms.
2014-11-17 00:30:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 98%. Interval: 255953 ms.
2014-11-17 00:31:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 98%. Interval: 315953 ms.
2014-11-17 00:32:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 98%. Interval: 375953 ms.
2014-11-17 00:33:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 98%. Interval: 435953 ms.
2014-11-17 00:34:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 98%. Interval: 495953 ms.
2014-11-17 00:35:05.77 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2014-11-17 00:35:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 98%. Interval: 555953 ms.
2014-11-17 00:36:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 97%. Interval: 615953 ms.
2014-11-17 00:37:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 98%. Interval: 675953 ms.

Hi Team,

i am installed  sql server 2012 two months back, to day i check the sql server error log it showing below error message.

Note : I my SQL server there is no SSIDB.

error log message:

2014-12-02 06:05:49.830 spid54     Using 'xpsqlbot.dll' version '2011.110.2100' to execute extended stored procedure 'xp_qv'. This is a

2014-12-02 06:05:49.830 spid54     Attempting to load library 'xpsqlbot.dll' into memory. This is an informational message only. No use

2014-12-02 06:05:48.770 spid4s     Recovery is complete. This is an informational message only. No user action is required.           

2014-12-02 06:05:48.770 spid4s     SQL Server is now ready for client connections. This is an informational message; no user action is

2014-12-02 06:05:48.760 spid4s     ------------------------------------------------------                                             

2014-12-02 06:05:48.760 spid4s     Execution of SSIS_HOTFIX_INSTALL.SQL completed                                                     

2014-12-02 06:05:48.760 spid4s     ------------------------------------------------------                                             

2014-12-02 06:05:48.760 spid4s     Database SSISDB was not patched.                                                                   

2014-12-02 06:05:48.760 spid4s     Database SSISDB does not exist in current SQL Server instance                                       

2014-12-02 06:05:48.760 spid4s     ------------------------------------------------------                                             

2014-12-02 06:05:48.760 spid4s     Starting execution of SSIS_HOTFIX_INSTALL.SQL                                                       

2014-12-02 06:05:48.760 spid4s     ------------------------------------------------------                                             

2014-12-02 06:05:48.740 spid4s     Database 'master' is upgrading script 'SSIS_hotfix_install.sql' from level 184552376 to level 184552

2014-12-02 06:05:48.660 spid4s     ------------------------------------------------------                                             

2014-12-02 06:05:48.660 spid4s     Execution of SSIS_DISCOVERY.SQL completed                                                          

2014-12-02 06:05:48.660 spid4s     ------------------------------------------------------                                             

2014-12-02 06:05:48.660 spid4s     Database SSISDB could not be upgraded successfully.                                                

2014-12-02 06:05:48.660 spid4s     User 'sa' is changing database script level entry 17 to a value of 500.                            

2014-12-02 06:05:48.660 spid4s     Database SSISDB does not exist in current SQL Server instance                                      

2014-12-02 06:05:48.630 spid4s     ------------------------------------------------------                                             

2014-12-02 06:05:48.630 spid4s     Starting execution of SSIS_DISCOVERY.SQL                                                           

2014-12-02 06:05:48.630 spid4s     ------------------------------------------------------                                             

2014-12-02 06:05:48.630 spid4s     Database 'master' is upgrading script 'ssis_discovery' from level 184552376 to level 184552715.    

2014-12-02 06:05:48.590 Logon      Login failed for user 'test'. Reason: Server is in script upgrade mode. Only administrator can

what are the reason we getting those type of messages.

I have a SQL Server 2012 instance running in WFC on 3 servers and I need to change from the current Class C network to a Class A network. Here is my example:

Server 1 - 192.168.2.10>Change to: 10.10.1.10

Server 2 - 192.168.2.11>Change to: 10.10.1.11

Server 3 - 192.168.2.12>Change to: 10.10.1.12

Failover cluster instance IP: 192.168.2.20 >Change to: 10.10.1.20

SQL Server instance IP: 192.168.2.30>Change to: 10.10.1.30

My question is what order to do this in? Do I first change each server's IP address and then change the SQL instance IP, then Failover cluster IP? Or do I first change the SQL instance IP, then Failover instance IP and then each server network IP?

Do I need to have an additional network adapter with the new subnet active the whole time, or do I just change each node 1 by 1?

Any info will help. Thank you!

Hello~ I use SQL agent to start up a SSIS package. But I found sometimes a task : Datapump task , timeout.

Executed as user:Server\SYSTEM. Microsoft (R) SQL Server Execute Package Utility  Version 10.50.4000.0 for 32-bit  Copyright (C) Microsoft Corporation 2010. All rights reserved.    Started:  10:00:00 AM  Error: 2014-12-09 10:00:33.29     Code: 0xC0047062     Source: DTSTask_DTSDataPumpTask_1 ADO NET Source [73]     Description: System.Data.SqlClient.SqlException:Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.     at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)     at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)     at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)     at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)     at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()     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)     at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)     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.ExecuteDbDataReader(CommandBehavior behavior)     at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)     at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.PreExecute()     at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostPreExecute(IDTSManagedComponentWrapper100 wrapper)  End Error  Error: 2014-12-09 10:00:33.32     Code: 0xC004701A     Source: DTSTask_DTSDataPumpTask_1 SSIS.Pipeline     Description: component "ADO NET Source" (73) failed the pre-execute phase and returned error code 0x80131904.  End Error  DTExec: The package execution returned DTSER_FAILURE (1).  Started:  10:00:00 AM  Finished: 10:00:33 AM  Elapsed:  32.968 seconds.  The package execution failed.  The step failed.

actually the SSIS only pointing to local server, don't know why still timeout.

Greetings. I'm starting to explore the use of Mgmt Data Warehouse and have some questions pertaining to creating a custom Collection Set via Profiler. 

I used this link to create a Collection Set to my liking for queries taking >= 5 seconds, and it got created as expected. 

Questions: 

1. While I was able to create the collection set, I don't see a table to query that collected data from? Links like this indicate that a new table will be created for me, but that never happens. It should also be noted that the referenced collection set is created via regular TSQL script, not Profiler the way I'm attempting.
2. Whats the benefit of using a Collection Set like this over simply using Profiler?
3. Once created and working, will other boxes be able to make use of this Custom Collection Set?

Thanks!

TIA, ChrisRDBA