Quantcast
Channel: SQL Server Setup & Upgrade forum
Viewing all 7696 articles
Browse latest View live

[SQL Server 2014] Processor usage (with stored procedure)

$
0
0

Hi,

I'm not sure about my question's category, but, as it's probably a configuration issue, I think "SQL Server Setup" is ok.

I have a SQL Server 2014 Std on a virtual Machine (Server 2012R2 / Hyper-V 3).

I've got a huge stored procedure called from another server.

Each time the procedure was called, the processor's load reached 100% usage, and of course, my procedure was very slow.

I tried to add virtual processor to my VM (from 1 virtual processor to 4).

When I look into the task manager, my stored procedure doesn't take 100% of my processor but I don't feel any gain in performance.

When I look into performance monitor, I can see % time processor and % time user reach 25% as soon as I call my stored procedure

My guess is that only one of my 4 virtual processor is used to execute this request.

My SQL Server has pretty much a default configuration.

Do you have any idea (if you think I'm right about my problem) how to share the load of this request to my 4 virtual processor?

If you think I'm wrong, can you think about anything that could help me ?

Best Regards,


Help Viewer 1.1 repair after SQL 2014 installation

$
0
0

I am seeking assistance installing or repairing HelpViewer 1.1 installed with SQL Server 2014. 

I receive the following error when choosing “I want to use local settings” option from Help Library Manager,

This page can’t be displayed

  • Make sure the web address http://127.0.0.1:47873 is correct
  • Look for the page with your search engine
  • Refresh the page in a few minutes

I attempted repairing the help viewer by executing the installation file found at

C:\Program Files\Microsoft Help Viewer\v1.0\Microsoft Help Viewer 1.1\install.exe

and choosing the REPAIR option.  The repair function completes; however, the error remains.

I examined the SQL 2014 installation disc and found nothing useful under the Maintenance/ Repair topic. I really do not look forward to a complete reinstall of SQL server and components so I may use local help files.

Please, anyone with insight or suggestions, I am happy the hear from you.

Thanks



SQL Server 2014 service wont start start after updating sp1 (KB3058865, KB3075950, KB3094221)

$
0
0

Hi, my SQL Server 2014 is working fine in my server with WIndows 2012 until I installed new updates & service pack that was required for server hardening. 

I installed successfully SP1 KB 3058865 first then found out that the services wont start. After so many research for fix, i came with the 2 cu updates KB3075950, KB3094221 knowing that this could solve my problem but unfortunately its not.

I also tried changing the account of the services that many would suggest but its not working.

I tried replacing the master & maslog file but also failed.

I tried running it in single usermode and restore master db and etc.. also failed.

heres the log file:

016-02-01 15:21:21.83 Server      Microsoft SQL Server 2014 (SP1-CU3) (KB3094221) - 12.0.4427.24 (X64) 
Oct 10 2015 17:18:26 
Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: ) (Hypervisor)

