Lookout SQL Server Running at 100%

Hi there,
We have a system that is logging alarms for several sewage pumpstations. We recently had a problem with the HMI machine where the Microsoft SQL Server was running at close to 100%. I was unsure what SQL server was doing, so I disabled it in the services manager.
However, after doing this I found that I could not search the database for alarms (which makes sense). I then restarted the SQL Server, but once again found that it pushed the computer CPU close to 100%.
Is there any reason for this? How could this be fixed?
-andrew

Check this previous post.
http://forums.ni.com/ni/board/message?board.id=190&message.id=3160

Similar Messages

EKM using the Azure Key Vault is now available for SQL Database and SQL Server running in Azure VM's

In preview today, you can create keys in the Azure Key Vault, and use them with Azure SQL Database, or SQL Server running in a Azure VM. Use the Extensible Key Management (EKM) for TDE, backup encryption, or cell level encryption. For more information, see
Extensible Key Management Using Azure Key Vault (SQL Server)
http://msdn.microsoft.com/en-us/library/dn198405.aspx.
The announcement:
Azure Key Vault in public preview
Key Vault offers an easy, cost-effective way to safeguard keys and other sensitive data used by cloud applications and services. Included are the following features:
Enhance data protection and compliance:
Protect cryptographic keys and sensitive data like passwords with keys stored in Hardware Security Modules (HSMs). For added assurance, import or generate your keys in HSMs certified to FIPS 140-2 level 2 and Common Criteria EAL4 standards,
so that keys stay within the HSM boundary. Key Vault is designed so that Microsoft doesn’t see or extract your keys.
All the control, none of the work:
Provision new vaults and keys in minutes and centrally manage keys, sensitive data, and policies. You maintain control over your encrypted data—simply grant permission for your own and third-party applications to use keys as needed. Enable
developers to easily manage keys used for dev/test and migrate seamlessly to production keys managed by security operations.
Boost performance and achieve global scale: Improve
performance and reduce latency of cloud applications by storing cryptographic keys in the cloud (versus on-premises). Key Vault rapidly scales to meet the cryptographic needs of your cloud applications and match peak demand.
Get started with Azure Key Vault by creating keys for applications you develop,
SQL Server encryption (TDE, CLE, and Backup), and partner solutions like
CloudLink SecureVM.
Key Vault is available now at no charge with discounted preview pricing starting on January 15, 2015.
For more information, please visit the
Key Vault webpage. For a comprehensive look at pricing, please visit the
Key Vault Pricing webpage.
Rick Byham, Microsoft, SQL Server Books Online, Implies no warranty

Thank you for sharing this Rick.
Regards,
Alberto Morillo
SQLCoffee.com

WSUS wants our SQL server (running 2008 R2 SP2) to install SP1. Why?

We just installed a bunch of Windows Updates on our servers (that were pushed out from WSUS). One of the updates -- SQL Server 2008 R2
SP1 -- failed to install on our SQL server. But that's because it already had
SP2 installed. I ran a Discovery Report, and all of our SQL Server 2008 R2 components are at SP2. And yet, WSUS wants this server to install SP1.
Any suggestions as to why? I'd rather not re-install SP2 if it's not necessary.
Thank you!
p.s. I do see the following in the Sumary.txt file produced by the Discovery Report:
Package properties:
Description:                   SQL Server Database Services 2008 R2
ProductName:                   SQL Server 2008 R2
Type:                          RTM
Version:                       10
SPLevel:                       1
Installation edition:          EVAL
What is this "EVAL" version? I don't think we ever installed an evaluation version of SQL, though I suppose that's possible

Hi,
A similar thread discussed below was caused that reporting service didn’t work properly. And the solution is to run
Sp2 setup again and just select reporting service for upgrade.
For more information please refer to:
SQL Server 2008 R2 SP2 wants to install SP1 again via WSUS
http://social.technet.microsoft.com/Forums/en-US/6e711903-7c2c-4bec-a9d8-c0b56ba0f9f8/sql-server-2008-r2-sp2-wants-to-install-sp1-again-via-wsus?forum=sqlsetupandupgrade

SQL Server runs update on one record, returns -1 records updated to java

