Hi

I have 2 server (2 diffrent Application) having Database Instance Collation as Japanese_CI_AS (Server#1) Japanese_BIN (Server#2). I want to move database from server#2 to Server#1 by backup and restore. In That case Server#1 instance Collation will be Japanese_CI_AS. but newly moved database collation will be Japanese_BIN. Actually its bascially requirement for both application to have diffrentDatabase Collation. Now my question are. 1. Is there any issue in above approach w.r.t SQL Server DBA point of view. 2. Is there any issue with Applicvation functions.  Although there will be test period but better to know openion in advance.

Detail:

(01) 2017-10-19 02:14:41 Slp: Log provider 'Microsoft.SqlServer.Chainer.Infrastructure.LogProviderFile' has been registered
(01) 2017-10-19 02:14:41 Slp: Log provider 'Microsoft.SqlServer.Chainer.Infrastructure.LogProviderConsole' has been registered
(01) 2017-10-19 02:14:41 Slp: Log provider 'Microsoft.SqlServer.Chainer.Infrastructure.LogProviderStatus' has been registered
(01) 2017-10-19 02:14:41 Slp: Reading XML resource 'Microsoft.SQL.Chainer.PackageData.Package.xml'
(01) 2017-10-19 02:14:41 Slp: Reading schema resource 'Microsoft.SQL.Chainer.Package.Package.xsd'
(01) 2017-10-19 02:14:41 Slp: Document 'Microsoft.SQL.Chainer.PackageData.Package.xml' validated with schema 'Microsoft.SQL.Chainer.Package.Package.xsd' has been successfuly loaded into datastore path '/Datastore/Package'
(01) 2017-10-19 02:14:41 Slp: ----------------------------------------------------------------------
(01) 2017-10-19 02:14:41 Slp: Running Action: ReadProductXML
(01) 2017-10-19 02:14:41 Slp: Reading XML resource 'Microsoft.SQL.Chainer.Product.Product.xml'
(01) 2017-10-19 02:14:41 Slp: Document 'Microsoft.SQL.Chainer.Product.Product.xml' validated with schema 'Microsoft.SQL.Chainer.Product.Product.xsd' has been successfuly loaded into datastore path '/Datastore/Product'
(01) 2017-10-19 02:14:41 Slp: Completed Action: ReadProductXML, returned True
(01) 2017-10-19 02:14:41 Slp: ----------------------------------------------------------------------
(01) 2017-10-19 02:14:41 Slp: Running Action: LoadExtensions
(01) 2017-10-19 02:14:42 Slp: Loading extension 'MSI' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.MsiExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'MSI' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'Config' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.ConfigExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'Config' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'Common' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Chainer.ExtensionCommon.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'Common' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'SqlConfigBase' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.SqlConfigBase.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'SqlConfigBase' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'Slp' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.SetupExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'Slp' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'RulesEngine' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.RulesEngineExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'RulesEngine' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'WorkflowData' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Chainer.WorkflowData.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'WorkflowData' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'SlpConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.SlpExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'SlpConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'Clst' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.Cluster.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'Clst' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'AgentConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.AgentExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'AgentConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'SqlPowershellConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.PowershellExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'SqlPowershellConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'SSISConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.SSISExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'SSISConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'ISMasterConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.ISMasterExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'ISMasterConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'ISWorkerConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.ISWorkerExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'ISWorkerConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'DReplayConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.DistributedReplayExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'DReplayConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'ASConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.ASExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'ASConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'ReplConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.Repl_ConfigExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'ReplConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'ManagementToolsConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.ManagementToolsExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'ManagementToolsConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'ManagementToolsAdvancedConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.ManagementToolsExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'ManagementToolsAdvancedConfig' version '14.0.1000.169' loaded

The 'SSBDT' entries into our SQL Errorlog did not occur in version 12.0.5207 however, they are flooding our 12.0.6024 instances daily by the thousands.

I see no one has replied on this thread for a while; plus there are only a few mentions of this problem when I search. Is there an answer found for this yet?

Hi all,

I'm trying to uninstall sql 2005 CTP, so that I can install the standard version... but I keep on getting a whole range of errors.... I can't uninstall the ctp, and I can't upgrade with the standard version...

 This is the errorcode I got

TITLE: Microsoft SQL Server 2005 Setup
------------------------------

The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation.

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.06&EvtSrc=setup.rll&EvtID=1603&EvtType=sqlca%5csqlcax.cpp%40SetInstanceProperty%40SetInstanceProperty%40x534

------------------------------
BUTTONS:

OK
------------------------------

Any Ideas?

When I try to install Sql server 2008 R2 in my windows 10 then show below message:-

SQL Server setup media does not support the language of the OS or does not have ENU localized files. Use the matching language-specific SQL Server media or change theOS locale through control panel.

Please tell me how do i fix it. 

CU 14 failed to install database engine service update. Browser, writer and support files are OK. What can I do?

Hi Team,

I am trying automate sql 2012 installation from linux remote machine & have followed below steps

1- Created new Local windows user ( other than Local administrator ) & added same in administrators Group for sql installation

2- Created ConfigurationFile.ini

3- Created the powershell script called sql-installation.ps1 with command to execute the SQL installation ---- > & D:\setup.exe /configurationfile="C:\configurationfile.ini" 

4- then executing this powershell from linux machine but i am getting below errror in summery log file,

Need help to resolve this issue.

Thanks

NM-BG

I am planning to upgrade SQL Server Management Studio (SSMS) from version 12 to the latest version 17.9.1 on my workstation. I've downloaded the SSMS 17.9.1 installer from the below URL of Microsoft web site.

Download SQL Server Management Studio (SSMS)

Could you advise me a couple of questions on the upgrade process, please?

Here is information of my environment.

---------------------------

<OS of workstation where SSMS is installed>

     Windows 10 Enterprise

<Version of SQL Server that the SSMN connect to>

     SQL Server 2014 SP1 Enterprise

----------------------------

(1) Currently old version 12 of SSMS is installed on my workstation. Should I uninstall ver 12 at first, then install the latest version 17.9.1? or is there any way to upgrade from 12 to 17.9.1?

(2) If it is right procedure to uninstall old one then install the latest one, is there any step required to take over the current configuration to the latest version before uninstall the old version? It is my understanding that SSMS is just GUI tool to operate as connecting to SQL Sever, so all current configuration are on SQL Server application, not on SSMS itself. (Please correct me if I was wrong.)

(3) Which OS and SQL Server version are compatible for the latest SSMS version 17.9.1?

Any advise will be gratefully appreciate it. Thank you..

Hello,

I'm working with a SCVMM 2016 server that has SQL 2016 installed on the same system.  Everything at the OS and SCVMM level patches no problem and is fully up to date.  However, I can't apply the SQL SP 2 CU update.  Either CU2 or CU6.  Any thoughts would be appreicated. Below are the logs and what all I have tried.

Thanks,
Brad

When I try updating:
An error occurred for a dependency of the feature causing the setup process for the feature to fail.

Error installing SQL Server Common Files
The upgrade cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade.
Error code: 1642
Log file: C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20190420_133826\MSSQLSERVER\sql_common_core_Cpu64_1.log
Visit http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.5292.0&EvtType=sql_common_core.msi%400x162A16FE%400x1642 to get help on troubleshooting.

In the log file:
Overall summary:
  Final result:                  The patch installer has failed to update the following instance: MSSQLSERVER. To determine the reason for failure, review the log files.
  Exit code (Decimal):           -2068052374
  Start time:                    2019-04-20 13:38:31
  End time:                      2019-04-20 13:40:58
  Requested action:              Patch

Instance MSSQLSERVER overall summary:
  Final result:                  The patch installer has failed to update the shared features. To determine the reason for failure, review the log files.
  Exit code (Decimal):           -2068052374
  Start time:                    2019-04-20 13:40:16
  End time:                      2019-04-20 13:40:51
  Requested action:              Patch

Machine Properties:
  Machine name:                  VMM01
  Machine processor count:       4
  OS version:                    Microsoft Windows Server 2016 Standard (10.0.14393)
  OS service pack:               
  OS region:                     United States
  OS language:                   English (United States)
  OS architecture:               x64
  Process architecture:          64 Bit
  OS clustered:                  No

Product features discovered:
  Product              Instance             Instance ID                    Feature                                  Language             Edition              Version         Clustered  Configured
  SQL Server 2016      MSSQLSERVER          MSSQL13.VMM01                  Database Engine Services                 1033                 Standard Edition     13.2.5149.0     No         Yes      
  SQL Server 2016                                                          SSMS                                     1033                                      13.0.15000.23   No         Yes       
  SQL Server 2016                                                          Client Tools Connectivity                1033                                      13.0.14500.10   No         Yes       
  SQL Server 2016                                                          Client Tools Backwards Compatibility     1033                                      13.0.14500.10   No         Yes       
  SQL Server 2016                                                          Client Tools SDK                         1033                                      13.0.14500.10   No         Yes       

Package properties:
  Description:                   Microsoft SQL Server 2016
  ProductName:                   SQL Server 2016
  Type:                          RTM
  Version:                       13
  SPLevel:                       2
  KBArticle:                     KB4488536
  KBArticleHyperlink:            http://support.microsoft.com/?kbid=4488536
  PatchType:                     QFE
  AssociatedHotfixBuild:         0
  Platform:                      x64
  PatchLevel:                    13.2.5292.0
  ProductVersion:                13.2.5026.0
  GDRReservedRange:              13.0.1700.0:13.0.1899.0;13.0.4200.0:13.0.4299.0;13.0.5200.0:13.0.5399.0
  Installation location:         F:\abd9fbad1f3b07b00aec0137\x64\setup\

Updated product edition:
  Instance             Edition             
  MSSQLSERVER          Standard            

User Input Settings:
  ACTION:                        Patch
  ALLINSTANCES:                  false
  CLUSTERPASSIVE:                false
  CONFIGURATIONFILE:             
  ENU:                           true
  HELP:                          false
  IACCEPTROPENLICENSETERMS:      false
  IACCEPTSQLSERVERLICENSETERMS:  true
  INDICATEPROGRESS:              false
  INSTANCEID:                    <empty>
  INSTANCENAME:                  <empty>
  MRCACHEDIRECTORY:              
  QUIET:                         false
  QUIETSIMPLE:                   false
  SUPPRESSPRIVACYSTATEMENTNOTICE: false
  UIMODE:                        Normal
  X86:                           false

Rules with failures:

Global rules:

There are no scenario-specific rules.

Rules report file:               C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20190420_133826\SystemConfigurationCheck_Report.htm

• Rebooting
• Installing from the WSUS server
• Installing from the standalone package (SQLServer2016-KB4488536-x64.exe).
• I tried the repair process outline in this MS article that poined to this MS article. Everything passed with no problems during the repair.

So I've hit a bit of a confusing issue. We have a pair of servers, that run Backup Exec. They were running an older version that used SQL 2008 Express. We upgraded it to SQL 2012 Express SP3 a while back. Along the way, someone else had installed a separate version of SQL 2017-RC1 (full, not express).

Fast forward and we're upgrading to a new Backup Exec that uses SQL 2014 express SP2. For whatever reasons the SQL 2014 install would fail. Since the other SQLs were not important, we removed all the previous SQL installs, along with Backup Exec. So on paper the system is clean of SQL.

Now when trying to install any SQL higher than 2008, whether 2012, 2014 or even 2017. I get stuck on the screen that says "Please wait while Microsoft SQL Server 201x setup processes the current operation" and it just sits there forever (and by forever, I've left it for over 24 hours). I've ran Windows updates, stripped out as much older software as possible, but none of those 3 versions will install. Oddly (or maybe not) version 2008 express will still install, but I can not upgrade to a newer version, it will again just sit and hang at the please wait screen.

Not sure where the error is at, but any insight would be appreciated. 

On attempting to install SQL Server 2008/R2 following a terminated install, the first screen I get is this one.



I select New Installation.  This is followed by the Licence Terms screen in which I accept the terms.

After this screen, instead of the screen where I get to select my options, I get the first screen again and it's forever in that loop until I decide to exit.  There is no message giving me a failed install.  Can anyone assist me?  I believe the registry has got itself tangled up.

The thing I'm thinking at the moment is having a completely rebuilt laptop.

Thank you in advance.

Good day,

Please bear with me i'm not clued up with the licensing etc

Currently have newly installed VM Windows 2016 with SQL Server2016 Standard Edition 64 Bit & VS2017 Community (SSDT) with 23GB  RAM.

I know the RAM is not great but I cant get more, I was told that I can upgrade the Standard edition to Enterprise as we have a Standard license, something about having multiple vm on same host the company is eligible 1 Premium License Key

Now I'm not clued up and they not giving me funds and before I try to download or Install Premium how do I go about it

Would my standard key work on premium?

I tried from standard iso to do Maintenance - Upgrade, but it only upgrades the Standard updates available and not to Premium > If I can get Key how do I change the version?

Please help

regards

I need to know the best way to determine when it's time to buy more user license for SQL.  Is there a monitor in the SLQ Server Management Studio that will tell me show me owned license compared to consumed license?

Thank you in advance for your responses.

Chad

Hi,

I am upgrading my SQL Server 2005 database to SQL Server 2016 so I am trying to use backup and restore. 
So I have created stop point to SQL Server 2008 SP2 where I am going to restore my database at 2008 box, upgrade it and move to 2016

Now when I try to restore database from SQL Server 2005 to SQL Server 2008 SP2 I am getting error.

Msg 3241, Level 16, State 0, Line 6
The media family on device 'c:\temp\backupname.bak' is incorrectly formed. SQL Server cannot process this media family.
Msg 3013, Level 16, State 1, Line 6
VERIFY DATABASE is terminating abnormally.

I have checked all possibility 

• I have access to location
• I am able to restore database SQL 2005.
• I have check version I am moving database from Enterprise to Enterprise

Please help me

Retiring a server w/sql 2008 r2. New will have sql 2017. MS tells me the cals in the 2008 sql are "not compatible", even if I buy the 2017 edition that uses cals rather than cores. They're just licenses for Pete's sake. Seems like straight up "we just want more money". makes as much sense as saying if I buy a new car I'd have to abandon my driveway and build a new one. Anybody know of any real reason other than just to get more money?

Hi

We need to have testing/dev environment to behave exactly like production one.

Is it possible to configure SQL Server 2017 dev edition to behave like Standard one? (in terms of cpu/threads usage etc)

Thank you

Hello,

I have recently installed the CU14 for SQL Server 2016 SP1 from the following URL:

https://support.microsoft.com/en-us/help/3177312/sql-server-2016-build-versions

However, the update was installed with some errors, due to which it was observed that the MSSQLSERVER service could not be started. As a result, I decided to uninstall the update from Control Panel. The update could be uninstalled successfully and the MSSQLSERVER service became functional as before. In order to attain surety of my action, I considered reinstalling the update, but got the same results - inability to start the SQL Serer (MSSQLSERVER) service. This time, the update could not be uninstalled completely even on several attempts, and my SQL Server service remains dysfunctional. A zipped file of the logs of all the actions can be accessed here:

https://drive.google.com/open?id=1j4SLaFEVal-1ths4TC3Q_KBBCslbeVtQ

Kindly help me get my SQL Server service up and running at the earliest.

Thank you.

I am a BI person so I can use a DB, but setting up and configuring - not so much (last time I created a DB was DB2 UDB on NT). I'm learning but looking for aquick start if anyone can help:

I have SS 2017 Express installed on a machine on my network. I need to grant other users on the same domain access to this instance. What is the quickest way to configure this?

Thanks.