2016-02-01 15:21:21.84 Server      UTC adjustment: 8:00
2016-02-01 15:21:21.84 Server      (c) Microsoft Corporation.
2016-02-01 15:21:21.84 Server      All rights reserved.
2016-02-01 15:21:21.84 Server      Server process ID is 5128.
2016-02-01 15:21:21.86 Server      System Manufacturer: 'Microsoft Corporation', System Model: 'Virtual Machine'.
2016-02-01 15:21:21.86 Server      Authentication mode is MIXED.
2016-02-01 15:21:21.86 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2016-02-01 15:21:21.86 Server      The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required.
2016-02-01 15:21:21.86 Server      Registry startup parameters: 
-d C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2016-02-01 15:21:21.86 Server      Command Line Startup Parameters:
-s "MSSQLSERVER"
2016-02-01 15:21:22.27 Server      SQL Server detected 1 sockets with 1 cores per socket and 1 logical processors per socket, 1 total logical processors; using 1 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2016-02-01 15:21:22.27 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2016-02-01 15:21:22.28 Server      Detected 7999 MB of RAM. This is an informational message; no user action is required.
2016-02-01 15:21:22.28 Server      Using conventional memory in the memory manager.
2016-02-01 15:21:22.33 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2016-02-01 15:21:22.37 Server      This instance of SQL Server last reported using a process ID of 1600 at 2/1/2016 3:13:12 PM (local) 2/1/2016 7:13:12 AM (UTC). This is an informational message only; no user action is required.
2016-02-01 15:21:22.38 Server      The maximum number of dedicated administrator connections for this instance is '1'
2016-02-01 15:21:22.38 Server      Node configuration: node 0: CPU mask: 0x0000000000000001:0 Active CPU mask: 0x0000000000000001:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2016-02-01 15:21:22.40 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.
2016-02-01 15:21:22.43 spid8s      Starting up database 'master'.
2016-02-01 15:21:22.49 Server      CLR version v4.0.30319 loaded.
2016-02-01 15:21:22.51 spid8s      8 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2016-02-01 15:21:22.61 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2016-02-01 15:21:22.62 spid8s      0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2016-02-01 15:21:22.62 spid8s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2016-02-01 15:21:22.79 spid8s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2016-02-01 15:21:22.80 spid8s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
2016-02-01 15:21:22.88 spid8s      SQL Trace ID 1 was started by login "sa".
2016-02-01 15:21:23.28 spid8s      Server name is 'UATCASADB'. This is an informational message only. No user action is required.
2016-02-01 15:21:23.28 spid13s     A self-generated certificate was successfully loaded for encryption.
2016-02-01 15:21:23.33 spid13s     Server is listening on [ 'any' <ipv6> 1433].
2016-02-01 15:21:23.40 spid13s     Server is listening on [ 'any' <ipv4> 1433].
2016-02-01 15:21:23.44 spid13s     Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2016-02-01 15:21:23.44 spid13s     Server local connection provider is ready to accept connection on [ \\.\pipe\sql\query ].
2016-02-01 15:21:23.48 Server      Server is listening on [ ::1 <ipv6> 1434].
2016-02-01 15:21:23.49 Server      Server is listening on [ 127.0.0.1 <ipv4> 1434].
2016-02-01 15:21:23.49 Server      Dedicated admin connection support was established for listening locally on port 1434.
2016-02-01 15:21:23.49 Server      SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
2016-02-01 15:21:23.60 spid14s     A new instance of the full-text filter daemon host process has been successfully started.
2016-02-01 15:21:23.71 Server      The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/UATCASADB.onenetworkbank.com.ph ] for the SQL Server service.
2016-02-01 15:21:23.72 Server      The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/UATCASADB.onenetworkbank.com.ph:1433 ] for the SQL Server service.
2016-02-01 15:21:23.97 spid17s     Starting up database 'msdb'.
2016-02-01 15:21:23.98 spid18s     Starting up database 'ReportServer'.
2016-02-01 15:21:23.98 spid19s     Starting up database 'ReportServerTempDB'.
2016-02-01 15:21:24.03 spid9s      Starting up database 'mssqlsystemresource'.
2016-02-01 15:21:24.08 spid9s      The resource database build version is 12.00.4427. This is an informational message only. No user action is required.
2016-02-01 15:21:24.11 Logon       Error: 18401, Severity: 14, State: 1.
2016-02-01 15:21:24.11 Logon       Login failed for user 'NT SERVICE\ReportServer'. Reason: Server is in script upgrade mode. Only administrator can connect at this time. [CLIENT: <local machine>]
2016-02-01 15:21:24.18 spid19s     1 transactions rolled forward in database 'ReportServerTempDB' (6:0). This is an informational message only. No user action is required.
2016-02-01 15:21:24.28 spid19s     0 transactions rolled back in database 'ReportServerTempDB' (6:0). This is an informational message only. No user action is required.
2016-02-01 15:21:24.44 spid17s     133 transactions rolled forward in database 'msdb' (4:0). This is an informational message only. No user action is required.
2016-02-01 15:21:24.73 spid17s     0 transactions rolled back in database 'msdb' (4:0). This is an informational message only. No user action is required.
2016-02-01 15:21:24.74 spid17s     Recovery is writing a checkpoint in database 'msdb' (4). This is an informational message only. No user action is required.
2016-02-01 15:21:24.79 spid9s      Starting up database 'model'.
2016-02-01 15:21:25.01 spid9s      Clearing tempdb database.
2016-02-01 15:21:25.94 spid9s      Starting up database 'tempdb'.
2016-02-01 15:21:26.12 spid20s     The Service Broker endpoint is in disabled or stopped state.
2016-02-01 15:21:26.12 spid20s     The Database Mirroring endpoint is in disabled or stopped state.
2016-02-01 15:21:26.15 spid20s     Service Broker manager has started.
2016-02-01 15:21:27.32 spid8s      Database 'master' is upgrading script 'msdb110_upgrade.sql' from level 201328592 to level 201331019.
2016-02-01 15:21:27.32 spid8s      ----------------------------------
2016-02-01 15:21:27.32 spid8s      Starting execution of PRE_MSDB.SQL
2016-02-01 15:21:27.32 spid8s      ----------------------------------
2016-02-01 15:21:28.36 spid8s      Setting database option COMPATIBILITY_LEVEL to 100 for database 'msdb'.
2016-02-01 15:21:28.56 spid8s      -----------------------------------------
2016-02-01 15:21:28.56 spid8s      Starting execution of PRE_SQLAGENT100.SQL
2016-02-01 15:21:28.56 spid8s      -----------------------------------------
2016-02-01 15:21:28.60 spid8s      Setting database option COMPATIBILITY_LEVEL to 120 for database 'msdb'.
2016-02-01 15:21:28.77 spid8s      Configuration option 'allow updates' changed from 1 to 1. Run the RECONFIGURE statement to install.
2016-02-01 15:21:28.77 spid8s      Configuration option 'allow updates' changed from 1 to 1. Run the RECONFIGURE statement to install.
2016-02-01 15:21:29.18 Logon       Error: 18401, Severity: 14, State: 1.
2016-02-01 15:21:29.18 Logon       Login failed for user 'NT SERVICE\ReportServer'. Reason: Server is in script upgrade mode. Only administrator can connect at this time. [CLIENT: <local machine>]
2016-02-01 15:21:31.84 spid8s      Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2016-02-01 15:21:31.86 spid8s      Using 'xpstar.dll' version '2014.120.4100' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2016-02-01 15:21:31.89 spid8s      DBCC TRACEOFF 1717, server process ID (SPID) 8. This is an informational message only; no user action is required.
2016-02-01 15:21:31.89 spid8s      DBCC execution completed. If DBCC printed error messages, contact your system administrator.
2016-02-01 15:21:31.90 spid8s       
2016-02-01 15:21:31.90 spid8s      Creating table temp_sysjobschedules
2016-02-01 15:21:32.20 spid8s       
2016-02-01 15:21:32.20 spid8s      Alter table sysdownloadlist...
2016-02-01 15:21:32.22 spid8s       
2016-02-01 15:21:32.22 spid8s      Alter table sysjobhistory...
2016-02-01 15:21:32.24 spid8s       
2016-02-01 15:21:32.24 spid8s      Alter table systargetservers...
2016-02-01 15:21:32.25 spid8s       
2016-02-01 15:21:32.25 spid8s      Alter table sysjobsteps...
2016-02-01 15:21:32.40 spid8s      Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install.
2016-02-01 15:21:32.40 spid8s      Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install.
2016-02-01 15:21:32.42 spid8s       
2016-02-01 15:21:32.42 spid8s      -----------------------------------------
2016-02-01 15:21:32.42 spid8s      Execution of PRE_SQLAGENT100.SQL complete
2016-02-01 15:21:32.42 spid8s      -----------------------------------------
2016-02-01 15:21:32.46 spid8s      DMF pre-upgrade steps...
2016-02-01 15:21:32.83 spid8s      DC pre-upgrade steps...
2016-02-01 15:21:32.83 spid8s      Check if Data collector config table exists...
2016-02-01 15:21:32.84 spid8s      Data Collector state before upgrade: 0
2016-02-01 15:21:32.84 spid8s      pre_dc100::Check if syscollector_collection_sets_internal table exists...
2016-02-01 15:21:32.84 spid8s      pre_dc100::Capturing Collection set status in temp table...
2016-02-01 15:21:33.05 spid8s      Deleting cached auto-generated T-SQL Data Collection packages from msdb...
2016-02-01 15:21:33.05 spid8s      End of DC pre-upgrade steps.
2016-02-01 15:21:33.05 spid8s      DAC pre-upgrade steps...
2016-02-01 15:21:33.06 spid8s      Starting DAC pre-upgrade steps ...
2016-02-01 15:21:33.06 spid8s      End of DAC pre-upgrade steps.
2016-02-01 15:21:33.06 spid8s      ----------------------------------
2016-02-01 15:21:33.06 spid8s      Starting execution of MSDB.SQL
2016-02-01 15:21:33.06 spid8s      ----------------------------------
2016-02-01 15:21:33.19 spid8s      Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
2016-02-01 15:21:33.19 spid8s      Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
2016-02-01 15:21:33.37 spid8s      Checking the size of MSDB...
2016-02-01 15:21:33.63 spid8s      Error: 8966, Severity: 16, State: 2.
2016-02-01 15:21:33.63 spid8s      Unable to read and latch page (1:56616) with latch type SH. Invalid page ID. failed.
2016-02-01 15:21:33.63 spid8s      Error: 8946, Severity: 16, State: 12.
2016-02-01 15:21:33.63 spid8s      Table error: Allocation page (1:56616) has invalid PFS_PAGE page header values. Type is 0. Check type, alloc unit ID and page ID on the page.
2016-02-01 15:21:33.63 spid8s      Error: 912, Severity: 21, State: 2.
2016-02-01 15:21:33.63 spid8s      Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 3601, state 5, severity 25. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
2016-02-01 15:21:33.64 spid8s      Error: 3417, Severity: 21, State: 3.
2016-02-01 15:21:33.64 spid8s      Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
2016-02-01 15:21:33.64 spid8s      SQL Server shutdown has been initiated
2016-02-01 15:21:33.64 spid8s      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
2016-02-01 15:21:34.70 spid8s      Error: 25725, Severity: 16, State: 1.
2016-02-01 15:21:34.70 spid8s      An error occurred while trying to flush all running Extended Event sessions.  Some events may be lost.
2016-02-01 15:21:34.71 spid13s     The SQL Server Network Interface library could not deregister the Service Principal Name (SPN) [ MSSQLSvc/UATCASADB.onenetworkbank.com.ph ] for the SQL Server service. Error: 0x2af9, state: 61. Administrator should deregister this SPN manually to avoid client authentication errors.
2016-02-01 15:21:34.71 spid13s     The SQL Server Network Interface library could not deregister the Service Principal Name (SPN) [ MSSQLSvc/UATCASADB.onenetworkbank.com.ph:1433 ] for the SQL Server service. Error: 0x2af9, state: 61. Administrator should deregister this SPN manually to avoid client authentication errors.

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