I am trying to troubleshoot an issue in SQL Server. For all the databases in a specific server, the return value for java initiated update statements have completed the update (ie. I can go into SQL Server and verify the values have changed), but returned
a value of -1 records updated. I am not sure what went wrong to cause this to fail. It works on one server, but not on any databases on the other server and it suddenly changed on Friday, April 10. Here is the results of the java I am running.
Driver vendor: Microsoft JDBC Driver 4.0 for SQL Server
DriverVersion: 4.0.4621.201
dbproduct: Microsoft SQL Server
JavaPlus Connection Made: no warnings
Executing :update maxsequence set maxreserved = 401 where sequencename ='SERVERSESSIONSEQ' and maxreserved=400
Using TYPE_SCROLL_INSENSITIVE
Execute Returned -- (boolean) --- false
Execute getUpdateCount -- (num) -1
Execute took :0(15) secs.
Update/Deleted :-1 records.
Fetching/Updating took :0(0) secs.
I am runnning SQL Server 2012 and Windows 2012R2
Microsoft SQL Server Management Studio 11.0.2100.60
Microsoft Analysis Services Client Tools
11.0.2100.60
Microsoft Data Access Components (MDAC) 6.3.9600.16384
Microsoft MSXML 3.0 4.0 6.0
Microsoft Internet Explorer 9.11.9600.16518
Microsoft .NET Framework 4.0.30319.34011
Operating System 6.3.9600

Can you clarify why your Java output saying Execute Returned -- (boolean) --- false
I suspect this update never happened and it is possible to get updated row counts such as by using stored
procedure and returning @@ROWCOUNT value through return statement to the data set
Would you like to try this?
Good Luck! Please Mark This As Answer if it solved your issue. Please Vote This As Helpful if it helps to solve your issue

Multiple instance of Sql server running for Analyzer 7.0 install

Hi,I do have a Sql server instance where the server name is: abc\xyz. Will analyzer accetp a '\' as the server name. This instance of Sql server is not running is not running on the std port 1433. Let me know if there will be any issues whrn installing Analyzer 7.0.Thanks,

There can only be a single default instance and multiple named instances.
BOL: http://technet.microsoft.com/en-us/library/ms143547.aspx
Kalman Toth Database & OLAP Architect
SELECT Video Tutorials 4 Hours
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

Unable to get SQL Server Agent to run after installing SQL 2012 Standard with SP1

I am unable to get SQL Server Agent to run after installing SQL 2012 Standard with SP1. Log message is as follows:
Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
Failed to verify Authenticode signature on DLL 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn\xplog70.dll'.
Error: 17750, Severity: 16, State: 0.
Could not load the DLL xplog70.dll, or one of the DLLs it references. Reason: (null).

Hi JFriedley,
According to your error message, there might three reasons for this issue.
xplog70.dll is corrupt, you need to check if you have any SQL Server running on same file version and same production
edition. If xplog70.dll is corrupt, you can copy it from the new server where agent is running fine to your problematic server.
Native client not installed properly. If you try applying any latest Service Pack or Cumulative Update then check if the SQL Server Agent can start, if that also doesn’t solve issue then try to reinstalling SQL Server Native client from SQL Server setup
files.
There is a similar issue about error 17750, you can review the following article.
http://blogs.lostincreativity.com/sqldba/sqlserver-error-17750-could-not-load-the-dll-xpstar90-dll/
Regards,
Sofiya Li
If you have any feedback on our support, please click here.
Sofiya Li
TechNet Community Support

Error when insert data in Sql Server table(DateTime data type)

Hello all,
I have created a database link in oracle 11g to SQL Server 2008 using Sqlserver gateway for oracle,Oracle run on Linux and SQL Server run on Windows platform.
I have queried a table and it fetches rows from the target table.
I am using this syntax for insert a row in Sql Server table.
Insert into Prod@sqlserver (NUMITEMCODE, NUMPREOPENSTOCK, NUMQNTY, NUMNEWOPENSTOCK, DATPRODDATE , TXTCOMPANYCODE, "bolstatus", NUMRESQNTY )
Values (1118 , 1390.0 , 100.0 ,1490 , '2012-06-23 12:37:58.000','SFP' ,0 , 0 );
but it give me error on DATPRODDATE,The data type of DATPRODDATE column in Sql Server is DATETIME.
My Question is how can i pass the date values in INSERT statement for Sql Server DateTime data type.
Regards

Just as with Oracle, you have to specify the date using the to_date() function or use the native date format for the target database (if you can figure out what that is). This is good practice anyway and a good habit to get into.

