Overview of existing SQL Server Logins, for edit/delete options

Hi all,
in my Sql Server Management Studio, I can create a new login by right-clicking the "security" item on the object explorer in the left, and selecting new->Login.
Where can I, however, get an ovevrview of all the existing logins, and possibly edit/delete them?
Thanks,
best regards,
Chris

The same place where you were looking at - the security node under the server name - has a sub node called Logins. Expand that and you will see all the logins on the server.
You can also see the logins via T-SQL query
SELECT * FROM sys.syslogins;
There is a Security node under the server node, and then there are security nodes under each database node. For LOGINs you want to look at the server level security node. If you want to see the users on each database look under the database level security
node.

Similar Messages

Check for all the dependencies of a particular SQL Server Login in SQL Server 2008R2.

I have to alter a SQL Server Login credentials. Before altering it I have to research that where is this login is being used currently. How to determine all the places where it is being used for? Thanks in advance.
PGupta

I have to alter a SQL Server Login credentials. Before altering it I have to research that where is this login is being used currently. How to determine all the places where it is being used for? Thanks in advance.
PGupta
Find out database to which this login is mapped.If its sysadmin login I guess it won't be used in application unless you dont follow security practices.Shoot a mail to application owners,all application owners.Inform them take permission from them to change
it.
This is not a exact solution but will save you from fingers getting pointed at you.because you already informed every body.
I guess there is no perfect way to find. If somebody can point I will be happy
Edit:You can configure login auditing from using below link and can check errorlog for details.Make it for both successful and failed login.Failed logins messages in errorlog has IP associated with them as well.So enough for you to guess
http://msdn.microsoft.com/en-us/library/ms175850.aspx
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Installing SQL Server 2012 Developer Edition or wait for SP2?

Hi everyone,
I just received my copy of SQL Server 2012 Developer Edition I ordered. As usual, before installing, I searched the web for any hint or other stuff on the subject.
I first found that SP1 was already available. Honestly I prefer installing using the last version available instead of upgrading. I found the SP1 install package using the following web address:
http://www.microsoft.com/fr-ca/download/details.aspx?id=35575
Is this the right install package to use?
Now, still reading everything I could find on that SP1, I found stories about major issues with SP1.
Two examples I remember:
http://connect.microsoft.com/SQLServer/feedback/details/770630
http://support.microsoft.com/kb/2793634/en-us?wa=wsignin1.0
Two others (not specifically related to SP1):
http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/a0da3372-ab3d-4af0-b4c4-0d47163e0e03/
http://www.sqlperformance.com/2012/11/system-configuration/2012-cal-problems
My question. Should I wait for SP2? If so, any target date when it should be available?
If not, what would you recommend as the logic install sequence? Should I look for any cumulative update(s)? Any other "manual settings" I should consider?
Finally, can someone guide me regarding what options I should choose while installing. My main goal is to program/build C++, C# applications using VS2010 that will interface with SQL Server for data storage purposes (add/update/delete,
batch update/delete) and reports.
Hope to hear from someone.
Stephane
BTW: My current setup is the following:
Intel(R) Core(TM)2 CPU [email protected]
3.00 Go
Vista Ultimate SP2 32bits
Visual Studio 2010 Professional Edition (which will be upgraded to last SP once installed)

Hi again,
I proceeded with download of CU7. On Microsoft's webpage, there are several files we can download:
2012_SP1_DAC_CU7_2894115_11_0_3393_x86
2012_SP1_AOrcleDes_CU7_2894115_11_0_3393_x86
2012_SP1_AOrcleSer_CU7_2894115_11_0_3393_x86
2012_SP1_PPExcel_CU7_2894115_11_0_3393_x86
SQLServer2012_SP1_CU7_2894115_11_0_3393_x86
Which one I should choose?
Also, some people reported having problems installing this update.
http://blogs.msdn.com/b/sqlreleaseservices/archive/2013/11/19/cumulative-update-7-for-sql-server-2012-sp1.aspx
Can you comment?
Thanks again for helping,
Stéphane

Wait on the Database Engine recovery handle failed. Check the SQL server error log for potential causes in SQL Server 2012 Developer Edition

