SQL Server TDE stuck encryption state 4
I'm trying to create a robust script that runs backups, backs up current certificate, creates a new certificate, backs up new certificate and regenerates database encryption keys with the new certificate. Obviously to do all this you're talking about a pretty
complicated script! i've tried to make it as robust as possible, however when running the script the databases have gotten stuck in encryption state 4. (this has happened before which is why i'm testing this to destruction.) now before i delete and recreate
these databases is there any way to force them out of state 4? It will not allow you to turn encryption off you get the following error : Cannot disable database encryption while an encryption, decryption, or key change scan is in progress.
I'm not sure what happened to get them into this state but want to prevent it at all costs.
Please see my script. You should be able to test this easily by creating a couple db's.
Any improvements would be greatly appreciated, and this will be extremely useful to anyone in a TDE environment.
*** UPDATED ***
USE master
DECLARE @Name NVARCHAR(50) , -- Database Name
@Path NVARCHAR(100) , -- Path for backup files
@FileName NVARCHAR(256) , -- Filename for backup
@FileDate NVARCHAR(20) , -- Used for file name
@BackupSetName NVARCHAR(50) ,
@SQLScript NVARCHAR(MAX) ,
@Live AS NCHAR(3) = 'No'
-- *** MAKE SURE YOU CHECK THIS BEFORE RUNNING ***
-- specify database backup directory
SET @Path = 'E:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Backup\'
-- specify filename format
SET @FileDate = REPLACE(REPLACE(REPLACE(CONVERT(NVARCHAR(20), GETDATE(), 120),
IF CURSOR_STATUS('global', 'db_cursor') >= -1
DEALLOCATE db_cursor
DECLARE db_cursor CURSOR
FOR
SELECT Name
FROM sys.databases
WHERE Name NOT IN ( 'master', 'model', 'msdb', 'tempdb' )
AND is_encrypted = 1
OPEN db_cursor
FETCH NEXT FROM db_cursor INTO @Name
WHILE @@FETCH_STATUS = 0
BEGIN TRY
SET @FileName = @Path + @Name + '_' + @FileDate + '.bak'
SET @SQLScript = 'BACKUP DATABASE ' + @Name + ' TO DISK = '''
+ @FileName + ''' WITH NOFORMAT, INIT, SKIP, STATS = 10
RESTORE VERIFYONLY FROM DISK = ''' + @FileName + ''' BACKUP LOG '
+ @Name + ' TO DISK = ''' + @Path + @Name + '_log.ldf'''
PRINT '*** STEP ONE Backing up Databases ***'
PRINT @SQLScript
IF @Live = 'Yes'
EXEC (@SQLScript)
FETCH NEXT FROM db_cursor INTO @Name
END TRY
BEGIN CATCH
PRINT 'Error Completing Backups'
SELECT ERROR_NUMBER() AS ErrorNumber ,
ERROR_SEVERITY() AS ErrorSeverity ,
ERROR_STATE() AS ErrorState ,
ERROR_PROCEDURE() AS ErrorProcedure ,
ERROR_LINE() AS ErrorLine ,
ERROR_MESSAGE() AS ErrorMessage;
RETURN
END CATCH
CLOSE db_cursor
DEALLOCATE db_cursor
-- Get current certificate statuses
SELECT DB_NAME(database_id) AS DatabaseName ,
Name AS CertificateName ,
CASE encryption_state
WHEN 0 THEN 'No database encryption key present, no encryption'
WHEN 1 THEN 'Unencrypted'
WHEN 2 THEN 'Encryption in progress'
WHEN 3 THEN 'Encrypted'
WHEN 4 THEN 'Key change in progress'
WHEN 5 THEN 'Decryption in progress'
END AS encryption_state_desc ,
create_date ,
regenerate_date ,
modify_date ,
set_date ,
opened_date ,
key_algorithm ,
key_length ,
encryptor_thumbprint ,
percent_complete ,
certificate_id ,
principal_id ,
pvt_key_encryption_type ,
pvt_key_encryption_type_desc ,
issuer_name ,
cert_serial_number ,
subject ,
expiry_date ,
start_date ,
thumbprint ,
pvt_key_last_backup_date
FROM sys.dm_database_encryption_keys AS e
LEFT JOIN master.sys.certificates AS c ON e.encryptor_thumbprint = c.thumbprint
-- TDE cannot be started while backup is running
WHILE EXISTS ( SELECT *
FROM master.dbo.sysprocesses
WHERE dbid IN ( DB_ID('*** DATABASE ***') )
AND cmd LIKE 'BACKUP%' )
BEGIN
PRINT 'Waiting for backups to complete'
WAITFOR DELAY '00:01:00'
END
--Code for backing up certificate and generating new certificate
DECLARE @CurrentCertificateName AS NVARCHAR(100) ,
@CertificateBackupFile AS NVARCHAR(256) ,
@KeyBackup AS NVARCHAR(256) ,
@KeyStore AS NVARCHAR(256) = 'E:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Key Backup\' ,
@SecurePass AS NVARCHAR(50) = '*** Password ***'
-- Get current certificate name
SELECT @CurrentCertificateName = c.name
FROM sys.dm_database_encryption_keys AS e
LEFT JOIN master.sys.certificates AS c ON e.encryptor_thumbprint = c.thumbprint
WHERE DB_NAME(e.database_id) = @Name
-- backup the current certificate
SET @CertificateBackupFile = @KeyStore + @CurrentCertificateName + '.cer'
SET @KeyBackup = @KeyStore + @CurrentCertificateName + '.pvk'
SET @SQLScript = 'BACKUP CERTIFICATE ' + @CurrentCertificateName
+ +' TO FILE = ''' + @CertificateBackupFile + ''' WITH PRIVATE KEY'
+ ' (FILE = ''' + @KeyBackup + ''',' + ' ENCRYPTION BY PASSWORD = '''
+ @SecurePass + ''')'
PRINT '*** STEP TWO Backing up current certificate: ' + @SQLScript + ' ***'
IF @Live = 'Yes'
BEGIN TRY
EXEC ( @SQLScript )
END TRY
BEGIN CATCH
PRINT 'Could not back up existing Certificate. Job Cancelled'
SELECT ERROR_NUMBER() AS ErrorNumber ,
ERROR_SEVERITY() AS ErrorSeverity ,
ERROR_STATE() AS ErrorState ,
ERROR_PROCEDURE() AS ErrorProcedure ,
ERROR_LINE() AS ErrorLine ,
ERROR_MESSAGE() AS ErrorMessage;
RETURN
END CATCH
-- Generate the new certificate.
DECLARE @Now AS NVARCHAR(12) = REPLACE(REPLACE(REPLACE(CONVERT(NVARCHAR(20), GETDATE(), 120),
DECLARE @NewCertificateName AS NVARCHAR(50) = 'PCI_Compliance_Certificate_'
+ @Now
-- Manually set certificate name
--SELECT @NewCertificateName = 'PCI_Compliance_Certificate_201312231546'
-- Generate a new certificate
DECLARE @NewCertificateDescription AS NVARCHAR(100) = 'PCI DSS Compliance Certificate for 2014'
SET @SQLScript = 'CREATE CERTIFICATE ' + @NewCertificateName
+ ' WITH SUBJECT = ''' + @NewCertificateDescription + ''''
PRINT '*** STEP THREE Creating New Certificate: ' + @SQLScript + ' ***'
IF @Live = 'Yes'
BEGIN TRY
EXEC ( @SQLScript
END TRY
BEGIN CATCH
PRINT 'Could not create the new Certificate. Job Cancelled'
SELECT ERROR_NUMBER() AS ErrorNumber ,
ERROR_SEVERITY() AS ErrorSeverity ,
ERROR_STATE() AS ErrorState ,
ERROR_PROCEDURE() AS ErrorProcedure ,
ERROR_LINE() AS ErrorLine ,
ERROR_MESSAGE() AS ErrorMessage;
RETURN
END CATCH
-- Back up the new certificate
SET @CertificateBackupFile = @KeyStore + @NewCertificateName + '.cer'
SET @KeyBackup = @KeyStore + @NewCertificateName + '.pvk'
SET @SQLScript = 'BACKUP CERTIFICATE ' + @NewCertificateName
+ +' TO FILE = ''' + @CertificateBackupFile + '''' + ' WITH PRIVATE KEY'
+ ' (FILE = ''' + @KeyBackup + ''',' + ' ENCRYPTION BY PASSWORD = '''
+ @SecurePass + ''')'
PRINT '*** STEP FOUR Backing up New Certificate: ' + @SQLScript + ' ***'
IF @Live = 'Yes'
BEGIN TRY
EXEC ( @SQLScript
END TRY
BEGIN CATCH
PRINT 'Error: Could not back up New Certificate.'
SELECT ERROR_NUMBER() AS ErrorNumber ,
ERROR_SEVERITY() AS ErrorSeverity ,
ERROR_STATE() AS ErrorState ,
ERROR_PROCEDURE() AS ErrorProcedure ,
ERROR_LINE() AS ErrorLine ,
ERROR_MESSAGE() AS ErrorMessage;
RETURN
END CATCH
--Encrypt database with new certificate
WHILE EXISTS ( SELECT *
FROM master.dbo.sysprocesses
WHERE dbid IN ( DB_ID('*** DATABASE ***') )
AND cmd LIKE 'BACKUP%' )
BEGIN
PRINT 'Waiting for backups to complete'
WAITFOR DELAY '00:01:00'
END
DECLARE db_cursor CURSOR
FOR
SELECT Name
FROM sys.databases
WHERE Name NOT IN ( 'master', 'model', 'msdb', 'tempdb' )
AND is_encrypted = 1
OPEN db_cursor
FETCH NEXT FROM db_cursor INTO @Name
WHILE @@FETCH_STATUS = 0
BEGIN TRY
SET @SQLScript = 'USE ' + @Name
+ ' ALTER DATABASE ENCRYPTION KEY REGENERATE WITH ALGORITHM = AES_256 ENCRYPTION BY SERVER CERTIFICATE '
+ 'PCI_Compliance_Certificate_' + @Now
PRINT '*** STEP FIVE Encrypting Databases ***'
PRINT @SQLScript
IF @Live = 'Yes'
EXEC (@SQLScript)
FETCH NEXT FROM db_cursor INTO @Name
END TRY
BEGIN CATCH
PRINT 'Error Encrypting Databases'
SELECT ERROR_NUMBER() AS ErrorNumber ,
ERROR_SEVERITY() AS ErrorSeverity ,
ERROR_STATE() AS ErrorState ,
ERROR_PROCEDURE() AS ErrorProcedure ,
ERROR_LINE() AS ErrorLine ,
ERROR_MESSAGE() AS ErrorMessage;
RETURN
END CATCH
CLOSE db_cursor
DEALLOCATE db_cursor
-- Inspect the new state of the databases
SELECT DB_NAME(e.database_id) AS DatabaseName ,
e.database_id ,
e.encryption_state ,
CASE e.encryption_state
WHEN 0 THEN 'No database encryption key present, no encryption'
WHEN 1 THEN 'Unencrypted'
WHEN 2 THEN 'Encryption in progress'
WHEN 3 THEN 'Encrypted'
WHEN 4 THEN 'Key change in progress'
WHEN 5 THEN 'Decryption in progress'
END AS encryption_state_desc ,
c.name ,
e.percent_complete
FROM sys.dm_database_encryption_keys AS e
LEFT JOIN master.sys.certificates AS c ON e.encryptor_thumbprint = c.thumbprint
Hello,
State 4 means (as you've noted in your script) that there is a key change in process. When a key change happens with TDE, all of the data must first be decrypted with the old keys and encrypted with the new keys which takes time. However long it takes to
decrypt and encrypt your entire database (depending on how many key changes there are in the hierarchy) is how long it will take.
There is also a very niche scenario where database corruption can cause issues with TDE while encrypting or decrypting. You could run a CHECKDB and validate this is not the case (you can also check suspect_pages at a quick glance).
Sean Gallardy | Blog |
Twitter
Similar Messages
-
SQL Server Transparent Data encryption
I have implemented TDE for the Database and Column Level Encryption for Sensitive data in Tables. But, the Porblem is the data is entered through an front end application how could i encrypt this data when it is inserted from the Front end. And how to decry-pt
this data for the users when it is selected.
Your suggestions are most valuable.
Reagrds
Rehaan Khan
RehaanKhan. MLet me start with a solution that may have been overlooked, but it is good to make sure we cover it. Have you considered using column-level permissions? It may not be a complete solution for your particular scenario if you need to give access to the column
for other reasons (after all, the group you are trying to restrict is probably developing applications on top of the column storing sensitive data) or if the developer group has permission to create objects that would render the sensitive data subject to ownership
chains. For more information on column-permissions look at
http://msdn.microsoft.com/en-us/library/ms186915.aspx
Assuming permissions alone will not solve the problem. By using encryption you should be able to limit access to the sensitive data to the developers, but it will also require some changes to your schema & application. TDE (Transparent Data Encryption)
will not help you in this scenario since you need to restrict access to the data and restricting access to the column is not sufficient.
The following links may be useful to get you started with SQL Encryption capabilities:
SQL Server Encryption (http://msdn.microsoft.com/en-us/library/bb510663.aspx)
Data Encryption in SQL Server (http://msdn.microsoft.com/en-us/library/bb669072(v=vs.110).aspx)
Encrypt a Column of data (http://msdn.microsoft.com/en-us/library/ms179331.aspx)
Cryptographic Functions (T-SQL) (http://msdn.microsoft.com/en-us/library/ms173744.aspx)
Older articles, but they may still be quite useful:
Indexing encrypted Data (http://blogs.msdn.com/b/raulga/archive/2006/03/11/549754.aspx)
SQL Server 2005: searching encrypted data (http://blogs.msdn.com/b/lcris/archive/2005/12/22/506931.aspx)
One recommendation may be to encrypt the data using an AES key, and protect the key using one or more certificates (I would recommend using a separate certificate per individual if possible), making sure that only authorized people have access to the keys.
Anyone else with access to the column, but not to the keys would not be able to decrypt the data.
BTW. I would also recommend using SQL Auditing (http://msdn.microsoft.com/en-us/library/cc280386.aspx) in order to keep honest people honest, by monitoring access to the keys & to the
sensitive data.
I hope this information helps,
-Raul Garcia
SQL Server Security
This posting is provided "AS IS" with no warranties, and confers no rights. -
Convert the insert statement of an MS SQL server into an oracle statement
Hi ,
The insert statement in the ms sql server is
INSERT INTO #temp EXEC Procedurename @Id OUTPUT
where table temp
CREATE TABLE #temp(
Id varchar(10),
FNa varchar(40),
LNa varchar(40),
SId varchar(20),
Aid varchar(20),
Did varchar(20),
CCNa varchar(255),
CCId int,
ISu char(1),
IA char(1),
Dir char(1),
Ema varchar(60),
St char(2),
DId char(3)
I converted the insert statement like this
Procedurename(Id);
LOOP
FETCH cv_1 INTO v_temp;
EXIT WHEN cv_1%NOTFOUND;
INSERT INTO TEMP VALUES v_temp;
END LOOP;
CLOSE cv_1;
But i am receiving PL/SQL: ORA-00947: not enough values
Can anyone help on this?
Thanks1) Are you sure that you even need a temp table? Fetching all the rows from a cursor 1-by-1 and then inserting them into a temp table (I'm assuming the Oracle table TEMP is declared as a global temporary table) would seem rather unusual and most likely pointless. In Oracle, readers don't block writers, so there is generally no need to use temp tables to hold intermediate results.
2) If you do need to store a set of results into a table, it's going to be more efficient to do this in a single SQL statement rather than using a cursor. Something like
INSERT INTO my_table ( <<list of columns>> )
SELECT <<list of columns>>
FROM <<other tables>>
WHERE <<some conditions>>The SELECT part of the statement here is likely whatever SQL you use in declaring the cursor.
Justin -
MS sql server 2005 and encryption
I've got a Microsoft SQL Server 2005 database server set up
with encryption forced on. I managed to get the MS 1.1 jdbc driver
from Microsoft, I then tried to configure it into Coldfusion v
7.0.2 as an Other data source. The problem I've got now is that I
get the error
"com.microsoft.sqlserver.jdbc.SQLServerException: The SQL
Server login requires an SSL connection."
I previously tried to use the SQL Server data source type but
that didn't work either.
So how do I get past this hurdle?There is currently no SSL support for JDBC connections.
Microsoft addresses it regarding SQL Server 2005 on this mdsn
forum thread:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1071465&SiteID=1 -
Weblogic7.0 with MS SQL Server 2000 and Callable Statement
Hello,
we have a little problem with our weblogic application.
In the SQL Server we have written a simple stored procedure
CREATE PROCEDURE nextval
@sequence_id INT OUT
AS
-- return an error if sequence does not exist
-- so we will know if someone truncates the table
set @sequence_id = -1
UPDATE sequences
SET @sequence_id = sequence_id = sequence_id + 1
RETURN @sequence_id
GO
It's a simple pk generator.
Also we have written a simple java application to test this procedure (getting
the connection over the weblogic datasource) and everything works fine.
But in the application running on weblogic we have problems with the second call.
Here the exceptions:
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal conn vor = null
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal conn nach = weblogic.jdbc.rmi.SerialConnection@397317
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal prepareCall
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal set gina
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal registeredOUtparameter
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal execute = false
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal nextVal = 30037
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal conn vor = null
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal conn nach = weblogic.jdbc.rmi.SerialConnection@4377a3
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal prepareCall
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal set gina
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal registeredOUtparameter
03.09.2002 / 14:33:24: [LOGLEVEL: 0] PKGenerator.nextVal execute = false
03.09.2002 / 14:33:24: [LOGLEVEL: 0] ****** PKGenerator.nextVal SQLException =
java.sql.SQLException: The transaction is no longer active (status = Rolling Back.
[Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out
after 29 seconds
Name=[EJB de.fiatbank.vehicle.template.beans.TemplateDetailEJB.create(java.util.ArrayList,java.util.ArrayList,java.util.ArrayList,java.lang.String)],Xid=220:408eb51e3b228e43(691834),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=29,seconds left=30,activeThread=Thread[ExecuteThread: '14' for queue:
'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=started,assigned=none,xar=weblogic.jdbc.jts.Connection@ffb40),SCInfo[fiatbank+gina]=(state=active),properties=({weblogic.transaction.name=[EJB
de.fiatbank.vehicle.template.beans.TemplateDetailEJB.create(java.util.ArrayList,java.util.ArrayList,java.util.ArrayList,java.lang.String)],
weblogic.jdbc=t3://192.168.0.27:7001, LOCAL_ENTITY_TX=true}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=gina+192.168.0.27:7001+fiatbank+t3+,
Resources={})],CoordinatorURL=gina+192.168.0.27:7001+fiatbank+t3+)]). No further
JDBC access is allowed within this transaction.
the two files are:
PKGenerator.java (Weblogic application)
CallableSamples1.java (TestApplication)
Has anyone an idea, if weblogic has a problem or we have made a mistake?
Bye
Steffen
[files.zip]Steffen Schenk wrote:
Hello,
we have a little problem with our weblogic application.Hi. It's not a JDBC issue, it's an EJB/transaction coordinator issue.
Any transactional EJB JDBC is done under the (usually silent) control of the
transaction coordinator. For instance, if your code calls Connection.commit()
in a transactional EJB, it will cheerfully be ignored, because only the transaction
coordinator knows when and whether to commit the whole transaction, not the
individual EJB, which may have been called as part of a larger transaction. Another
aspect of the coordinator's overseeing of the transaction is that once the transaction
is over, which may be right in the middle of an EJB's running if the transaction
timeout limit has been reached, then the coordinator will roll back or commit the
transaction as appropriate and take control of the JDBC objects. Any further attempt
by the EJB to do any JDBC will result in an exception.
>
In the SQL Server we have written a simple stored procedure
CREATE PROCEDURE nextval
@sequence_id INT OUT
AS
-- return an error if sequence does not exist
-- so we will know if someone truncates the table
set @sequence_id = -1
UPDATE sequences
SET @sequence_id = sequence_id = sequence_id + 1
RETURN @sequence_id
GO
It's a simple pk generator.
Also we have written a simple java application to test this procedure (getting
the connection over the weblogic datasource) and everything works fine.
But in the application running on weblogic we have problems with the second call.
Here the exceptions:
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal conn vor = null
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal conn nach = weblogic.jdbc.rmi.SerialConnection@397317
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal prepareCall
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal set gina
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal registeredOUtparameter
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal execute = false
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal nextVal = 30037
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal conn vor = null
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal conn nach = weblogic.jdbc.rmi.SerialConnection@4377a3
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal prepareCall
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal set gina
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal registeredOUtparameter
03.09.2002 / 14:33:24: [LOGLEVEL: 0] PKGenerator.nextVal execute = false
03.09.2002 / 14:33:24: [LOGLEVEL: 0] ****** PKGenerator.nextVal SQLException =
java.sql.SQLException: The transaction is no longer active (status = Rolling Back.
[Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out
after 29 seconds
Name=[EJB de.fiatbank.vehicle.template.beans.TemplateDetailEJB.create(java.util.ArrayList,java.util.ArrayList,java.util.ArrayList,java.lang.String)],Xid=220:408eb51e3b228e43(691834),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=29,seconds left=30,activeThread=Thread[ExecuteThread: '14' for queue:
'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=started,assigned=none,xar=weblogic.jdbc.jts.Connection@ffb40),SCInfo[fiatbank+gina]=(state=active),properties=({weblogic.transaction.name=[EJB
de.fiatbank.vehicle.template.beans.TemplateDetailEJB.create(java.util.ArrayList,java.util.ArrayList,java.util.ArrayList,java.lang.String)],
weblogic.jdbc=t3://192.168.0.27:7001, LOCAL_ENTITY_TX=true}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=gina+192.168.0.27:7001+fiatbank+t3+,
Resources={})],CoordinatorURL=gina+192.168.0.27:7001+fiatbank+t3+)]). No further
JDBC access is allowed within this transaction.
the two files are:
PKGenerator.java (Weblogic application)
CallableSamples1.java (TestApplication)
Has anyone an idea, if weblogic has a problem or we have made a mistake?
Bye
Steffen
Name: files.zip
files.zip Type: Zip Compressed Data (application/x-zip-compressed)
Encoding: base64 -
Oracle statement to SQL Server
Hi All,
I have a oracle statement, I need same logic in SQL Server. I know in SQL server we use CASE statement instead of decode, but I don't understand this oracle statement
Select count(decode(sign((A.StartDate - A.EndDate) - 60) ,-1, 'NewDateField',0, 'NewDateField')) NewDateField_1
From SampleTable A
I need SQL code for this in SQL server.
Thanks in advance,
RH
sqlHi sql9, I am guessing here since DDL is missing.
The code you have shown, calculating difference between startdate and enddate and then deducting 60. The result is checking to see whether negative number or zero ignoring positive number. Finally counting how many of these in a table ie., looks like counting
number of records whose elapsed days between startdate and enddate are less than or equal to 60 days.
Select count(decode(sign((A.StartDate - A.EndDate) - 60) ,-1, 'NewDateField',0, 'NewDateField')) NewDateField_1
From SampleTable A
Few interesting observations:
1. Perhaps startdate and enddate columns are integer data types as there are no date manipulation functions used.
2. It never yields either 0 or positive number unless startdate is greater than enddate.
Please refer the code shown below to prove the above mentioned points. Also note that CNT1, CNT2 and CNT3 are all equivalent to your expected result to pass to aggregate function COUNT. Hope it helps.
declare @SampleTable table ( id int identity,startDate datetime, EndDate datetime, startDT int, EndDt int )
insert into @SampleTable(startDate, EndDate, startDT, EndDt )
values ('04/01/2014', '04/23/2014', 20140401, 20140423),
('01/01/2013', '04/03/2013', 20130101,20130403),
('04/05/2013','04/05/2013', 20130405,20130405),
('04/05/2013','04/05/2014', 20130405,20140405)
select
startdate, enddate,
dateadd(day,60, startdate) 'Add 60 days',
datediff(day, startdate, enddate) 'elapsed days',
case
when dateadd(day, 60,startdate)>= enddate then 1
else null
end as 'cnt1',
case
when startdate>= dateadd(day, -60,enddate) then 1
else null
end as 'cnt2',
case
when datediff(day, startdate, enddate) <=60 then 1
else null
end as 'cnt3',
startDT,
enddt
from @SampleTable
select
count(
case (sign((startDT - enddt)-60))
when -1 then 'NewDateField'
when 0 then 'NewDateField'
end
) as NewDateField_1
from @SampleTable -
hi there:
I've experienced several sql server service crashes yesterday, service was brought up after a few secs as we have an autostart feature.
Today, I'd like to dig more into the errors and on the event viewer -> Application, I saw errors below
"Faulting application sqlservr.exe, version 2009.100.4302.0, time stamp 0x52f5d194, faulting module ntdll.dll, version 6.0.6001.18538, time stamp 0x4cb73957, exception code 0xc0000374, fault offset 0x00000000000a7857, process id 0x15ec, application
start time 0x01cfd7e72b2997d3.
People suggested to check dump file inside C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\Log
However, the lastest .mdmp file was on April 11, 2014. Do I need to turn on some settings on sql server in order to have this dump file?
Thanks
Hui
--Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --Results after sp_readerrorlog 1
LogDate ProcessInfo
Text
2014-09-24 04:03:28.460 Server
Microsoft SQL Server 2008 R2 (SP2) - 10.50.4302.0 (X64)
Feb 7 2014 17:23:24
Copyright (c) Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 6.0 <X64> (Build 6001: Service Pack 1)
2014-09-24 04:03:28.460 Server
(c) Microsoft Corporation.
2014-09-24 04:03:28.460 Server
All rights reserved.
2014-09-24 04:03:28.460 Server
Server process ID is 5612.
2014-09-24 04:03:28.460 Server
System Manufacturer: 'IBM', System Model: 'IBM System x3650 -[7979AC1]-'.
2014-09-24 04:03:28.460 Server
Authentication mode is MIXED.
2014-09-24 04:03:28.460 Server
Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\Log\ERRORLOG'.
2014-09-24 04:03:28.460 Server
This instance of SQL Server last reported using a process ID of 6780 at 9/24/2014 4:03:20 AM (local) 9/24/2014 11:03:20 AM (UTC). This is an informational message only; no user action is required.
2014-09-24 04:03:28.460 Server
Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\DATA\mastlog.ldf
2014-09-24 04:03:28.480 Server
SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2014-09-24 04:03:28.480 Server
Detected 4 CPUs. This is an informational message; no user action is required.
2014-09-24 04:03:28.480 Server
Cannot use Large Page Extensions: lock memory privilege was not granted.
2014-09-24 04:03:28.580 Server
Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2014-09-24 04:03:28.700 Server
Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2014-09-24 04:03:28.870 spid7s
Starting up database 'master'.
2014-09-24 04:03:28.940 spid7s
1 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.
2014-09-24 04:03:28.940 spid7s
0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
2014-09-24 04:03:28.940 spid7s
Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2014-09-24 04:03:29.040 spid7s
CHECKDB for database 'master' finished without errors on 2014-09-20 12:00:01.697 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:29.050 spid7s
Resource governor reconfiguration succeeded.
2014-09-24 04:03:29.050 spid7s
SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2014-09-24 04:03:29.050 spid7s
SQL Server Audit has started the audits. This is an informational message. No user action is required.
2014-09-24 04:03:29.050 spid7s
FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQL2008R2'.
2014-09-24 04:03:29.070 spid7s
SQL Trace ID 1 was started by login "sa".
2014-09-24 04:03:29.070 spid7s
Starting up database 'mssqlsystemresource'.
2014-09-24 04:03:29.090 spid7s
The resource database build version is 10.50.4302. This is an informational message only. No user action is required.
2014-09-24 04:03:29.600 spid10s
Starting up database 'model'.
2014-09-24 04:03:29.600 spid7s
Server name is 'BPWDB046\SQL2008R2'. This is an informational message only. No user action is required.
2014-09-24 04:03:29.880 spid13s
A new instance of the full-text filter daemon host process has been successfully started.
2014-09-24 04:03:29.960 spid14s
Starting up database 'msdb'.
2014-09-24 04:03:29.960 spid17s
Starting up database 'DW_Detail'.
2014-09-24 04:03:29.960 spid16s
Starting up database 'ReportServer_MSSQLSSRSTempDB'.
2014-09-24 04:03:29.960 spid13s
Starting up database 'Billing_Rep'.
2014-09-24 04:03:29.960 spid15s
Starting up database 'ReportServer_MSSQLSSRS'.
2014-09-24 04:03:29.960 spid18s
Starting up database 'BCBio_DW'.
2014-09-24 04:03:29.960 spid19s
Starting up database 'ODS'.
2014-09-24 04:03:29.960 spid20s
Starting up database 'ReportServer$SQL2008'.
2014-09-24 04:03:29.970 spid21s
Starting up database 'ReportServer$SQL2008TempDB'.
2014-09-24 04:03:29.970 spid22s
Starting up database 'Billing'.
2014-09-24 04:03:29.970 spid23s
Starting up database 'Billing_Snap'.
2014-09-24 04:03:29.970 spid24s
Starting up database 'DBA'.
2014-09-24 04:03:30.000 Server
A self-generated certificate was successfully loaded for encryption.
2014-09-24 04:03:30.000 Server
Server is listening on [ 'any' <ipv6> 52328].
2014-09-24 04:03:30.000 Server
Server is listening on [ 'any' <ipv4> 52328].
2014-09-24 04:03:30.000 Server
Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQL2008R2 ].
2014-09-24 04:03:30.000 Server
Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SQL2008R2\sql\query ].
2014-09-24 04:03:30.010 Server
Server is listening on [ ::1 <ipv6> 52329].
2014-09-24 04:03:30.010 Server
Server is listening on [ 127.0.0.1 <ipv4> 52329].
2014-09-24 04:03:30.010 Server
Dedicated admin connection support was established for listening locally on port 52329.
2014-09-24 04:03:30.060 spid10s
CHECKDB for database 'model' finished without errors on 2014-09-20 12:00:17.583 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:30.060 spid10s
Clearing tempdb database.
2014-09-24 04:03:30.140 Server
The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/BPWDB046.bcbio.org:SQL2008R2 ] for the SQL Server service.
2014-09-24 04:03:30.140 Server
The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/BPWDB046.bcbio.org:52328 ] for the SQL Server service.
2014-09-24 04:03:30.140 Server
SQL Server is now ready for client connections. This is an informational message; no user action is required.
2014-09-24 04:03:30.480 spid21s
CHECKDB for database 'ReportServer$SQL2008TempDB' finished without errors on 2014-09-20 16:13:10.043 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:30.520 spid14s
2933 transactions rolled forward in database 'msdb' (4). This is an informational message only. No user action is required.
2014-09-24 04:03:30.650 spid7s
0 transactions rolled back in database 'msdb' (4). This is an informational message only. No user action is required.
2014-09-24 04:03:30.650 spid7s
Recovery is writing a checkpoint in database 'msdb' (4). This is an informational message only. No user action is required.
2014-09-24 04:03:30.770 spid14s
CHECKDB for database 'msdb' finished without errors on 2014-09-20 12:00:18.473 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:30.950 spid10s
Starting up database 'tempdb'.
2014-09-24 04:03:30.990 spid52
Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2014-09-24 04:03:31.010 spid52
Using 'xpstar.dll' version '2009.100.1600' to execute extended stored procedure 'xp_sqlagent_monitor'. This is an informational message only; no user action is required.
2014-09-24 04:03:31.060 spid14s
The Service Broker protocol transport is disabled or not configured.
2014-09-24 04:03:31.060 spid14s
The Database Mirroring protocol transport is disabled or not configured.
2014-09-24 04:03:31.070 spid14s
Service Broker manager has started.
2014-09-24 04:03:31.330 spid16s
CHECKDB for database 'ReportServer_MSSQLSSRSTempDB' finished without errors on 2014-09-20 12:00:39.873 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:31.500 spid20s
2 transactions rolled forward in database 'ReportServer$SQL2008' (11). This is an informational message only. No user action is required.
2014-09-24 04:03:31.960 spid7s
0 transactions rolled back in database 'ReportServer$SQL2008' (11). This is an informational message only. No user action is required.
2014-09-24 04:03:31.960 spid7s
Recovery is writing a checkpoint in database 'ReportServer$SQL2008' (11). This is an informational message only. No user action is required.
2014-09-24 04:03:32.150 spid20s
CHECKDB for database 'ReportServer$SQL2008' finished without errors on 2014-09-20 16:13:07.583 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:33.170 spid24s
CHECKDB for database 'DBA' finished without errors on 2014-09-20 16:22:41.603 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:33.600 spid13s
Recovery of database 'Billing_Rep' (8) is 0% complete (approximately 1537 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:03:34.820 spid15s
CHECKDB for database 'ReportServer_MSSQLSSRS' finished without errors on 2014-09-20 12:00:32.067 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:48.290 spid13s
Recovery of database 'Billing_Rep' (8) is 1% complete (approximately 1488 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:03:49.520 spid17s
1 transactions rolled forward in database 'DW_Detail' (7). This is an informational message only. No user action is required.
2014-09-24 04:03:50.070 spid7s
0 transactions rolled back in database 'DW_Detail' (7). This is an informational message only. No user action is required.
2014-09-24 04:03:50.070 spid7s
Recovery is writing a checkpoint in database 'DW_Detail' (7). This is an informational message only. No user action is required.
2014-09-24 04:03:50.070 spid7s
Recovery completed for database DW_Detail (database ID 7) in 5 second(s) (analysis 251 ms, redo 4314 ms, undo 44 ms.) This is an informational message only. No user action is required.
2014-09-24 04:03:50.520 spid22s
CHECKDB for database 'Billing' finished without errors on 2013-04-25 18:47:20.743 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:51.620 spid17s
CHECKDB for database 'DW_Detail' finished without errors on 2014-09-20 12:00:46.917 (local time). This is an informational message only; no user action is required.
2014-09-24 04:04:03.740 spid13s
Recovery of database 'Billing_Rep' (8) is 2% complete (approximately 1493 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:13.040 spid13s
Recovery of database 'Billing_Rep' (8) is 0% complete (approximately 8052 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:23.220 spid18s
Database BCBio_DW has more than 1000 virtual log files which is excessive. Too many virtual log files can cause long startup and backup times. Consider shrinking the log and using a different growth increment to reduce the number of virtual log files.
2014-09-24 04:04:23.420 spid18s
Recovery of database 'BCBio_DW' (9) is 0% complete (approximately 4664 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:25.640 spid18s
Recovery of database 'BCBio_DW' (9) is 0% complete (approximately 4954 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:25.640 spid18s
Recovery of database 'BCBio_DW' (9) is 3% complete (approximately 74 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:25.730 spid18s
Recovery of database 'BCBio_DW' (9) is 2% complete (approximately 98 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:26.000 spid18s
Recovery of database 'BCBio_DW' (9) is 12% complete (approximately 18 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:28.000 spid19s
Database ODS has more than 1000 virtual log files which is excessive. Too many virtual log files can cause long startup and backup times. Consider shrinking the log and using a different growth increment to reduce the number of virtual log files.
2014-09-24 04:04:28.350 spid19s
CHECKDB for database 'ODS' finished without errors on 2014-09-20 16:07:22.603 (local time). This is an informational message only; no user action is required.
2014-09-24 04:04:29.370 spid18s
Recovery of database 'BCBio_DW' (9) is 19% complete (approximately 24 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:31.380 spid18s
Recovery of database 'BCBio_DW' (9) is 25% complete (approximately 22 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:32.490 spid18s
Recovery of database 'BCBio_DW' (9) is 32% complete (approximately 18 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:33.150 spid13s
Recovery of database 'Billing_Rep' (8) is 0% complete (approximately 9805 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:33.860 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 04:04:33.860 Logon
Login failed for user 'ETLAdmin'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.101.33]
2014-09-24 04:04:34.040 spid18s
Recovery of database 'BCBio_DW' (9) is 39% complete (approximately 15 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:35.600 spid18s
Recovery of database 'BCBio_DW' (9) is 46% complete (approximately 13 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:36.740 spid18s
Recovery of database 'BCBio_DW' (9) is 53% complete (approximately 10 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:37.220 spid13s
Recovery of database 'Billing_Rep' (8) is 0% complete (approximately 10106 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:37.230 spid13s
Recovery of database 'Billing_Rep' (8) is 2% complete (approximately 2587 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:37.360 spid13s
Recovery of database 'Billing_Rep' (8) is 1% complete (approximately 3654 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:37.560 spid13s
Recovery of database 'Billing_Rep' (8) is 3% complete (approximately 1564 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:38.070 spid13s
Recovery of database 'Billing_Rep' (8) is 4% complete (approximately 1328 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:38.830 spid18s
Recovery of database 'BCBio_DW' (9) is 61% complete (approximately 8 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:40.080 spid13s
Recovery of database 'Billing_Rep' (8) is 5% complete (approximately 1268 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:40.680 spid18s
Recovery of database 'BCBio_DW' (9) is 69% complete (approximately 6 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:42.960 spid18s
Recovery of database 'BCBio_DW' (9) is 77% complete (approximately 4 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:44.870 spid18s
Recovery of database 'BCBio_DW' (9) is 85% complete (approximately 3 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:44.870 spid18s
3 transactions rolled forward in database 'BCBio_DW' (9). This is an informational message only. No user action is required.
2014-09-24 04:04:45.120 spid18s
Recovery of database 'BCBio_DW' (9) is 85% complete (approximately 3 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:46.870 spid7s
0 transactions rolled back in database 'BCBio_DW' (9). This is an informational message only. No user action is required.
2014-09-24 04:04:46.870 spid7s
Recovery is writing a checkpoint in database 'BCBio_DW' (9). This is an informational message only. No user action is required.
2014-09-24 04:04:46.870 spid7s
Recovery completed for database BCBio_DW (database ID 9) in 23 second(s) (analysis 2417 ms, redo 19227 ms, undo 1745 ms.) This is an informational message only. No user action is required.
2014-09-24 04:04:47.610 spid18s
CHECKDB for database 'BCBio_DW' finished without errors on 2014-09-20 14:02:10.680 (local time). This is an informational message only; no user action is required.
2014-09-24 04:04:47.820 spid23s
Database Billing_Snap has more than 1000 virtual log files which is excessive. Too many virtual log files can cause long startup and backup times. Consider shrinking the log and using a different growth increment to reduce the number of virtual log files.
2014-09-24 04:04:48.570 spid23s
CHECKDB for database 'Billing_Snap' finished without errors on 2014-09-20 16:13:11.037 (local time). This is an informational message only; no user action is required.
2014-09-24 04:04:52.970 spid13s
Recovery of database 'Billing_Rep' (8) is 6% complete (approximately 1247 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:05:05.540 spid13s
Recovery of database 'Billing_Rep' (8) is 7% complete (approximately 1224 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:05:17.980 spid13s
Recovery of database 'Billing_Rep' (8) is 8% complete (approximately 1202 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:05:22.450 spid13s
Recovery of database 'Billing_Rep' (8) is 8% complete (approximately 1196 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:05:22.450 spid13s
1 transactions rolled forward in database 'Billing_Rep' (8). This is an informational message only. No user action is required.
2014-09-24 04:05:22.560 spid13s
Recovery of database 'Billing_Rep' (8) is 8% complete (approximately 1196 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
2014-09-24 04:05:22.710 spid13s
CHECKDB for database 'Billing_Rep' finished without errors on 2014-09-20 13:25:01.597 (local time). This is an informational message only; no user action is required.
2014-09-24 04:05:22.720 spid13s
0 transactions rolled back in database 'Billing_Rep' (8). This is an informational message only. No user action is required.
2014-09-24 04:05:22.720 spid13s
Recovery is writing a checkpoint in database 'Billing_Rep' (8). This is an informational message only. No user action is required.
2014-09-24 04:05:22.730 spid13s
Recovery completed for database Billing_Rep (database ID 8) in 109 second(s) (analysis 63983 ms, redo 45211 ms, undo 154 ms.) This is an informational message only. No user action is required.
2014-09-24 04:05:22.750 spid7s
Recovery is complete. This is an informational message only. No user action is required.
2014-09-24 07:00:06.930 spid53
Common language runtime (CLR) functionality initialized using CLR version v2.0.50727 from C:\Windows\Microsoft.NET\Framework64\v2.0.50727\.
2014-09-24 07:00:07.720 spid53
AppDomain 2 (mssqlsystemresource.sys[runtime].1) created.
2014-09-24 07:13:38.590 spid51
SQL Server blocked access to STATEMENT 'OpenRowset/OpenDatasource' of component 'Ad Hoc Distributed Queries' because this component is turned off as part of the security configuration for this server. A system administrator can enable the use of 'Ad
Hoc Distributed Queries' by using sp_configure. For more information about enabling 'Ad Hoc Distributed Queries', see "Surface Area Configuration" in SQL Server Books Online.
2014-09-24 07:13:53.870 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 07:13:53.870 Logon
Login failed for user 'BCBIO\sqlservice'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.100.6]
2014-09-24 07:13:56.560 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 07:13:56.560 Logon
Login failed for user 'BCBIO\sqlservice'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.100.6]
2014-09-24 07:13:57.460 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 07:13:57.460 Logon
Login failed for user 'BCBIO\sqlservice'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.100.6]
2014-09-24 07:13:57.560 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 07:13:57.560 Logon
Login failed for user 'BCBIO\sqlservice'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.100.6]
2014-09-24 07:13:57.950 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 07:13:57.950 Logon
Login failed for user 'BCBIO\sqlservice'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.100.6]
2014-09-24 07:14:04.410 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 07:14:04.410 Logon
Login failed for user 'BCBIO\sqlservice'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.100.6]
2014-09-24 07:14:04.960 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 07:14:04.960 Logon
Login failed for user 'BCBIO\sqlservice'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.100.6]
2014-09-24 07:34:13.330 spid54
Error: 17053, Severity: 16, State: 1.
2014-09-24 07:34:13.330 spid54
V:\log\templog.ldf: Operating system error 112(There is not enough space on the disk.) encountered.
2014-09-24 07:34:14.430 spid54
Error: 9002, Severity: 17, State: 4.
2014-09-24 07:34:14.430 spid54
The transaction log for database 'tempdb' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
--Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN -- -
Use of PVKConverter with SQL Server 2012 SP2
I am trying to convert a certificate that was exported from our database server to be used by SQL Server for database encryption. When I run the PVKConverter, not Private Key File (PVK) is generated.
The certificate has Server and Client Authentication as the purposes of the certificate.
What purpose or purposes does the certificate need in order to be able to be used by SQL Server 2012 SP2?
Why doesn't the PVKConverter generate a private key file?
I can use the command makecerts to generate a self signed certificate and have it work with SQL Server database encryption.
Thanks.
DJHi DJ,
Based on my research, SQL Server supports the importing of existing security certificates, specified as a pair of files that are encoded in PVK/DER format. Below Transact-SQL script displays the basic key file format for SQL Server database encryption.
CREATE CERTIFICATE <Certificate name>
FROM FILE = '<PVK/DER format file>.cer'
WITH PRIVATE KEY (FILE = '<PVK/DER format file>.pvk',
DECRYPTION BY PASSWORD = '<Encryption password>');
According to your description, PVKConverter doesn’t generate a private key file. PVKConverter is used to generate PVK/DER encoded security certificates from existing PFX encoded security certificates. Thus, please ensure that your certificate is encoded in
PFX format and make sure you perform all the steps properly as described in the
KB article.
There is also a related blog for your reference.
http://blogs.msdn.com/b/sql_pfe_blog/archive/2014/02/04/generating-a-trusted-tde-certificate-in-the-proper-format-from-a-certificate-authority.aspx
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support -
SQL Server 2012 restoring database from backup file
Hi All,
1. I was restoring the database from PROD box to DEV box with the deferent name.
For Ex: Both PROD and DEV boxes are having "A" database. Now I am refreshing database"A" from PROD bot to DEV box with name "B". Now while restoring in SQL server 2012 I used GUI and took database name as "A" by default.
by mistake I executed the request. before completing I notice that "A" database in DEV Box went to restoring mode.
Now, in middle I stopped the query but still I am seeing database "A" is in restoring state.
Please guide me is there any way to bring database online with current data?
2. Why sql server 2012 takes tail log backup of the existing database while restoring database with different name?Hi,
check this link for the same issue and solutions:
http://stackoverflow.com/questions/520967/sql-server-database-stuck-in-restoring-state
Ronen Ariely
[Personal Site] [Blog] [Facebook] -
What MS SQL Server Express version should I install?
Hi, I'm planning to use MS SQL Express for my LabVIEW app under Windows 7.
There are 3 versions available on the MS site: 2005, 2008, 2012. My first choice is on the latest, however I wonder if there may be any reason to choose an earlier version.
Also I wonder if the installation could conflict some way with the SQL Server Express 2005 the DSC module uses.
Sorry for my rather dumb questions but I'm not very strong on the relational databases subject.
Thanks a lot for any comment.
Paolo
LV 7.0, 7.1, 8.0.1, 2011Ranjeet...
I am using SQLServer Express 2012 with TestStand 2012 and having no luck getting TestStand to log to the catalog that I have created based off of the standard NI SQL scheme.
When creating the tables using the build sql file I found that...
I ran ito issues with the 'constraint' SQL commands TestStand was using:
CONSTRAINT STEP_RESULT_FK FOREIGN KEY (UUT_RESULT) REFERENCES (ID))
this must actually be:
CONSTRAINT STEP_RESULT_FK FOREIGN KEY (UUT_RESULT) REFERENCES UUT_RESULT (ID))
Note.... the 'UUT_RESULT' infront of (ID), without this the statement fails.
I had to correct all the constraint commands in order to get the tables built.
Now when I try to use the catalog to log data using TestStand I get...
An error occurred calling 'LogResults' in 'ITSDBLog' of 'zNI TestStand Database Logging'
An error occurred executing a statement.
Schema: SQL Server Stored Proc (NI)
Statement: UUT_RESULT.
Description: Could not find stored procedure 'InsertUUTResult'.
Number: -2147217900
NativeError: 2812
SQLState: 42000
Reported by: Microsoft OLE DB Provider for SQL Server
Source: TSDBLog
The procedure is present so I am confused.
FYI... I am currently using TestStand in eval mode as I am waiting on delivery, could the eval mode be the issue???
Any help would be greatly appreciated. I have done this before with TestStand 3.5 and SQL Server 2008 with no problems so I am confused why it not working now.
Pete -
MS SQL Server Architecture (Query Processing)
Explain Sql server Architecture for Select statement diagrammatically ?
Explain Sql server Architecture for Insert , update statements diagrammatically ?
bhageeHi,
to me, we have to completely read SQL Server Internals book to understanding internals of DMLs. so many internal compoents, layers works starting from pressing F5 at client location till we get the result in results pane.
Below link has high level info about SELECT
http://www.sqlservercentral.com/blogs/livingforsqlserver/2010/12/05/what-happens-when-a-query-is-submitted/
internals of SELECT
http://rusanu.com/2013/08/01/understanding-how-sql-server-executes-a-query/
Internals of INSERT
http://www.sqlservercentral.com/blogs/livingforsqlserver/2012/11/26/time-pass-with-transaction-log-part-4-ddl/
http://www.sqlservercentral.com/blogs/livingforsqlserver/2012/11/27/time-pass-with-transaction-log-part-5-insert/
hope you would find this useful.
Ramkumar Gopal Living For SQL Server Blog: http://www.sqlservercentral.com/blogs/livingforsqlserver/ Facebook: https://www.facebook.com/#!/groups/livingforsqlserver/ Twitter: https://twitter.com/LivingForSQL -
Does MS SQL Server provide an obfuscation tool whereby the actual data is obfuscated when copied to lower environments, such as Test, Training and Pre-Prod environments? I need to copy data from prod then obfuscate the data (sensitive data like a social
security number) from the contractors who work on the application.Sofiya, you completely misunderstood Elias's request. The purpose is not to encrypt the data, but alter it so that no sensitive information is disclosed. For instance a customer name like Barack Obama could be altered to Jack Jones. In this context, if the
information altered in some unrecoverable way, this is a plus. The purpose is to make it possible to use a production database in other environments.
And, no, there is nothing like this built-into SQL Server, and I am not sure that there should be, but this may be better left to the third-party market.
Erland Sommarskog, SQL Server MVP, [email protected]
Hi Erland,
Thanks for your post. I missed the customer’s requirement. In SQL Server, there is indeed no build-in tools which can change the sensitive data to an obfuscation data (such as your example) when you move the production database to a test
environment. If you use SQL Server Column Level encryption via symmetric keys, it only change the original data to an encrypted value which only be of datatype varbinary.
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support -
Upgrade from SQL Server 2005 to SQL Server Express 2014 Enterprise
I was just wondering if it is possible to upgrade from SQL Server 2005 to SQL Server Express or will I have to build the environment and then migrate the database?
Thanks for any helpHi Lance_Romance,
As others’ posts, you don’t have to build new environment and then migrate databases between SQL Server instances, you can use the in-place upgrade strategy to upgrade from SQL Server 2005 to SQL Server 2014 .Please note that SQL Server 2005 SP4 is required
in this case.
Before upgrading , I recommend you to use
upgrade advisor, it can help to analyze your existing SQL Server deployment and inform you of issues that need to be addressed. In addition, please perform a full server backup prior to performing the in-place upgrade, which will be an important way
to revert your SQL Server to its previous state if the upgrade does not go as planned. For more details, please review this blog:
Upgrading to SQL Server 2014: A Dozen Things to Check.
Thanks,
Lydia Zhang -
SCCM coudn't connect to database after recovering SQL server
Hello.
Please help to solve a problem. After crashing data storage, i have lost my SCCM and SQL server. I have restored SCCM server as virtual machine and re-install SQL server. I restored old databases to the new SQL server. Same instances and names.
And now i have logs smsexec.log :
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
SMS_EXECUTIVE
27.03.2015 10:34:19
3268 (0x0CC4)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
SMS_EXECUTIVE
27.03.2015 10:34:19
3268 (0x0CC4)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
SMS_EXECUTIVE
27.03.2015 10:34:19
3268 (0x0CC4)
CSiteControlEx::GetCurrentSiteInfo: Failed to get SQL connection
SMS_EXECUTIVE
27.03.2015 10:34:19
3268 (0x0CC4)
I found that i lost my certificate
i found article Certificate drop down menu empty when trying to select SSL certificate to enable SQL Server 2008 client encryption
but i get an error when trying to execute certificate request.
ERROR TRANSLATE --- no information about certificate template
I don't know what to do. Plz help. This problem sticks me. :(~===================== << Starting Configuration Manager 2012 Setup >> =====================
Configuration Manager Setup 01.04.2015 15:37:03
8980 (0x2314)
INFO: ConfigMgr2012 Setup was started by AV\dobrokhotov.vn.
Configuration Manager Setup 01.04.2015 15:37:03
8980 (0x2314)
INFO: Command line specified was: "C:\Program Files\Microsoft Configuration Manager\bin\X64\SetupWpf.exe"
Configuration Manager Setup 01.04.2015 15:37:03
8980 (0x2314)
FQDN for server SRV-SCCM is SRV-SCCM.ashipyards.com
Configuration Manager Setup 01.04.2015 15:37:03
8980 (0x2314)
INFO: Target computer is a 64 bit operating system.
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Checking for existing setup information.
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Setting setup type to 1. Configuration Manager Setup
01.04.2015 15:37:04 8980 (0x2314)
INFO: Checking for existing SQL information.
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: 'SRV-SQL.ashipyards.com' is a valid FQDN.
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Verifying the registry entry for Asset Intelligence installation
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Found registry key for installation of Asset Intelligence full version
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Setup detected an existing Configuration Manager installation. Currently installed version is 7958
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Phase is 1C7 Configuration Manager Setup
01.04.2015 15:37:04 8980 (0x2314)
WARNING: Failed to initialize COM to get SDK Providers. It might already be initialized. return code: 80010106.
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: SDK Provider is on SRV-SCCM.ashipyards.com.
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Setting the default CSV folder path Configuration Manager Setup
01.04.2015 15:37:04 8980 (0x2314)
INFO: Language: Mobile Device (INTL), LangPack: 0.
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Language: RUS, Server LangPack: 1. Configuration Manager Setup
01.04.2015 15:37:04 8980 (0x2314)
INFO: Language: RUS, Client LangPack: 1. Configuration Manager Setup
01.04.2015 15:37:04 8980 (0x2314)
INFO: Configuration Manager Build Number = 7958
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Configuration Manager Version = 5.0 Configuration Manager Setup
01.04.2015 15:37:04 8980 (0x2314)
INFO: Configuration Manager Minimum Build Number = 800
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Verifying Configuration Manager Active Directory Schema Extensions.
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Found DS Root:CN=Schema,CN=Configuration,DC=ashipyards,DC=com
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Verifying Configuration Manager Active Directory Schema Extensions.
Configuration Manager Setup 01.04.2015 15:37:04
8980 (0x2314)
INFO: Found DS Root:CN=Schema,CN=Configuration,DC=ashipyards,DC=com
Configuration Manager Setup 01.04.2015 15:37:05
8980 (0x2314)
INFO: SqlMasterDB = MSSC\master Configuration Manager Setup
01.04.2015 15:37:05 8980 (0x2314)
Removed SQL alias SRV-SQL.ashipyards.com\MSSC successfully.
Configuration Manager Setup 01.04.2015 15:37:05
8980 (0x2314)
INFO: Registered type SRV-SQL.ASHIPYARDS.COM MSSC\MASTER for SRV-SQL.ashipyards.com MSSC\master
Configuration Manager Setup 01.04.2015 15:37:05
8980 (0x2314)
INFO: Registered type SMS Master for SRV-SQL.ashipyards.com MSSC\master
Configuration Manager Setup 01.04.2015 15:37:05
8980 (0x2314)
INFO: Registered type SRV-SQL.ASHIPYARDS.COM MSSC\SYSTEMCENTERCM_S01 for SRV-SQL.ashipyards.com MSSC\SystemCenterCM_S01
Configuration Manager Setup 01.04.2015 15:37:05
8980 (0x2314)
INFO: Registered type SMS ACCESS for SRV-SQL.ashipyards.com MSSC\SystemCenterCM_S01
Configuration Manager Setup 01.04.2015 15:37:05
8980 (0x2314)
INFO: 'SRV-SCCM.ashipyards.com' is a valid FQDN.
Configuration Manager Setup 01.04.2015 15:37:05
8980 (0x2314)
INFO: Run Site Maintenance on the primary site.
Configuration Manager Setup 01.04.2015 15:37:05
8980 (0x2314)
INFO: Checking for existing setup information.
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
INFO: Setting setup type to 1. Configuration Manager Setup
01.04.2015 15:37:06 8980 (0x2314)
INFO: Checking for existing SQL information.
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
INFO: 'SRV-SQL.ashipyards.com' is a valid FQDN.
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
INFO: Verifying the registry entry for Asset Intelligence installation
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
INFO: Found registry key for installation of Asset Intelligence full version
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
INFO: SDK Provider is on SRV-SCCM.ashipyards.com.
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
INFO: Retrieving current site control image...
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
CSiteSettings::ReadActualSCFFromDatabase: Failed to get sql connection
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
ERROR: Failed to retrieve verifiable site control data
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
INFO: Evaluating for Site Maintenance process.
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
INFO: g_SetupCmdLine.bMoveSql 0, g_SetupCmdLine.sNewSqlServer , g_SetupCmdLine.sNewSqlDatabaseName , pSetupInf->SqlMasterDB MSSC\master.
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:06
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:09
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:09
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:09
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:09
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:12
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:12
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:12
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:12
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:15
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:15
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:15
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:15
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:18
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:18
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:18
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:18
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:21
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:21
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:21
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:21
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:24
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:24
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:24
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:24
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:27
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:27
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:27
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:27
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:30
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:30
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:30
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:30
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:33
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:33
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:33
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:33
8980 (0x2314)
ERROR: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:36
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:36
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:36
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:36
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:36
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:39
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:39
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:39
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:39
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:42
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:42
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:42
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:42
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:45
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:45
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:45
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:45
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:48
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04.2015 15:37:48
8980 (0x2314)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
Configuration Manager Setup 01.04.2015 15:37:48
8980 (0x2314)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
Configuration Manager Setup 01.04.2015 15:37:48
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Configuration Manager Setup 01.04.2015 15:37:51
8980 (0x2314)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
Configuration Manager Setup 01.04. -
SQL Server Developer Edition Licensing
SQL Server 2008 Developer Edition states that it can be used for end client acceptance testing. My question is this.
Does every end client that will be doing testing need to have a license or cal to be able to use the database for testing, or do you only need to buy licenses for the developers that will be developing against it?Each license of SQL Server 2005 Developer Edition entitles one developer to use the software on as many systems as necessary and additional developers can use the software by purchasing additional licenses
Anyway for license related questions, it is better to ask Microsoft Licensing Team directly. You might want to look at these links:
Licensing Question
http://www.microsoft.com/sql/howtobuy/licensing.mspx
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2435258&SiteID=1
Toll free numbers
http://technet.microsoft.com/en-us/subscriptions/bb856399.aspx
Thanks,
Leks
Maybe you are looking for
-
ICloud will not sync contacts and calendar events from my iPhone to my macbook pro.
Only a few contacts are displayed on my Macbook and no calendar events are displayed. Any suggestions?
-
Span columns problem with Table of Contents order
Hello, I'm having a strange issue with headings that span columns and Table of contents order. My document has a heading paragraph in a coloured box, which is then inserted in-line into a 2-column text box. The paragraph style for the box (set to in-
-
How to place a pdf form online?
I created a new pdf form with all the necessary field but when i uploaded it online, I could not write anything in the form fiels or tick a box
-
Problem upgrading to a new version of WCS
Hi, I'm currently trying to upgrade my wcs from version 5.1.64.0 to 6.0.181.0. but every time i run the installation file it tells me that there are multiple copies of the WCS installed on the server and i can't upgrade i can only start a new install
-
I need some help! I admit, I'm not a java guru...far from it, just a college student with a book that doesn't have many examples for what I'm looking for. Any help will be greatly appreciated!!! My problem: My java program is to find a root using the