Unable to protect SQL Server after adding SQL Aliases

DPM 2012 R2 had been successfully backing up a Server 2012 R2 virtual machine running SQL Server 2012 SP2 with 3 databases. It had been working properly for several months, the Virtual Machine is running on a Hyper-V Cluster.
Approximately a week ago we configured aliases for the various SQL databases to provide better resiliency in case of server failure. IE, instead of connecting to SQL as ServerName\DatabaseA, you could connect to just DatabaseADNS. Doing so we
had to add extra IP addresses to the server's adapter. Initially all the addresses were registering in DNS and Named Pipes was disabled in SQL Configuration Manager for the Databases so it led to some connection difficulties when trying to connect to
the named instances (ServerName\DatabaseA). We resolved this so that while the server's adapter has multiple IP address there is only one DNS entry for the ServerName and one entry for each Database in DNS. Named pipes is enabled so SQL Manager
can connect properly.
Since Aliases were applied however DPM began failing on 2 of the 3 Databases. It was unable to create recovery points.
The connection to the DPM agent on the SQL Server is OK, but if you try to modify a protection group and browse to the SQL Server when you expand it it just displays an hourglass and will not error out or display ANY sources to backup. Even after several
hours.
We stopped protection of all items on the SQL Server, uninstalled the DPM agent, restarted, re-installed the DPM agent, restarted. Restarted DPM Server, and are still unable to protect ANY items of the SQL Server.
There are no errors in the event logs on either server I could find. And I've watched the DPMRA service start on the SQL Server when the DPM Server attempts to query it, so there is some communication. Any help would be appreciated as I am at
a loss.

After much testing and troubleshooting a solution was found. Our configuration is apparently a perfect storm of settings that cause DPM issues. Our SQL Server has multiple NICs (if one is disabled it begins working) Our SQL Server's multiple
instance are all using the default port 1433 (if ports are set differently it works), and we are using TCP aliases for more than one instance (if only one, it works)
Each instance in SQL Config manager is assigned a unique IP address, so our production NIC has multiple IPs, set this nic to NOT register in DNS. Manually create a Static DNS entry for the server and each alias IP address.
In SQL Config manager set a Named Pipe alias for each instance. Be sure to do both 32 and 64 bit aliasing.
On the SQL Server run cliconfg.exe and enable both TCP/IP and Named Pipe protocols.
And DPM can now enumerate and backup the server again.

How to Configure Remote Connections To SQL Server 2008 R2 Express

