Hello,

I am currently running SQL Server 2008 in a VM with Windows Server 2012 Standard. Lately, i decided to migrate to the latest version (2017) but as i can see my current sql server must be patched with SP4 before doing so.

The question is, how safe it is to install SP4 on my current version ? Is it possible/easy to rollback if anything goes wrong ? Are there any remarkable changes in terms of security / perfomance between vanilla and SP4 ?

Thank you in advance

Regards,

Roy

I have a Server with 10 SQL Server named instances. 

On 3 of them (the last 3 I've installed) I am unable to connect remotely using ServerName\InstanceName.

However, I am able to access remotely to these 3 Instances with:

• CName that points to the Instance IP Address
• ServerName, InstancePort

Locally, on the Server where my Instances are installed I am able to connect with ServerName\InstanceName.

All other instances work fine, i.e. I am able to connect remotely with ServerName\InstanceName.

My SQL Server Browser Service is running and I have a firewall rule to allow connections to UDP 1434 (otherwise the other 7 Instances would not work either). The Ports from all the Instances are also open on my Firewall (otherwise I would not be able to connect to using the CName (IP Address of the Instance).

I am running the latest build, SQL Server 2016 SP2 CU3 (13.0.5216.0).

I have nothing on my SQL Server Log, Server Log and Firewall Log.

Has anyone experience something similar or can give me a hint on what I should be looking at?

Hi,

   When I upgrade from SQL Server 2014 to SQL Server 2017 with only the database engine and SSIS installed.  I am able to uninstall SQL Server 2014 SSIS, and SSMS using unattended  configuration file.  But When I have all the services installed (SSRS, SSIS, SSAS)  somehow the installation process leaves a lot of SQL Server 2014 menu items behind, and SSIS 12 in the configuration manager behind.  But I can't clean it up. I see some suggestions to go to the program features and uninstall, but I am try to execute this in an unattended way.

First of all is this to be expected.  shouldn't it get rid of SQL Server 2014 items from the menu?  Thanks.

I am trying to obtain a 64-bit  "Microsoft Text Driver (*.txt; *.csv)" driver  so that I can access csv files. Does one exist?

I am using sqlserver 2005 x64 and have installed the 64-bit version  MSDASQL
 
My goal is use openrowset as follows

select*
fromOpenRowset('MSDASQL','Driver={Microsoft Text Driver (*.txt; *.csv)}; 
                      DefaultDir=\\myserver\share\testdata;Extensions=CSV;',
                         'select * from testdata.csv')


But get the following error

OLE DB provider "MSDASQL" for linked server "(null)" returned message "[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified".
Msg 7303, Level 16, State 1, Line 1
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "(null)".

This work fine on a 32 bit server


Thanks

Hi,

I have elevated rights on my PC but not Admin rights exactly (I cannot start or stop a service)...I think this is part of the issue as it failed during installation. When I look at the local services they are not running. Not sure how to fix it. Log below.

Hi people,

I'm tring to migrate Sql Server 2000 to SQL Server 2005 using "Copy Database Wizard" but i get the following error:

- Add log for package (Success)
- Add task for transferring database objects (Success)
- Create package (Success)
- Start SQL Server Agent Job (Success)
- Execute SQL Server Agent Job (Error)
 Messages
 * The job failed.  Check the event log on the destination server for 
details. (Copy Database Wizard)

When I take a look at 'Event viewer' on the SQL 2005 server, the following 
error is displayed;

InnerException-->An error has occurred while establishing a connection to 
the server. 
When connecting to SQL Server 2005, 
this failure may be caused by the fact 
that under the default settings SQL Server does not allow remote connections. 
(provider: Named Pipes Provider, error: 40 - Could not open a connection to 
SQL Server)

I try this link but not success.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=752092&SiteID=1

Can anyone help me?

SQL Newbie here -

I installed SQL 2012 on a server and want to isolate traffic to a specific nic.  I've gone into configuration manager where Named Pipes is disabled, Shared Mem is enabled and TCP/IP is enabled. I've modified the TCP/IP protocol by changing the Listen All to NO, changed the IPALL: TCP Dynamic ports to have no value and modified one of the IPn enabled values to yes and manually changed that IP from a 169 address to the IP of the nic I want SQL to send traffic through: 192.168.0.1. I've also changed all the other IPn enable values to No, including the 127.0.0.1. 

I've gone to the command line and ran netstat -ano and confirmed sql is listening via the IP and port I've specified and only on that IP. 

192.168.0.1:1433 

My mysqlserver instance is running, as I can run sc query mysqlserver and the command line and see state 4 running.

However, the app, I'm trying to connect to sql fails, despite using a windows account that pretty much has god access. 

So. how can I confirm that the client server can connect to mysql server independent of the app? 

Jim

hi

getting space constraint   on C: ,  can we remove this file from this location?

C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Update Cache   -- contains KBarticles

recently applied patches on 5/13/2018  

or else  except recent KB.   we can remove all thing?

C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log

once we remove this files,

 we cannot revert backup the patches/ uninstall patches.

 while install new patches it will not show existing version list.

so can we remove all files except recent files.?

Hi,

I need SQL Server 2016 SP2 CU2 and not CU3 but I cannot find this version anymore, everything routes me back to CU3.

I nned CU2 as this is what we have tested against and not CU3, and we don't have time to test CU3 before we go live.

thanks

Hello,

I have recently installed SQL Server 2017 Enterprise Developer Edition for evaluation and am particularly interested in all aspects of security.  So for the install, I have checked to install SSIS Scale Out Master and SSIS Scale Out Worker.  I accepted the default virtual service accounts for these two services as well as for others (ie sql server, sql server agent).  I configured SQL Server login audit events to write the Windows Event -> Application Log.   I keep seeing entries like in Windows Event Viewer:

Login failed for user 'NT Service\SSISScaleOutMaster140'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]

I then checked the Local Users & Groups on the SQL Server machine and I didn't see this account - 'NT Service\SSISScaleOutMaster140' or any other service accounts (like sql server service, agent and etc..) which I had accepted as defaults during the installation.

Questions are:

Q1 - Where do I find these virtual accounts - NT Service\*

Q2 - What's the reason for the login failure related to 'NT Service\SSISScaleOutMaster140' and how do I fix this?

Thank you

Hello,

  When I right click on 'Databases' on a SQL server, the  'Attach Databases' opens with disabled content. Hence I am unable to proceed with attaching any databases.

Please have a look.



Hello,

Since two months I can see many entries with the below sentences in SQL logs.

2017-04-24 22:01:43.900 spid31s      SSBDT: Dialog timer delete during registration (did: 725D87C0-8AAF-4383-BCFC-725AC025CD1D:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:02:41.290 spid31s      SSBDT: Dialog timer delete during registration (did: 6F5BF516-934A-45E4-B1B1-D60DF3401B4E:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:03:17.650 spid31s      SSBDT: Dialog timer delete during registration (did: F044EE94-7203-4FF5-9BB6-00D21B86E686:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:03:22.350 spid31s      SSBDT: Dialog timer delete during registration (did: 0B92D137-915C-4920-9C69-541F87266D90:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:03:37.980 spid31s      SSBDT: Dialog timer delete during registration (did: 958A51D1-B18F-410F-93B5-358D10C81EF5:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:03:40.310 spid31s      SSBDT: Dialog timer delete during registration (did: 14373439-9330-4E2C-BF2B-6901A3ED42BF:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:07:39.000 spid31s      SSBDT: Dialog timer delete during registration (did: 6E9C57B7-BDD5-42BC-BA9A-A5A3F97DC91A:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:08:02.360 spid31s      SSBDT: Dialog timer delete during registration (did: 98B47642-1373-4EF7-86B0-E320B48611A9:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:08:02.480 spid31s      SSBDT: Dialog timer delete during registration (did: 1D1263CE-151D-4C64-90BA-4293A29D6BD0:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:09:27.750 spid31s      SSBDT: Dialog timer delete during registration (did: C7D98CCF-F67D-450B-870B-0242585E9B07:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:09:36.700 spid31s      SSBDT: Dialog timer delete during registration (did: 0D243BC3-6B83-45A0-AF2B-E4AF24098B9D:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:09:51.270 spid31s      SSBDT: Dialog timer delete during registration (did: 4CCDA7EA-FB1E-44C7-9234-C0D7C8484750:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:10:15.450 spid31s      SSBDT: Dialog timer delete during registration (did: 2A515B80-9AFA-45F2-9ECB-1328BBB63852:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:11:10.770 spid31s      SSBDT: Dialog timer delete during registration (did: 9920B4CC-EF38-4A8C-A3AE-FAADD7D75267:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:11:15.610 spid31s      SSBDT: Dialog timer delete during registration (did: 4ABA0501-7CD2-4F58-9B59-49A7A9799092:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:11:20.960 spid31s      SSBDT: Dialog timer delete during dispatch (did: 8FAECCF7-6AC5-4FB2-84DC-4927E839D028:Target, OpType: DialogCleanupDispatch OpResult: Null)
2017-04-24 22:13:24.770 spid31s      SSBDT: Dialog timer delete during registration (did: A932AF41-C0D0-4234-899B-5E5A4565F924:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:13:24.910 spid31s      SSBDT: Dialog timer delete during registration (did: 00F178A3-640D-44E4-9C39-A69271B279C9:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:13:42.310 spid31s      SSBDT: Dialog timer delete during dispatch (did: 20D9F06E-BC29-4BA5-9623-E08765B42BC7:Target, OpType: DialogCleanupDispatch OpResult: Null)
2017-04-24 22:14:00.290 spid31s      SSBDT: Dialog timer delete during registration (did: AA47FA4F-F793-4D89-BBCB-2E434596476F:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:16:31.660 spid31s      SSBDT: Dialog timer delete during registration (did: DD35C46C-7EF0-410F-B78D-CB38DFBD4DEB:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:17:06.290 spid31s      SSBDT: Dialog timer delete during registration (did: E857E323-ED31-4FEC-9AB9-39115D50CA4E:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:18:47.130 spid31s      SSBDT: Dialog timer delete during registration (did: CEDC4256-B4F2-4844-B2DA-9F49C41DE529:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:19:06.390 spid31s      SSBDT: Dialog timer delete during registration (did: 2ACDA3E2-4449-46A8-8A64-E8DF072FEF2A:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:21:30.410 spid31s      SSBDT: Dialog timer delete during dispatch (did: E09596A9-CD56-4597-B428-DE392D542E29:Target, OpType: DialogCleanupDispatch OpResult: Null)
2017-04-24 22:22:32.890 spid31s      SSBDT: Dialog timer delete during dispatch (did: EC39EEE2-ACC5-49F4-A375-2CC3EA2C68CD:Target, OpType: DialogCleanupDispatch OpResult: Null)
2017-04-24 22:23:01.630 spid31s      SSBDT: Dialog timer delete during dispatch (did: DF7D37D2-C4C6-403B-AD77-EC070EC47F36:Target, OpType: DialogCleanupDispatch OpResult: Null)
2017-04-24 22:23:25.520 spid31s      SSBDT: Dialog timer delete during dispatch (did: 8FDB1B72-8C0B-49F3-B305-93DC9F52EC72:Target, OpType: DialogCleanupDispatch OpResult: Null)
2017-04-24 22:25:22.860 spid31s      SSBDT: Dialog timer delete during dispatch (did: 8E7E1C64-16C7-4BB9-A77C-717B1BDF5859:Target, OpType: DialogCleanupDispatch OpResult: Null)
2017-04-24 22:25:45.920 spid31s      SSBDT: Dialog timer delete during dispatch (did: E47E8924-8741-48B0-BB55-2B573247CEE7:Target, OpType: DialogCleanupDispatch OpResult: Null)
2017-04-24 22:27:17.560 spid31s      SSBDT: Dialog timer delete during dispatch (did: CBE4F1C7-A98D-424E-AD0D-339727F76937:Target, OpType: DialogCleanupDispatch OpResult: Null)

We are using SQL server 2012 SP3

Do you know what could be the source of that problem?

We could not find info....

Hi there,

We had bought Volume License for our client for their SQL server for 50 units.

And we had received Volume License certificate from our provider

And (the accounting vendor) had install it in the server last year, around July 2017.

Last week Monday, the client, called us and told us that their SQL server stop functioning, then i've try to remote into their server and found that their SQL services not running - even though i try to restart the services and reboot the whole server.

Upon something is fishy, i went down to Event Logs to inspect, and to my shock, the logs reported, the SQL services could not be started due to the expiry of the SQL Trial version. Then i checked the SQL version, yes, it is evaluation version and asked to enter the product keys.

My question is, i had log into the VLSC and downloaded the correct SQL server 2016 version and put it into that server to be installed. Then how come after a year, (evaluation is 180 days or 6 months), this SQL version suddenly changed to Evaluation version. Anyone had any ideas about this ?

And as far as i know Volume Licensing product does not have Product Key - as i could not see any product key in VLSC when i downloaded the SQL server 2016.

I'm trying to run a silent install of SQL Server 2014 and getting the error: Media ScenarioEngine.exe returned exit code: 0x84B40001. I call this install from a C# program but if I run the same command from a command line it works fine. Here's the command I'm issuing:

SQLExpr_x64_ENU.exe /SkipInstallerRunCheck /QUIETSIMPLE /SAPWD="OurPWHere" /INSTANCENAME="PACSGEAR" /INSTANCEID="PACSGEAR" /ACTION=Install /FEATURES=SQLENGINE /AGTSVCSTARTUPTYPE=Manual /ISSVCSTARTUPTYPE=Automatic /ISSVCACCOUNT="NT AUTHORITY\NetworkService" /ASSVCSTARTUPTYPE=Automatic /SQLSVCSTARTUPTYPE=Automatic /SQLSVCACCOUNT="NT AUTHORITY\NETWORK SERVICE" /SQLSYSADMINACCOUNTS="BUILTIN\Administrators" /SECURITYMODE=SQL /IACCEPTSQLSERVERLICENSETERMS /SKIPRULES=RebootRequiredCheck

And here's a snippet of the c# code that fails

string commandLine = "/SkipInstallerRunCheck /QS /SAPWD=" + sSQLOurSAPwd + " " +
                "/INSTANCENAME=" + sqlInstance + " /INSTANCEID=" + sqlInstance + " /ACTION=Install " +
                "/FEATURES=SQLENGINE /AGTSVCSTARTUPTYPE=Manual /ISSVCSTARTUPTYPE=Automatic " +
                "/ISSVCACCOUNT=\"NT AUTHORITY\\NetworkService\" /ASSVCSTARTUPTYPE=Automatic /SQLSVCSTARTUPTYPE=Automatic " +
                "/SQLSVCACCOUNT=\"NT AUTHORITY\\NETWORK SERVICE\" /SQLSYSADMINACCOUNTS=\"BUILTIN\\Administrators\" /SECURITYMODE=SQL " +
                "/IACCEPTSQLSERVERLICENSETERMS /SKIPRULES=RebootRequiredCheck";

Process installerProcess = Process.Start(sSQLSetup, commandLine);

I've googled the exact error message and found nothing. Please help!

Hi all,

We're looking to implement a SQL 2016 server (Standard) with multiple DB's within the same instance.

One of the apps we're putting in to it is SolarWinds which is very hungry.

Is there any way to prevent that from impacting the other apps running out of this instance within the SQL standard license?

I know with Ent you get access to resource governor but is there anything similar in Standard? Or should we just be looking at separate instance / clusters?

Thanks,

Tom

Hello,

Trying to deploy SQL Server 2016 on a maschine that already has SQL Server Mgmt Studio 2017 (v14.0.17277.0) installed. This leads to an exception during installation: 

(01) 2018-10-12 13:25:04 Slp: Target package: "C:\WINDOWS\ccmcache\n\1033_ENU_LP\x64\setup\x86\DACFramework.msi"
(01) 2018-10-12 13:25:04 Slp: MSI Error: 0 A newer version of Microsoft SQL Server Data-Tier Application Framework is already installed.
(01) 2018-10-12 13:25:04 Slp: InstallPackage: MsiInstallProduct returned the result code 1603.

Indeed, the machine has SQL Server Data-Tier Application Framework x86 v14.0.4079.2 already installed during setup of SSMS 2017.

Reproduced this by: 

• uninstalling SSMS 2017
• uninstalling Data-Tier Application Framework
• rebooting
• installing SSMS 2017 again
• > this brings back the data tier application framework v14

When I uninstall the framework and then retry setup for SQL Server 2016, the installation completes successfully.

This creates the following questions for me: 

• is it generally not supported to install SQL Server 2016 when SSMS 2017 is already installed?
• can I somehow prevent SSMS 2017 from installing Data Tier Application Framework?
• can I tell SQL Server 2016 to ignore teh fact that a newer version of Data Tier Application Framework is already installed?

im go to take adhoc sql full backup, before application upgrade eg: BACKUP DATABASE testdb  TO DISK = 'C:\testdb.BAK' WITH STATS, DESCRIPTION = 'Full backup for AdventureWorks' GO how do you I know, my backup is not corrupted, and will work after repair sql database, incase if required Sorry I dont have environment to test.. it.. Do i need to do consistency check or readability check before take backup, if yes, how can i do that in Tsql?