I m using SQL Server 2012 Developer Edition. Even I tried 2012 express and enterprise edition but all
gave same error. I browsed msdn blog. But nothing help me out.
Below is the error log details--
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893606
Start time: 2013-10-21 12:58:05
End time: 2013-10-21 13:52:30
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for RS: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for DQ: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for FullText: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for Replication: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name: CROY-TOSH
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
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
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: C:\Users\CRoy\Downloads\SQL Server 2012 Developer Edition (x86 and x64) - DVD (English)\x64\setup\
Installation edition: Developer
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT Service\SQLSERVERAGENT
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AI
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Data
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: NT Service\MSSQLServerOLAPService
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: CRoy-TOSH\CRoy
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: ROY
CLTRESULTDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir\
CLTSTARTUPTYPE: Manual
CLTSVCACCOUNT: NT Service\SQL Server Distributed Replay Client
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir\
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\ConfigurationFile.ini
CTLRSTARTUPTYPE: Manual
CTLRSVCACCOUNT: NT Service\SQL Server Distributed Replay Controller
CTLRSVCPASSWORD: <empty>
CTLRUSERS: CRoy-TOSH\CRoy
ENABLERANU: false
ENU: true
ERRORREPORTING: true
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, BIDS, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT, SNAC_SDK, MDS
FILESTREAMLEVEL: 2
FILESTREAMSHARENAME: MSSQLSERVER
FTSVCACCOUNT: NT Service\MSSQLFDLauncher
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: false
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: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT Service\MsDtsServer110
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: SharePointFilesOnlyMode
RSSVCACCOUNT: NT Service\ReportServer
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AI
SQLSVCACCOUNT: NT Service\MSSQLSERVER
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: CRoy-TOSH\CRoy
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Passed
Feature: Client Tools Connectivity
Status: Passed
Feature: Client Tools SDK
Status: Passed
Feature: Client Tools Backwards Compatibility
Status: Passed
Feature: Management Tools - Basic
Status: Passed
Feature: SQL Server Data Tools
Status: Passed
Feature: Reporting Services - Native
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, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Database Engine Services
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, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Data Quality 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, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Full-Text and Semantic Extractions for Search
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, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
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, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Master Data Services
Status: Passed
Feature: Distributed Replay Client
Status: Passed
Feature: Distributed Replay Controller
Status: Passed
Feature: Integration Services
Status: Passed
Feature: Data Quality Client
Status: Passed
Feature: Analysis Services
Status: Passed
Feature: Reporting Services - SharePoint
Status: Passed
Feature: Reporting Services Add-in for SharePoint Products
Status: Passed
Feature: SQL Browser
Status: Passed
Feature: Documentation Components
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\SystemConfigurationCheck_Report.htm