Post written June 10, 2010 and pertains to:
SQL Server 2008 R2 Express on both my server and local machines: SQLX_SRV,
SQLX_LOC
SQL Server 2008 R2 Management Studio on both my server and local machines:
MS_SRV, MS_LOC
Windows Server 2008 R2 Enterprise installed on a Hyper-V VPS: WS
SQL Server Configuration Manager on both my server and local machines:
CMGR_SRV, CMGR_LOC
Server Manager: SMGR
I am connecting to my hosting server via Remote Desktop Connection: RDC
I installed SQLX_SRV and MS_SRV on my hosting server and SQLX_LOC and MS_LOC on my local development machine. I am able to use MS_LOC to connect to SQLX_LOC and to use MS_SRV to connect to SQLX_SRV. However I am not able to use MS_LOC to connect
with SQLX_SRV. Here's what I have done so far:
SMGR -> Configuration -> Windows Firewall to turn off the Windows Firewall for Domain, Private and Public profiles. Obviously I'll change this later, but until I can connect I want to remove as many variables as possible.
CMGR_SRV -> SQL Server Services to confirm that both SQL Server (SQLEXPRESS) and SQL Server Browser services were running.
CMGR_SRV -> SQL Server Network Configuration -> Protocols for SQLEXPRESS to ENABLE the Shared Memory, Named Pipes, and TCP/IP protocols and DISABLE the deprecated VIA protocol.
CMGR_SRV -> SQL Server Network Configuration -> Protocols for SQLEXPRESS -> double click TCP/IP to open the TCP/IP properties dialogue. On the Protocol tab Enabled: Yes, Keep Alive: 30000, changed Listen All to No. I've tried it both
ways, but I've got six IP addresses on my server and I wanted to configure SQLEXPRESS to listen to only the first and primary IP. On the IP Addresses tab went to IPALL and cleared the TCP Dynamic Ports field and entered 1433 in the TCP Port field.
For my first and primary IP Address I made sure that Enabled was Yes, I cleared the TCP Dynamic Ports field, and entered 1433 in the TCP Port field. For all other IP Addresses Enabled was set to No and I cleared both the TCP Dynamic Ports and TCP Port
fields.
CMGR_SRV -> SQL Server Services -> SQL Server (SQLEXPRESS) right click and Restart. This of course stopped and restarted my instance of SQLX_SRV enabling the TCP/IP configuration in the previous step to take effect.
On my server, SQLX_SRV is the only instance of SQL Server running and so it's easy to hard wire it to the default port 1433.
The instance name for both SQLX_SRV and SQLX_LOC is the default "SQLEXPRESS". My server machine name is "SERVER1" on the EnglishBrains.com domain. So the proper local name (local within the context of my remote server as connected via RDC) for
my instance of SQLX_SRV would be:
SERVER1\SQLEXPRESS
Note the use of a backslash NOT a forward slash.
Of course to connect remotely from my development machine, which is not on the same domain as my hosting server, I would need to specify the domain as well, so the SQL Server name becomes:
SERVER1.EnglishBrains.com\SQLEXPRESS
I must also use SQL Server Authentication. Before I can use such a remote connection, however, there are still several configuration steps required. So on my server (connected via RDC) I used MS_SRV to connect to SQLX_SRV using SERVER1\SQLEXPRESS
for the server name and Windows Authentication. Once connected I performed the following steps:
MS_SRV -> right click the connected parent SERVER1\SQLEXPRESS instance node at the top -> Properties -> Security -> Server authentication: select "SQL Server and Windows Authentication mode". This will enable connections using either type
of authentication.
Next, leaving the Server Properties dialogue open, Connections -> check "Allow remote connections to this server" box.
Click OK to save these changes and close the Server Properties dialogue.
MS_SRV -> Security -> right click Logins and select "New Login...", the Login - New dialogue opens.
On the General page Enter a name for your new login
Select SQL Server Authorization
Enter and confirm a password
Uncheck Enforce password expiration
Select the default Database and Language
On the ServerRoles page Public will be checked, also check SysAdmin. This is probably not a good idea and I'll uncheck this as soon as I can connect to the SQLX_SRV.
On the User Mapping page select the databases you want your new Login to access and enter the Default Schema of "dbo".
At the bottom of the User Mapping page you'll see the Database Roles table. Public will be selected by default. Also select db_Owner. Again this is probably not a good idea, and I'll refine this once I can connect.
On the Status page confirm that "Grant" is checked under "Permission to connect to database engine" and "Enable" is checked under "Login".
Click OK to save all changes and close the Login - New dialogue.
With these steps completed you should now be able to use MS_SRV to connect to SQLX_SRV using SQL Server Authentication by supplying the name and password for your new Login. I tried this and it worked fine. Next I tried to use this same login
remotely, that is I went to my local development machine and used MS_LOC to try and connect to SQLX_SRV by using
SERVER1.EnglishBrains.com\SQLEXPRESS
and opting for SQL Server Authentication and supplying the name and password of my new login.
THIS DID NOT WORK?? Instead I get the following error message:
Cannot connect to SERVER1.EnglishBrains.com\SQLEXPRESS.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider:
SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
For help, click:
http://www.microsoft.com/products/ee/transform.aspx?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1
If you follow the suggested help link, you are told:
The SQL Server client cannot connect to the server. This error could be caused by one of the following reasons:
A specified SQL Server instance name is not valid.
The TCP, or named pipes protocols are not enabled.
The firewall on the server has refused the connection.
The SQL Server Browser service (sqlbrowser) is not started.
WRONG on all 4 counts! The instance name IS valid. Both TCP/IP and Named Pipes protocols are enabled. The firewall has been shut down, so it is not relevant. Finally the SQL Server Browser IS started.
The next thing I tried was to circumvent discovery by the SQL Browser service by using the following syntax to specify the IP address and port directly when specifying the SQL Server name.
tcp:68.71.134.186,1433
Using this in the Server Name field I was able to use MS_SRV to successfully connect to SQLX_SRV (using SQL Server Authentication of course) with or without the SQL Browser service running.
However when I tried to connect from MS_LOC to SQLX_SRV using this same login (WITH SQL Browser service running just for good measure) it does not work?? I get the following error message:
Cannot connect to tcp:68.71.134.186,1433.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider:
TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) (Microsoft SQL Server, Error: 10060)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=10060&LinkId=20476
If you follow the help link you are told:
"The SQL Server client cannot connect to the server. This error could occur because either the firewall on the server has refused the connection or the server is not configured to accept remote connections."
However, the firewall has been shut down and the server HAS been configured to accept remote connections!
I confirmed that i could indeed Ping to 68.71.134.186 and running NetStat -a |find /i "listening" on the server shows that the server is indeed listening at 68.71.134.186 Port 1433 -- which is why I was able to connect to SQLX_SRV using MS_SRV with
tcp:68.71.134.186,1433 .
IN SUMMARY: Even though I can connect to my SQLEXPRESS instance multiple ways from the server itself, I cannot connect remotely from my development machine!
If anyone can help me figure out why I would be very, very grateful!