I would appreciate every help i can get. Thanks.

MS SQL restore missing data

$
0
0

Hi,

I have a database on DEV that I restored six months ago and now I would like to update with data from PROD.What will be best way to do it ?

I assume that i should use restore FULL on existing DEV database? Can someone describe mi full process, please?

Kind Regards,

M



SQL Server 2012 SP3 Extraction Fails

$
0
0

Hi,

I just did a new install of SQL Server 2012 Standard with SP2 (64 bit). I downloaded SP3 from Microsoft and when I install it during the extraction process get error "Extraction Failed: The operation was cancelled by the user".

I rebooted tried it again and it failed. I downloaded it again and the install had the same result.

Thanks in advance!

Recomended Instance Root Dir

$
0
0

Hello!

I´ve got a simple question about the sql server installation process. (SQL Server 2012 / 2014)

Is it recomemded to change the "instance root directory" to another drive than c:\ ?

It´s clear to seperate the data-files from c:\ - but when I change the "instance root directory",

then the Binaries from SQL Server move to that drive.

Thanx in advance!

Greetings

Karsten

Extended ASCII Settings

$
0
0

We have an sql server 2008 database that has been in service for nearly 3 years.  The users of the database are in the states.  Recently, we received some company name data that contained extended ASCII characters, such as, Ç (0xc7), Ã (0xc3), '.' (0xa0).  The database mangled the characters, including increasing the number of bytes.