Hi,
This 3rd time I followed this link. But nothing new, same error.
Can you please tell me how to do follow, I cannt do the 1st step, how to change the local system to windows level account, vice-versa. It is shown mine as
Server Configuration Manager(Local)
From here I folllowed the steps ---[I cannt insert link/image :-(]
SQL 2008/R2 setup fails with "Wait on the database engine recovery handle failed"
If I right clicked on SQL Server Service, there is no option to change the account.
Hello,
Thanks for your patience,did you tried stesp mentioned in below article
http://blogs.msdn.com/b/sqljourney/archive/2012/03/16/sql-2008-r2-setup-fails-with-quot-wait-on-the-database-engine-recovery-handle-failed-quot.aspx
To resolve it, follow these steps:-
When the installation throws this error, click on OK and allow it to proceed. It will fail for Database Engine, but the SQL Server service should have
been created. Check the Services console.
If the service is present, perform the following steps:-
1. Go to SQL Server Configuration manager, right click on the SQL Server service, and change the service account (if it is local system, give
it a windows level account, and vice-versa). It might throw a WMI error but you will see the account getting updated anyway. If not, then use the Services console. Change the account for SQL Agent as well.
Use this link to change sql server service account
http://technet.microsoft.com/en-us/library/ms345578.aspx
2. Next, try to start the service. It should come online.
3. However, you will not be able to log in to the SQL Server
4. Now stop the service and start it from the command prompt using -m -c -T3608 parameters.
5. Now try logging in to the server using admin connection from sqlcmd (sqlcmd admin:<server name>\<instance name> ...)
6. Once logged in, use the sp_addsrvrolemember '<domain\username>','sysadmin'.
Also add the builtin/administrators to the sysadmin role
7. Now stop the service from the command prompt and start it from SQL Server configuration manager
You should be able to log in to the server now.
Hope this helps someone.
Please revert if it helps or even if it does not
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

[Oracle][ODBC SQL Server Wire Protocol driver][SQL Server]Login failed for user 'RECOVER'

Hi,
We have exadata x3-2. I am seeing this error in alert log file frequently.
The db version: 11.2.0.3 On RAC on Linux 5.8 x86-64Bit
Errors in file /d01/oracle/TEST/11.2.0/admin/TEST1_dbtest/diag/rdbms/prod/TEST1/trace/TEST1_reco_11909.trc:
ORA-01017: invalid username/password; logon denied
[Oracle][ODBC SQL Server Wire Protocol driver][SQL Server]Login failed for user 'RECOVER'. {28000,NativeErr = 18456}
ORA-02063: preceding 2 lines from HIS_CUST
The file /d01/oracle/TEST/11.2.0/admin/TEST1_dbtest/diag/rdbms/prod/TEST1/trace/TEST1_reco_11909.trc
Contains many repeated lines like below
*** 2015-01-21 06:34:40.209
ERROR, tran=21.24.51311, session#=1, ose=0:
ORA-01017: invalid username/password; logon denied
[Oracle][ODBC SQL Server Wire Protocol driver][SQL Server]Login failed for user 'RECOVER'. {28000,NativeErr = 18456}
ORA-02063: preceding 2 lines from HIS_CUST
Could any please help why is this happening.
Thanks

Hi,
You have customers who are running distributed transactions using a gateway which need to be rolled back. However, the gateway has not been correctly configured for distributed transactions. To roll back a transaction on the SQL*Server database a connection is made as the user defined in the parameter HS_FDS_RECOVERY_ACCOUNT in the gateway init<sid>.ora file but this user has not been created in the SQL*Server database with the password defined in HS_FDS_RECOVERY_PWD. This user also needs to own the transaction log table.
I assume you are using the Database Gateway for SQL*Server (DG4MSQL) as the Database Gateway for ODBC (DG4ODBC) doesn't support distributed transaction.
If you have access to My Oracle Support have a look at this note -
How to Setup DG4MSQL to Use Distributed Transactions (Doc ID 227011.1)
Otherwise, check the Gateway documentation.
Regards,
Mike

SQL Server 2005 Workgroup Edition compatibility for SAP B1 2005B

Hi Experts,
Please advise SQL Server 2005 Workgroup Edition can be used as the backend for SAP Business One 2005B.
Thanks,
Shakeel

Hi
Please go to:SAP service portal-product availability-supported platform-database platform
For 2005 B version we could get the following supportted information:
Microsoft?SQL Server 2005 SP2
- 32 Bit / 64 Bit (x64)
- Express (3), Workgroup (4), Standard & Enterprise Edition
Please read SAP Note 928839 on how to order SQL 2005 for upgrade purposes.
(3)SQL 2005 Express Edition is only supported with the SAP Business One Evaluation Versions and only in 32 Bit mode.
(4)SQL 2005 Workgroup Edition is only supported with Windows Small Business Server (SBS) 2003 and only in 32 Bit mode
For more detailed information regarding the supportted platform you could refer to the webpage from the above path.
Best Regards
Helen Sun
SAP Business One Forums Team

SQL database login for 'SharePoint_Config_2010' on instance 'DB server' failed. Additional error information from SQL Server is included below.

we formatted Database server and restored all the databases from the backup. but the sharepoint site is giving below error when i access the home page.
we have 3 application servers in that two are working fine, but only one server getting the below error.
SQL database login for 'SharePoint_Config_2010' on instance 'db server' failed. Additional error information from SQL Server is included below.
Login failed for user 'domain\user'.
could you help what is the issue?

Hi,
According to your post, my understanding is that you failed to access sharepoint site with one application server.
It was due to the MOM/SCOM Agent that has a SharePoint management pack installed, the agents Windows Service runs as ‘Local System’ and thus causes this.
The workaround is to either kill the SCOM agent service, or set it to run as a dedicated service account.
In addtion, I recommend to add the logon account of the SharePoint Timer service as a user of the SharePoint_Config database. Give role membership to the account db_owner.
You also need to add the SharePoint accounts back into sql server.
There are some similar articles for you to take a look at:
http://blog.blksthl.com/2012/04/26/login-for-sharepoint_config-login-failed-for-user-domaincomputername-scom-agent/
http://msdn.microsoft.com/en-us/library/jj551781(v=nav.70).aspx
http://sharepoint.stackexchange.com/questions/51623/moved-sql-databases-for-sharepoint-2010-and-now-have-a-3351-error
Best Regards,
Linda Li
Linda Li
TechNet Community Support

Event 3351, SQL database login for 'DB_Config' on instance failed. Additional error information from SQL server is mentioned below. Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

category-database
event id-3351
source-sharepoint foundation
SQL database login for 'DB_Config' on instance 'DB\instance' failed. Additional error information from SQL Server is included below:
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
I have been getting this error every hour on only 1 application server of the 2.
My farm consists of 2 app servers, 2 wfes & 2 sql nodes.
My public site is working fine. Authentication is NTLM.
SharePoint VSS Writer is disabled.None of my appPool accounts are running under local system.
I have read many forums/blogs, but couldnt find a solution for this.
Any help would be appreciated!

Hi,
As I understand, you found event id 3351 in event log. Please collect more information as below：
Check if the error also occurs on other servers in your farm.
Check if backup job is scheduled at the time when the event id occurs.
Please run Config Wizard or psconfig.exe -cmd secureresources on all servers and test the issue again.
Regards,
Rebecca Tu
TechNet Community Support

Password expiry option for sql server logins

Hi Experts,
Can we set 'password expiry option' at a time for sqlserver logins as in sybase.
Thanks
Shashikala

Correct. Applies only to SQL Server logins
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

Which .exe file I should choose to apply SP2 for SQL Server 2008r2 Enterprise Edition 64Bit

Hi All,
Which .exe file I should choose to apply SP2 for SQL Server 2008r2 Enterprise Edition 64Bit.
And what is the difference between below .exe files.
SQLServer2008R2SP2-KB2630458-x64-ENU.exe
SQLServer2008R2SP2-KB2630458-IA64-ENU.exe
Grateful to your time and support. Regards, Shiva

Good day
Shiva Shakthi,
I have change the type of the thread to a question, as this is a question :-)
please chose the right type next time. If you have a question then use a question thread (this is the default), and that will let you mark the answers that you get.
Have a nice day :-)
[Personal Site] [Blog] [Facebook]