My two cents to help you out on c# code example to configure the remote sql server express.
Hope it helps. It works, but you have to be extra carefull to read it all and setup the server configuration and netsh commands; also the port fowarding on the router.
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Data.SqlClient;
namespace sqlremoteconnection
class Program
static void Main(string[] args)
// this is the local sql server connection
// 192.168.1.101\SQLEXPRESS
// now, the configuration for remote access:
// activate SQL SERVER BROWSER - set it to start "automatic"; then START UP
// SQL Server Configuration Manager
// --> SQL SERVER BROWSER -> properties -> Service -> Start Mode -> automatic -> apply
// --> Log On -> Start -> Ok
            // netsh firewall set portopening protocol = TCP port = 1433 name = SQLPort mode = ENABLE scope = all profile = CURRENT
            // netsh firewall set portopening protocol = UDP port = 1434 name = SQLPort mode = ENABLE scope = all profile = CURRENT
            // netsh advfirewall firewall add rule name = SQLPort dir = in protocol = tcp action = allow localport = 1433 remoteip = any profile = PUBLIC
            // netsh advfirewall firewall add rule name = SQLPort dir = in protocol = udp action = allow localport = 1434 remoteip = any profile = PUBLIC
// VERY IMPORTANT FOR REMOTE ACCESS: you have to add the rules on port fowarding
// on the router!!!
// TCP: 1433
// UDP: 1434
// or just a personal port like TCP 31433/UDP 31434
// read carefully the netsh commands above
// server name: 123.132.24.177\SQLEXPRESS
// server name: anyurl.myftp.org\SQLEXPRESS,1433 <<-- regular port
// server name: anyurl.myftp.org\SQLEXPRESS
// server name: anyurl.myftp.org\SQLEXPRESS,31433 <<-- WOW different PORT here!!!
SqlConnection myConnection = new SqlConnection(
"user id=sa;" +
"password=password_goes_here!;" +
"server=anyurl.myftp.org\\SQLEXPRESS,31433;" +
//"Trusted_Connection=no;" +
"database=database_name_here; " +
"connection timeout=30");
try
myConnection.Open();
catch (Exception e)
Console.WriteLine(e.ToString());
try
SqlDataReader myReader = null;
SqlCommand myCommand = new SqlCommand("select * from mytable", myConnection);
myReader = myCommand.ExecuteReader();
while (myReader.Read())
Console.WriteLine(myReader["tab01_name"].ToString());
Console.WriteLine(myReader["tab01_age"].ToString());
catch (Exception e)
Console.WriteLine(e.ToString());
try
myConnection.Close();
catch (Exception e)
Console.WriteLine(e.ToString());
Adelino Araujo

A network-related or instance-specific error occurred while establishing a connection to SQL Server.