What are the best practices for handling the extended ASCII?  Should they be converted to something close in regular ASCII, like C and A in the above example?  Or is there a setting that enables sql server to treat these extended characters correctly. If it's a setting, is it safe to apply and what is the best way to apply the steps.

Database Error When Running WordPress Site in Visual Studio

$
0
0

I've been trying to test/run/debug an existing Wordpress Site(which I didn't create) with Visual Studio for the last few days. I have added the php extensions. The debugger started working once I had added beta 8. However, I still can't run the site locally on my computer. 

As suggested by the php extension people, I downloaded mySQL. They suggested that I use a local version of mySQL for developing purposes instead of using the one that is on the live website. I then changed the wp-config.php file name in the hopes that this would force visual studio to reconfigure the WordPress site. No such luck. 

I added MySQL as a data source within the "Server Explorer" panel. I can see my computer as the server. I also added Message Queuing (MSMQ) as that had a red X next to it within the server's panel and from forums online, it seemed like this had something to do with passing data. There is no red X, but I still can't run the website locally. 

Right now, when I try to run the website in the browser, I get the words: Error Establishing a Database Connection. I can finally see the favicon in the browser, but I have no idea how it got there or why nothing else is showing up. 

If anyone could help me, I would really appreciate it. This is driving me crazy. 