Upgrading from SQL Server 2005 Compact Edition [ENU] to SQL Server 2008 Express Edition OR HIGHER for Microsoft Security Compliance Manager

I have downloaded the MS Security Compliance Manager, which is in two parts: MS SQL Server 2008 Express Edition & the SCM. The install instructions state the the server needs to be install before the SCM. So as the install continues I get
an error message, which cancels the installation. So, I am trying to install SQL 2008 EE separate from SCM. My question is:
Can I upgrade from my current SQL Server 2005 Compact Edition [ENU]
directly to SQL Server 2008 Express Edition (or higher)?

So as the install continues I get an error message, which cancels the installation.
And which error message did you got?
SQL Server Compact Edition is something different then SQL Server Express (or Standard) Edition, you can't upgrade it as you asked for,.
Olaf Helper
[ Blog] [ Xing] [ MVP]

What licenses and how many should be taken for SQL Server 2012 Standard Edition

Hi,
Could you help me please with my problem: what licenses (per core or Server + CAL) should I take for SQL Server 2012 Standard Edition for the following environment:
SQl Server will be installed on VM with 1 core.
Physical processor is Intel Xeon CPU E7-4830, 2.13 GHz, 2131 Mhz.
Few people will have an access to the VM but SQL server is used for a web-application for about 200 users from Active Directory.
Great thanks in advance,
Lena

Hello,
Since the question is a license issue, you can call 1-800-426-9400, Monday through Friday, 6:00 A.M. to 6:00 P.M. (Pacific Time) to speak directly
to a Microsoft licensing specialist. You can also visit the following site for more information and support on licensing issues:
http://www.microsoft.com/licensing/mla/default.aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

ERROR – SQL Server Login Failed, Error 11001

We have an application that uses MSDE as its ‘Back-end’.
It has been working fine for years. We have however had to recently re-build the Operating System on our own Server that it was running on.
Original O/S Environment
We used Windows Server 2008 r2, using
Hyper-V to run Windows Server 2003 so that we can use
MSDE to run our application.
We do not want to change to later versions of SQL Server Express as they no-longer support Replication.
NEW O/S Environment
When we re-built the Server we went for Windows Server 2008 r2, using
Hyper-V to run Windows 7 Enterprise so that we can use
MSDE to run our application.
We have used this setup many times before and know that MSDE runs quite happily under Windows 7.
Servers have been renamed
The real Windows Server 2008 r2 machine used to be called FILESERVER.
It is now called FILE-SERVER.
The virtual machine running our application was originally called GEMSERVER.
It is now called GEM-SERVER.
What’s happening on the Server
The application is running fine. We can access the underlying MDSE Database with SQL Server 2005 Management Studio Express without problem.
We can build a test ODBC Data Source and connect to the ‘SQL Server’ Database, again without problems.
What’s happening on the Client PC
The application does not connect. I get:
     An error occurred while connecting.
     [DBNETLIB]ConnectionOpen (Connect())SQL Server does not exist
     or access denied.