Dear all,
I know that this topic may be a bit old school; but it really make me mad as I tried all solutions i found and it still cant be resolved....please give a hand...
The situation is like this,my company divided different platform as a status of project, like DEV, SIT and UAT. I got a project that require me to upgrade an vs2003 project to vs2005. I upgraded it completely and
successfully, it works fine in development and UAT platform; EXCEPT, the SIT platform.
The situation is very strange that, once I move the source to SIT, it return the following error:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections.
(provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
but it never happen in either DEV or UAT platform and even do I copy the workable web.config from DEV or UAT platform to SIT, the error still here and unable to resolve it.
I search a lot in the internet by Google, but solution suggested are not suitable or fail in my case. Most answer suggest that "enable remote control", "check fire wall", "check server" etc......But as I can connect well the
DBServer in DEV and UAT properly, I dont think those are the cause(but still, I check them all, and all are enabled properly, except my firewall setting is OFF, so adding port is ignored).
After all the searching and testing, I believed and have reason to believe that, the cause is inside my web.config:
<appSettings>


<clear/>
<add key="Environment" value="UAT v1.31"/>
<add key="DBServer" value="DB_UAT"/>
<add key="cnBPSS.ConnectionString" value="data source=DB_UAT\BPSS;persist security info=True;user id=theloginid;workstation id=RP_UAT;packet size=4096;pwd=theloginpwd"/>
<add key="UTBPSSConn.ConnectionString" value="data source=DB_UAT\BPSS;persist security info=False;user id=theloginid;workstation id=RP_UAT;packet size=4096;pwd=theloginpwd"/>
<add key="UTDSBDBConn.ConnectionString" value="workstation id=RP_UAT;packet size=4096;user id=theloginid;data source=DB_UAT\DSBDB;persist security info=False;password=theloginpwd"/>
<add key="cnDSBDB.ConnectionString" value="workstation id=RP_UAT;packet size=4096;user id=theloginid;data source=DB_UAT\DSBDB;persist security info=False;password=theloginpwd"/>
<add key="Timer1.Enabled" value="True"/>
<add key="Timer1.AutoReset" value="True"/>
<add key="cnbpss.ConnectionString" value="data source=DB_UAT\BPSS;password=theloginpwd;persist security info=True;user id=theloginid;workstation id=RP_UAT;packet size=4096"/>
<add key="cnbpss1.ConnectionString" value="data source=DB_UAT\BPSS;password=theloginpwd;persist security info=True;user id=theloginid;workstation id=RP_UAT;packet size=4096"/>
</appSettings>
</configuration>
I know such kind of setting is old school; But due to this program runs for few years from tons of ppl...I dont dare to modify it unless I am very sure they are the cause.....
May I ask if anyone cna give me some advice and help in this issue please? I already tried for weeks and turning mad....Please I really need some help...
Many thanks.
Ksun Chan

Checklist of possible reason of this error
1. Check SQL services are running
2. Check SQL Browser service is running
3. Check remote connections are enabled
4. Network connectivity between database & application servers by TRACERT command
5. Check TCP/IP protocol enabled at SQL server
6. Check talent connectivity – telnet <IP address> <port no on SQL server running>
7. Check UDP port 1434 is open or not on SQL Server
8. Check firewall is running or not Check
9. If firewall running, SQL Server & UDP port must be added in exception in firewall
Regards,
Rohit Garg
(My Blog)
This posting is provided with no warranties and confers no rights.
Please remember to click Mark as Answer and Vote as Helpful on posts that help you. This can be beneficial to other community members reading the thread.

Assigning database roles on SQL Server db

I am trying to set up a SQL Server adapter (not a database table adapter for SQL tables) to manage role assignment on a database 'test1' on my sql server ( 2000) 'sqlserver1' using IdM 7.1. I am trying to assign role1 to user tuser1 on test1. I am using 'sa' account so permissions should not be an issue.
Per resource reference document, I mapped:
userNametest1 <-> userNametest1
rolestest1 <-> rolestest1
My login for user 'tuser1' gets created on the SQL server. However the database and role assignment is not happening. I do not get any errors in the IdM admin pages from where I am testing this. Hence I am assuming I am not setting something right in the resource schema. I have tried different ways such as
userNametest1 <->userName
rolestest1 <-> roles
and some more combination but none seem to work. How can i find out what my resource attribute mapping should be? If anyone has done this, can you please share how you got it work?
Thanks in advance.

Some more info.
I have set up the out of the box MS SQL server adapter to connect to MSDE version of SQL server running on my local machine. I used the MSSQLServer Form provided in the samples folder and assigned it to an admin user and turned on the trace.
I am able to create logins by assigning the resource to a user. Using the admin user I am able to see in the trace that the server Roles are also being retrieved fine. What I am not able to get is assigning a database to the user and then assigning db roles.
Following the documentation (Resource Reference guide for IdM 7.1) I have created following attributes on the left hand side of schema.
defaultDB,serverRoles,domain, userNameMyTestDb,rolesMyTestDb.
No matter what I map the last two attribute I am not able to assign a db and dbroles to a user. I turned on sql profiler and then again used the admin user to view a test user using MSSqlServer form and it appears that the procedure sp_databases is not being called at all. I have decompiled the sql server class file and it appears there might be an issue with the way list of databases is being retrieved.
Has any one seen this before? If you were able to get it to work, can you please give me information on the resource schema and any other settings you had to make to get it to work?
Thanks in advance.

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] .