Thanks,

Kelsey



Installing updates to SQL Server stops

$
0
0

Hi,

I have SQL 2012 on Server 2008 R2.  When running a security patch for SQL on it, the progress meter shows that files are being extracted. The files are extracted and a shell pops up for a second and then closes.  After that, the temporary files are deleted and nothing further happens.  There are no entries in the 110/setup bootstrap/logs folder.  Any ideas on where to look or what to try?  I ran a repair on the install and same behavior.

Thanks

Storage Server Changes To SQL2k5 User Databases

$
0
0

Hello,

We currently have a user database with the combined size of (including filegroups) of about 1.8 tb. SQL2k15 version. We want to first migrate the storage location to a new faster storage hardware before deciding to upgrade the SQL server version to SQL2k14. Here are my questions:

1. Our management wants to simply by consolidating the filegroups (15 total) into one .mdf file thinking that the higher performing new storage will compensate for performance degrading due to combination of filegroups into one .mdf file. Can this be done and if so, steps please. Of course, we will maintain separate drives for tempdb, templog, transaction logs and data (mdf) files. Basically, the goal is to take out the multiple filegroups.

2. Can we reduce the number of filegroups into say 5 instead of 15 (still allocate different drives) and if so, how can we merge some of the filegroups? Again, steps please.

Will greatly appreciate your early response.

Thanks.

Victor



VR3357

SQL server 2014 Install error: Missing dll

$
0
0

Hi everybody,

I am trying to install SQL Server 2014 on windows 10. Once the installer wizard starts installing, I get the following message:

There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.

I have already searched the web and tried every solution I could find (running as administator, changing the permissions for certain folders and re-installing). Any suggestions are welcome.

The last install log reports the following:

Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2068052293
  Start time:                    2016-02-03 12:50:30
  End time:                      2016-02-03 12:52:43
  Requested action:              Install

Setup completed with required actions for features.
Troubleshooting information for those features:
  Next step for Adv_SSMS:        Use the following information to resolve the error, and then try the setup process again.
  Next step for Conn:            Use the following information to resolve the error, and then try the setup process again.
  Next step for SDK:             Use the following information to resolve the error, and then try the setup process again.
  Next step for BC:              Use the following information to resolve the error, and then try the setup process again.
  Next step for SSMS:            Use the following information to resolve the error, and then try the setup process again.
  Next step for SQLEngine:       Use the following information to resolve the error, and then try the setup process again.
  Next step for Replication:     Use the following information to resolve the error, and then try the setup process again.
  Next step for SNAC:            Use the following information to resolve the error, and then try the setup process again.
  Next step for SNAC_SDK:        Use the following information to resolve the error, and then try the setup process again.