When I build a ODBC Data Source to test the Connection I get:
Microsoft SQL Server Login
Connection failed:
     SQLState: '01000'
     SQL Server Error: 11001
     [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
     (Connect()).
     Connection failed:
     SQLState: '08001'
     SQL Server Error: 6
     [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL
     server not found
I can Ping GEM-SERVER from the Client PC without problems.
I have disabled Firewalls an Anti-Virus Software on both the GEM-SERVER and the Client PC – to no avail.
I’ve tried connecting with:
Named Pipes,
TCP/IP,
IP Address of GEM-SERVER – 192.168.16.122,
Using Specific Port 1433 in connection.
NONE of it worked. L
ANYBODY any ideas what to try next?

Here's the solution that we came up with to our own problem:
This problem was actually caused by a bug in our own Application.
For some reason when we restored our MDSE Database the correct SQL Server Access Protocols were not setup correctly. (It is designed to handle these setup issues for us and has done so previously.)
We still have to determine why it happened and rectify the problem within our Software.
However to correct the problem with our own 'Server' we had to manually:
Run netsvrcn.exe using command prompt as an Administrator on the ‘Server’ running the MSDE Database,
Enable TCP and NAMED PIPES protocol
Restart SQL Server instance
Exclude the ports SQL Server normally listens on, from the firewall using ‘Windows Firewall Advanced Security’ for both in-bound and out-bound rules:
1433 TCP port
1434 UDP port
We then tested the ODBC connection from client machine and found that it worked fine, as indeed did our application.
However we still have a residual problem.
For we cannot connect to our Server called GEM-SERVER using GEM-SERVER\GEMSQLSRVR we have had to use 192.168.16.122\GEMSQLSRVR.
We are not sure why. We obviously wish to use the machine’s name rather than its IP Address, as its IP Address is dynamically assigned by a DHCP server so may change in future.
Do I need to raise this remaining problem as a separate issue?

Unable to add replication feature in sql server 2012 web edition

Hi All,
We are using SQL Server 2012, Web edition and when it was installed replication is not an added feature so I tried to add this feature but getting below error.
Error: There are no SQL Server instances or shared features that can be updated on this computer.
Description: The version of SQL Server instance MSSQLSERVER does not match the version expected by the SQL Server update. The installed SQL Server product version is 11.1.3000.0, and the expected SQL Server version is 11.0.2100.60
And also please let me know how to identify the default file location of the setup file 'setup.exe' for SQL Server 2012 (Webedition, 64bit) Grateful to your time and support.
I'm using "C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Update Cache\KB2777772\QFE\setup.exe" to add replication feature, please correct me if I'm wrong.
Thank You.
Regards,
Kalyan
----Learners Curiosity Never Ends----

It looks like you are trying to add Replication Components, however, you are using the Cumulative update package 5 setup, which is wrong.
Note that you will not find the setup file for SQL Server on your file system, it will be on your installation media.
To install SQL Server Replication Components, locate your installation media and run Setup.exe. Select the add features to an existing instance option, select your instance, and add replication components.
Brandon Williams (blog |
linkedin)

Is it possible to install SQL Server 2012 Standard Edition on a Windows Server 2012 Standard Which is installed on a Virtual Machine that is created by Hyper-V?

Hi
I have recently bought a Virtual Machine from a data center and installed a Windows Server 2012 Standard Edition on it. As I tried to install the SQL Server 2012 Standard Edition, the data center administrator denied me to do this telling me it is not possible
to install any licensed Microsoft software on a Windows installed on virtual machine created by Hyper-V. It was really strange for me! I wanna know if this is true.
Thanks Everybody

Hi Farid,
For SQL server running on virtual server please refer to following article :
http://blogs.technet.com/b/peeyusht/archive/2010/03/19/sql-licensing-under-virtualization.aspx
In addition , for license issue we still recommend you to contact MS Activation Center:
http://www.microsoft.com/licensing/existing-customers/activation-centers.aspx
Best Regards,
Elton Ji
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

Overview of existing SQL Server Logins, for edit/delete options

Similar Messages

Maybe you are looking for