Connect Sql Server From Oracle Both on Windows

I want to connect my SQL Server running on Windows2003 with my oracle database 10g which is also on windows through some odbc which i have also created on my machine running oracle 10g. Can some one guide me with simple steps.

Generally most folks use OLEDB rather than ODBC for that.
If you have Metalink access, check out the following note:
Note.191368.1 Ext/Pub How to Create a Sql Server Linked Server With The Oracle Provider for OLE DB:
Hope it helps,
Greg

Merge Replication from 2012 SQL Server publisher/distributor to 2014 SQL Express subscriber

Hi, I'm having a question about which version to use when running SQL Merge Replication.
In my test enviroment I have a SQL 2012 server running as Publisher and Distributor for my Merge Replication. I have now set up a test client running Win7 with SQL 2014 Express as a subscriber. The subscription initializes and runs perfectly.
But according to the SQL documentation this should not be possible as it states that the subscriber should have a version number equal or lower than the publisher. My subscription client was set ut using SQL-scripting, if I try using the wizard it will just
cause an error message telling that this is not possible since the client has a newer version number. I still not encountered any problems after I set it up using the script with the sp_addmergepullsubscription and sp_addmergepullsubscription_agent procedures.
The roll-out of my solution will start in a few weeks and I now have to decide whether to use 2014 Express or 2012 Express on the clients. Using 2014 Express will save me for a lot of upgades in a year or two. The 2012 SQL Server running as publisher/distributor
will be upgraded to/replaced with a 2014 Server in some few months.
I'm looking for good advices and recommendations for what to choose on the clients, 2012 Express or 2014 Express. Are the any known problems with using 2014 Express as a subscriber to a publisher/distributor running 2012 SQL Server?
All responses are welcome!
Regards, Anders

Hi,
As you understand that a Subscriber to a merge publication can be any version less than or equal to the Publisher version. When you set up a subscription from a publisher to a subscriber using SQL Server Management Studio, you will get error
“The selected Subscriber does not satisfy the minimum version compatibility level of the selected publication.” And you can use T-SQL script to get around this error message.
I would install SQL Server 2012 Express on the clients. Here is the reasons:
1. If you upgrade the publisher to SQL Server 2014, it is still working with SQL Server 2012 on the subscriber.
2. I cannot tell whether there are other potential problems if I choose the later one besides the error message.
Reference:
http://msdn.microsoft.com/en-us/library/ms143699(v=sql.120).aspx
Thanks.
Tracy Cai
TechNet Community Support

MS SQL Server to Oracle

I am going to write all of the steps here that I have used trying to connect Oracle to MS SQL Server, so that others may benefit. I spent a few days using the following document, but in the end it turned out to be fairly incomplete, and I was frustrated by the amount of time that I had wasted.
"Using Heterogeneous Services"
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96544/admin.htm#169356
This document could be substantially improved with just three additions:
1. A clear distinction between tasks which are to be performed on the MS SQL Server hardware vs. the Oracle server,
2. More meaningful naming conventions in the examples instead of "Sybase_sales" and "SalesDB", that give you an idea of whether they refer to an Oracle Instance, a SQL Server Database, or something else,
3. Some mention of Oracle Transparent Gateway, and the fact that it needs to be installed for any of this to work.
I fully recognize the fact that I am still somewhat in the dark because I havn't gotten it to work yet; however, I wanted to mention that I began working for Oracle Consulting in 1990, and have been an independent Oracle Consultant since 1995. Therefore; the documentation for Heterogeneous Connectivity has not been adequate for a somewhat experienced Oracle developer.
Below are the steps that I have performed:

How to use TG4MSQL with MS SQL Server Instances
Microsoft introduced with MS SQL Server 2000 the concept of "instances".
All older releases (6.5 or 7.0) running on the same machine as a
SQL Server 2k act as a DEFAULT instance. The same is true for the first
installation of a MS SQL SERVER 2k on a PC.
All further installations of MS SQL Server 2k on the same machine are
named instances; this means a name must be provided during the
MS installation routine for this instance.
How to configure TG4MSQL in detail is described in
Note 231458.1 named HOW TO SETUP TG4MSQL
If there is only a default instance of MS SQL Server running, the parameter
HS_FDS_CONNECT_INFO is configured as:
HS_FDS_CONNECT_INFO = <server name>.<database name>
Method I:
This method is the fastest, but might cause problems if the MS SQL Server
is not listening on the default port. Give it a try, but if this method
causes troubles, please proceed to method 2.
The simplest way to work with instances is to specify the connect details in
the init.ora of the TG4MSQL.
The connect info contains the server name of the MS SQL Server, the instance
name and the database of the instance:
HS_FDS_CONNECT_INFO="<SERVER NAME>\\<INSTANCE NAME>.<DATABASE>"
If the server name is SQLSERVER and the instance name is instance2, the connect
string to the Northwind database looks like:
HS_FDS_CONNECT_INFO="SQLSERVER\\instance2.Northwind"
Similar to the description above is the connect information:
HS_FDS_CONNECT_INFO="SERVER=<SERVER NAME>\\<INSTANCE NAME>;DATABASE=<DATABASE>"
(HS_FDS_CONNECT_INFO="SERVER=SQLSERVER\\instance2; DATABASE=Northwind" )
Method II:
This method can be used also to connect to a MS SQL Server not listening
on the default port 1433.
It is based on using ALIASes:
If the MS SQL Server port or an alias is used instead of the servername,
the following registry key will be checked:
HKEY_LOCAL_MACHINE\
SOFTWARE\
Microsoft\
MSSQLServer\
ConnectTo
Microsoft provides a Client Configuration Tool to pass all parameters into the
registy (for example run PROFILER, click on options and execute the
Client Config Tool).
If there is no SQL Server client installed on the gateway machine, an idea
could be to configure it on the MS SQL Server, export the registry key and
import it again on the TG4MSQL machine. Please contact Microsoft about details.
This registry key is responsible for the connection details to the MS SQL Server.
While dealing with INSTANCEs or changing the MS SQL Server to listen on a
networking port other then 1433 (MS default port for SQL Server) the SUBKEY
ConnectTo is used to verify the connect details.
The Micrososft Client Configuration Utility configures ALIASes.
To work with a second instance of the MS SQL Server, an ALIAS for this
instance must be added.
This tool asks to choose a Serveralias (a name you can define on your own)
and to specify the Server name.
Normally the server name is equal to the IP address or to the hostname of
the MSQ SQL Server machine. But while working with instances the instance name
must be specified as well. The instance name is separated by TWO back slashes
from the server name.
For a better explanation the value for for the Server alias is "instance2alias" and
for the server name it is MSSQLSERVER. The sample name of the second instance is
INSTANCE2.
In the config tool type instance2alias into the entry filed of the server alias
and type MSSQLSERVER\\INSTANCE2 as server name.
Furthermore the default option is to figure out the MS SQL Server Ports dynamically.
If you do not want to detect them automatically, add the port of your SQL
Server is listening on; default is 1433. For this example port 1868 is used.
After applying this the ALIAS is saved into the registry:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo]
and it contains the following connect information:
"instance2alias"="DBMSSOCN,MSSQLSERVER\\INSTANCE2,1868"
The first parameter is the SQL Server alias, the second is a MS key word and
the next value is the hostname delimited by two back slashes from the instance
name.
Comment: Default instances do not have an entry here.
The last parameter is the port if it is not detected automatically.
If you have any questions about creating SQL Server aliases or what to
fill into the according columns, please contact Microsoft Support!
There is also a good note in the MS knowledge base:
Microsoft Knowledge Base Article - 265808
INF: How to Connect to an SQL Server 2000 Named Instance
with the Previous Version's Client Tools
Back to the Gateway configuration:
Oracle Transparent Gateway is able to work with MS SQL Server instances;
instead of specifying the <servername> at HS_FDS_CONNECT_INFO, the
<alias> must be specified.
For this example the parameter looks like:
HS_FDS_CONNECT_INFO = instance2alias.master

Lookout SQL Server Running at 100%

Similar Messages

Maybe you are looking for