Machine Properties:
  Machine name:                  MELCHIOR
  Machine processor count:       8
  OS version:                    Windows 8
  OS service pack:               
  OS region:                     United States
  OS language:                   Nederlands (Nederland)
  OS architecture:               x64
  Process architecture:          64 Bit
  OS clustered:                  No

Product features discovered:
  Product              Instance             Instance ID                    Feature                                 Language             Edition              Version         Clustered  Configured

Package properties:
  Description:                   Microsoft SQL Server 2014 
  ProductName:                   SQL Server 2014
  Type:                          RTM
  Version:                       12
  SPLevel:                       0
  Installation location:         C:\Users\melchior\Documents\SQLEXPRWT_x64_ENU\x64\setup\
  Installation edition:          Express

Product Update Status:
  None discovered.

User Input Settings:
  ACTION:                        Install
  ADDCURRENTUSERASSQLADMIN:      true
  AGTSVCACCOUNT:                 NT AUTHORITY\NETWORK SERVICE
  AGTSVCPASSWORD:                *****
  AGTSVCSTARTUPTYPE:             Disabled
  ASBACKUPDIR:                   Backup
  ASCOLLATION:                   Latin1_General_CI_AS
  ASCONFIGDIR:                   Config
  ASDATADIR:                     Data
  ASLOGDIR:                      Log
  ASPROVIDERMSOLAP:              1
  ASSERVERMODE:                  MULTIDIMENSIONAL
  ASSVCACCOUNT:                  <empty>
  ASSVCPASSWORD:                 <empty>
  ASSVCSTARTUPTYPE:              Automatic
  ASSYSADMINACCOUNTS:            <empty>
  ASTEMPDIR:                     Temp
  BROWSERSVCSTARTUPTYPE:         Disabled
  CLTCTLRNAME:                   <empty>
  CLTRESULTDIR:                  <empty>
  CLTSTARTUPTYPE:                0
  CLTSVCACCOUNT:                 <empty>
  CLTSVCPASSWORD:                <empty>
  CLTWORKINGDIR:                 <empty>
  COMMFABRICENCRYPTION:          0
  COMMFABRICNETWORKLEVEL:        0
  COMMFABRICPORT:                0
  CONFIGURATIONFILE:             
  CTLRSTARTUPTYPE:               0
  CTLRSVCACCOUNT:                <empty>
  CTLRSVCPASSWORD:               <empty>
  CTLRUSERS:                     <empty>
  ENABLERANU:                    true
  ENU:                           true
  ERRORREPORTING:                false
  FEATURES:                      SQLENGINE, REPLICATION, CONN, BC, SDK, SSMS, ADV_SSMS, SNAC_SDK
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  <empty>
  FTSVCPASSWORD:                 <empty>
  HELP:                          false
  IACCEPTSQLSERVERLICENSETERMS:  true
  INDICATEPROGRESS:              false
  INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
  INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
  INSTALLSQLDATADIR:             <empty>
  INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
  INSTANCEID:                    SQLEXPRESS
  INSTANCENAME:                  SQLEXPRESS
  ISSVCACCOUNT:                  NT AUTHORITY\Network Service
  ISSVCPASSWORD:                 <empty>
  ISSVCSTARTUPTYPE:              Automatic
  MATRIXCMBRICKCOMMPORT:         0
  MATRIXCMSERVERNAME:            <empty>
  MATRIXNAME:                    <empty>
  NPENABLED:                     0
  PID:                           *****
  QUIET:                         false
  QUIETSIMPLE:                   false
  ROLE:                          AllFeatures_WithDefaults
  RSINSTALLMODE:                 DefaultNativeMode
  RSSHPINSTALLMODE:              DefaultSharePointMode
  RSSVCACCOUNT:                  <empty>
  RSSVCPASSWORD:                 <empty>
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         <empty>
  SECURITYMODE:                  <empty>
  SQLBACKUPDIR:                  <empty>
  SQLCOLLATION:                  Latin1_General_CI_AS
  SQLSVCACCOUNT:                 NT Service\MSSQL$SQLEXPRESS
  SQLSVCPASSWORD:                <empty>
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           MELCHIOR\melchior
  SQLTEMPDBDIR:                  <empty>
  SQLTEMPDBLOGDIR:               <empty>
  SQLUSERDBDIR:                  <empty>
  SQLUSERDBLOGDIR:               <empty>
  SQMREPORTING:                  false
  TCPENABLED:                    0
  UIMODE:                        AutoAdvance
  UpdateEnabled:                 true
  UpdateSource:                  MU
  USEMICROSOFTUPDATE:            false
  X86:                           false

  Configuration file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20160203_125029\ConfigurationFile.ini

Detailed results:
  Feature:                       Management Tools - Complete
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server Native Client Access Component
  Component error code:          1723
  Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20160203_125029\sqlncli_Cpu64_1.log
  Error description:             There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sqlncli.msi%40RollbackCleanup%401723

  Feature:                       Client Tools Connectivity
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server Native Client Access Component
  Component error code:          1723
  Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20160203_125029\sqlncli_Cpu64_1.log
  Error description:             There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sqlncli.msi%40RollbackCleanup%401723

  Feature:                       Client Tools SDK
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server Native Client Access Component
  Component error code:          1723
  Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20160203_125029\sqlncli_Cpu64_1.log
  Error description:             There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sqlncli.msi%40RollbackCleanup%401723

  Feature:                       Client Tools Backwards Compatibility
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server Native Client Access Component
  Component error code:          1723
  Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20160203_125029\sqlncli_Cpu64_1.log
  Error description:             There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sqlncli.msi%40RollbackCleanup%401723

  Feature:                       Management Tools - Basic
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server Native Client Access Component
  Component error code:          1723
  Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20160203_125029\sqlncli_Cpu64_1.log
  Error description:             There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sqlncli.msi%40RollbackCleanup%401723

  Feature:                       Database Engine Services
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server Native Client Access Component
  Component error code:          1723
  Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20160203_125029\sqlncli_Cpu64_1.log
  Error description:             There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sqlncli.msi%40RollbackCleanup%401723

  Feature:                       SQL Server Replication
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server Native Client Access Component
  Component error code:          1723
  Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20160203_125029\sqlncli_Cpu64_1.log
  Error description:             There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sqlncli.msi%40RollbackCleanup%401723

  Feature:                       SQL Client Connectivity
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred during the setup process of the feature.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server Native Client Access Component
  Component error code:          1723
  Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20160203_125029\sqlncli_Cpu64_1.log
  Error description:             There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sqlncli.msi%40RollbackCleanup%401723

  Feature:                       SQL Client Connectivity SDK
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred during the setup process of the feature.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server Native Client Access Component
  Component error code:          1723
  Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20160203_125029\sqlncli_Cpu64_1.log
  Error description:             There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sqlncli.msi%40RollbackCleanup%401723

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file:               C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20160203_125029\SystemConfigurationCheck_Report.htm

Upgrade from SQL server express

$
0
0

Hi I am trying to upgrade from sql server express 2008 to SQL server standard version 2014, and keep getting stuck at the preinstall upgrade advisor.  It is giving me a score of 90. I tried going back to SQL server 2012, and received the same error message.  Wondering how I get around this.   Any help is appreciated!

Thanks

SQL 2012 spt_values

$
0
0

Hi,

Our spt_values view is missing on our SQL 2012 server.  I tried running the u_tables.sql file to fix it, but I get the following error:

Msg 208, Level 16, State 1, Procedure spt_values, Line 7
Invalid object name 'sys.spt_values'.
sp_MS_marksystemobject: Invalid object name 'spt_values'
Msg 15151, Level 16, State 1, Line 2
Cannot find the object 'spt_values', because it does not exist or you do not have permission

How can we fix this on 2012?

Thanks!

-Mike

How do I repair connection error?

$
0
0

I'm running SQL Server 2014 Developer on a Windows 10 64-bit computer. Before to day all was good. Today none of my applications that use SQL Server can connect. Also I can't connect using the  Management Studio. I tried going to Program and Features and running a repair on "Microsoft SQL Server 2014 Setup (English), and that didn't help. Here's the error I get in the Management Studio.

microsoft .net framework cas policy manager has stopped working error while installing SQL Server 2008 R2

$
0
0

Hi,

I have a Windows7 64 bit machine.

I have installed Visual Studio 2010 professional on it. it gave an popup error message of microsoft .net framework cas policy manager has stopped working while installing, but when I clicked cancel it install the remaining tools. On the last screen it  showed error related to Microsoft SQL Server 2008 Express Service Pack 1 (x64).

I checked that Visual studio and TFS installed correctly.

My issue started when I tried to install SQl Server 2008R2. As I clicked on the SetUp.Exe, it again gave me error of microsoft .net framework cas policy manager has stopped workingand not going any further.

I tried below options to solve it, but nothing work-

a) Uninstall VS2010

b) Disable/Enable the .NET framework 3.5.1.

c) Apply a fresh copy of installation media.

d) Verify the .NET framework 3.5 with .NET setup verification tool.

Please suggest some solution for it.



--------------------------------------- Thanks, Apne Please use Marked as Answer if my post solved your problem and use Vote As Helpful if a post was useful.


Changing SQL Locale

$
0
0

We are testing san application to mimic multiple locales, like UK, Germany, US etc

Changing the OS locale is simple. How do I change the SQL locale to reflect different countries?

The difference in locale can be seen as below grid

Date   Format

Thousand   Separator

Decimal   Separator

Alignment

          M/D/YYYY

,

.

Right

DD/MM/YYYY

,

.

Right

DD/MM/YYYY

,

.

Left

DD/MM/YYYY

;

,

Right

DD/MM/YYYY

;

,

Right

DD.MM.YYYY

;

,

Right

DD.MM.YYYY

;

,

Right

YYYY/MM/DD

,

.

Right

YYYY/MM/DD

,

.

Right

YYYY-M-D

,

.

Right

D/MM/YYYY

,

.

Right

D/M/YYYY

,

.

Right

D-M-YYYY

;

,

Right

¿What improves SQL Server performance? HD speed, Processor speed or Ram?

$
0
0

 

Hi,

 

I have several data bases on a server (SQL Server 2000 only, no web server installed) and lately, as the company keeps gowing, my users complain saying the server gets slow, (this dbs are well designed and recieve optimizations and integrity checks, etc) because of this, Im thinking about getting a new server to repleace my old ProLiant ML 330 which was bought 4 years ago but Im concerned about what server arquitecture or characteristic can help me best to improve response performance, is it HD speed? Processor speed? or more Ram? I want to make a good decision, so I´d really appreciate your help...

 

Thanks, Luis Luevano

Upgrade SQL server to increase processing speed

$
0
0
I have connected SQL server to my web service and currently the number of records being processed by a particular table has increased on a large scale. As a result of deleting and inserting into this table, the performance has gone down. Are there any suggestions on how existing SQL server can be updated to increase the performance? Currently im using SQL server Enterprise edition 2012. Only a single server is been used with no replications. Please advice.

mayooran99

unattended installation of sql server lite speed ..

$
0
0

Hi ,

I need some help in regarding .. unattended installation of sql server lite speed...

any ideas... please share...

Thanks in advance..

 

 


Yangamuni Prasad M

Processor Clock Speed vs Cores/Threads/Cache

$
0
0

We are in the process of purchasing a new SQL Server. It will initially run 64 Bit SQL 2008 Standard R2 but we will eventually upgrade to 2012. It will have 48 GB RAM with RAID 1 OS, RAID 10 data and RAID 10 logs; all 15,000 RPM drives. The server handles the back-end for our (relatively small) 60 user in-house manufacturing system. I have been given the option of the following two processors:

2 x Xeon X5675                 6 Cores                 12 Threads          12 MB Cache      3.46 GHz
2 x Xeon E7-2830              8 Cores                 16 Threads          24 MB Cache      2.13 GHz

Considering the size of our system, would it be more beneficial (performance wise) to go with the faster clock speed processor (X5675) or the processor with more cores, threads and cache (E7-2830)? I.e. in our situation would SQL utilize more cores, threads and cache.

Viewing all 7696 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>