Can I connect Azure SQL Database from Project Siena ?

Can I connect Azure SQL Database from Project Siena ?
I want to connect Azure SQL Database of Office 365 SharePoint's Access App from Project Siena.
Access App's Database is Azure SQL Database.
and can connect to Excel/PowerBI/etc.
Access App's Database can connect from specific location / any locations.
Access App's Database can allow read-only connection / read-write connection.
I want to create Windows App connected to Access App's Database.
Regards,
Yoshihiro Kawabata.

Hi Yoshihiro,
Could you share more with us about the high level scenario for what you are trying to accomplish offline? We can discuss further at
[email protected]
Once we are done, we will definitely share our findings with the community.
Thanks!

Similar Messages

  • How can I connect to a database from ipaq with cldc??

    how can I connect to a database from ipaq with cldc??

    Hi Again
    There is a library by Mimer which allows you do connect to a Mimer SQL Server, don't know must about it, but here is a link.
    http://developer.mimer.com/
    If that doesn't suit you, I suspect that you will have to use some sort of proxy solution. Either by creating a servlet to accept the sql string you want to send, or by creating your own custom proxy server running J2EE. The servlet or the proxy server must be able to receive an SQL String, do the query to the actual database and return the results in some sort of format to the mobile device. Maybe just a space delimited string.
    Hope this helps
    -Daur

  • Consistently getting "The wait operation timed out" when connecting to Azure SQL Database from a virtual instance...

    I have a web app that is backed by a an Azure SQL Database. The problem is that I had multiple issues when connecting to the database mainly when trying to establish a connection, or timeouts. This is the log I just encountered when trying to use the web
    app.
    [Win32Exception (0x80004005): The wait operation timed out]
    [SqlException (0x80131904): Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in time. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=21970; handshake=1; ]
    System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection) +671
    System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection) +116
    System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection) +1012
    System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions) +6712291
    System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry) +152
    System.Data.SqlClient.SqlConnection.Open() +229
    System.Data.EntityClient.EntityConnection.OpenStoreConnectionIf(Boolean openCondition, DbConnection storeConnectionToOpen, DbConnection originalConnection, String exceptionCode, String attemptedOperation, Boolean& closeStoreConnectionOnFailure) +102

    Hi Affar2k,
    According to your description, we need to verify if there is no network issue and the Sqlclient version is older than .NET 4.5.  You can try to connect to the Windows Azure SQL database via SSMS and check if it can run well. When you
    connect to the SQL Azure database via ADO.NET, you need to verify that the server name and passwords are right in the connection string.
    For more information, you can review the following article about how to connect to Windows Azure SQL Database using ADO.NET.
    http://msdn.microsoft.com/en-us/library/windowsazure/ee336243.aspx
    Thanks,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • Can't connect to SQL Database using new login

    I can connect to Azure SQL Database using the admin ID created when I set up the Azure account.  Now I want to set up a different login that has only regular read/write privileges.  I have followed the instructions on several web posts, to create
    a login at the server level, then create a user at the database level from the login.  When I try to connect, though, the connection fails.  I get an error message, and a GUID that I am supposed to supply to MS tech support, except that all I have
    is a standard Azure subscription, which does not include tech support.
    Here is what I have done so far:
    Logging in to the server with the admin account with SQL Mgmt Studio, I go to the master database on my Azure server, and create the login:
    CREATE LOGIN clouduser@gxw8x04nlb with PASSWORD = 'xoxoxoxo';
    This appears to work (password supplied is a "strong" password), or at least it doesn't show any error response.
    Then, connecting to the production database in Azure, I set up a user and set permissions as follow:
    CREATE USER clouduser1 FROM LOGIN clouduser@gxw8x04nlb;
    EXEC sp_addrolemember 'db_datareader', 'clouduser1'
    EXEC sp_addrolemember 'db_datawriter', 'clouduser1'
    When I attempt to connect to Azure using the new login, however, I get an error message (from SQL Mgmt Studio as well as from MS Access).  I am using the SQL Server Native Client 10.0.
    The message is:
    Connection failed:
    SQLState '28000'
    SQL Server Error 18456
    [Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user 'clouduser'.
    Connection failed:
    SQLState: '01000'
    SQL Server Error: 40608
    [Microsoft][SQL Server Native Client 10.0][SQL Server]This session has been assigned a tracing ID of
    '271851d5-8e94-497c-a332-d9d40682bb7a'.  Provide this tracing ID to customer support when you need assistance.
    Is there some missing step I need to do, to permit the login to see the database?  I have looked for such in the various discussions about connection problems, but have not been able to find such a thing.   Or extend more permissions to the new
    user? Or specify a default user ID for a given login ?  (as they do not have the same names, in the examples I have seen).  I tried making the user ID the same as the login (w/o the server name), but that didn't seem to help, either.
    I have done numerous web searches, and tried about every variation of login or user ID, password, etc. that I can think of, and all of them encounter the same error.  It's got to be something very simple - clearly Azure supports more than one login
    per database.  But's that's all I have at the moment.  That login connects just fine, but others won't, using the same PC, middleware, IP address, etc.
    Any help would be much appreciated -
    Thanks,
         Doug

    Olaf -
    I noticed that, but all of the examples I have seen have Users named slightly differently from the Logins.  I did try logging in with the Login name instead.  No good.  I tried making the Login and the User name the same (clouduser).  Also
    no good - same symptoms.
    I think the problem is that the initial creation of the Login needs to be done WITHOUT the server name on the end.  
    Logged in to the master DB, I tried:  Create LOGIN clouduser@gxw8x04nlb with PASSWORD = 'xoxoxoxo';
    That didn't give me an error message, but I think it created a LOGIN of 'clouduser@gxw8x04nlb'.  When
    referenced from the outside world, I would need to specify 'clouduser@gxw8x04nlb@gxw8x04nlb'.
    I tried deleting the logins, and then creating the login 'clouduser' in the Master DB.  Then in
    the application DB, I created User clouduser from LOGIN clouduser, and then assigned a role.  That seems to work!
    In my connection string, File DSN, etc. I still need to supply the login as 'clouduser@gxw8x04nlb'.
     But when I am logged in to the server, and working in the Master DB or the application DB, I just refer to the Login as 'clouduser'.  
    Seems a little more complicated than it really should be, but at least I now have something that works.
    Doug
    Doug Hudson

  • I can't connect to MySQL database from The JSP Standard Tag Library

    Hi All !
    I have a problem, please help me anybody !
    I don't connect to MySQL database from jsp page using JSTL tag but from servlet all work correctly. I set my path and put �mysql-connector-java-3.1.13-bin.jar� in ENVIRONMENT WinXP(classpath=C:\Java\jdk1.5.0_10\jre\lib\ext\mysql-connector-java-3.1.13-bin.jar) and in War project folder �WEB-INF/lib� and in [TomcatServer]\common\lib.
    I have in folder�WEB-INF/lib� following files:
    antlr.jar
    commons-beanutils.jar
    commons-collections.jar
    commons-digester.jar
    commons-fileupload.jar
    commons-logging.jar
    commons-validator.jar
    jakarta-oro.jar
    jsf-api.jar
    jsf-impl.jar
    jstl.jar
    mysql-connector-java-3.1.13-bin.jar
    standard.jar
    struts.jar
    I'm using:
    NetBeans 5.5 Build200610171010 (bundled Tomcat 5.5.17)
    Ent.Pack 20061020 Visual Wb Pack 061103
    OS WinXP SP2
    Java 1.5.0_10
    MySQL 5.0.18-nt
    1:<%@page contentType="text/html"%>
    2:<%@page pageEncoding="UTF-8"%>
    8: <%@taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c"%>
    9: <%@taglib uri="http://java.sun.com/jstl/sql" prefix="sql"%>
    10:
    11: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
    12: "http://www.w3.org/TR/html4/loose.dtd">
    13:
    14: <sql:setDataSource var="ds"
    15: driver="com.mysql.jdbc.Driver"
    16: url="jdbc:mysql://localhost:3306/test"
    17: user="root"
    18: password="xxxx"/>
    19:
    20:
    21:<sql:query sql="select name, age from People" var="res"
    22: dataSource="${ds}"/>
    I have received report on mistake when entered code at the top:
    �/index.jsp [21;0] According to TLD or attribute directive in tag file, attribute dataSource does not accept any expressions�
    I used instead of (dataSource="${ds}")->(dataSource="ds") but this did not work.
    After build and run I have received
    =========================================START=================================
    HTTP Status 500
    type Exception report:
    message
    description The server encountered an internal error () that prevented it from fulfilling this request.
    exception
    org.apache.jasper.JasperException: /index.jsp(21,0) According to TLD or attribute directive in tag file, attribute dataSource does not accept any expressions
    org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:510)
    org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:375)
    org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
    org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
    org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:368)
    root cause
    org.apache.jasper.JasperException: /index.jsp(21,0) According to TLD or attribute directive in tag file, attribute dataSource does not accept any expressions
    org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:39)
    org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:405)
    org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:146)
    org.apache.jasper.compiler.Validator$ValidateVisitor.checkXmlAttributes(Validator.java:955)
    org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:710)
    org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1441)
    org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2163)
    org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2213)
    org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2219)
    org.apache.jasper.compiler.Node$Root.accept(Node.java:456)
    org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2163)
    org.apache.jasper.compiler.Validator.validate(Validator.java:1489)
    org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:166)
    org.apache.jasper.compiler.Compiler.compile(Compiler.java:295)
    org.apache.jasper.compiler.Compiler.compile(Compiler.java:276)
    org.apache.jasper.compiler.Compiler.compile(Compiler.java:264)
    org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:563)
    org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:303)
    org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
    org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
    org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:368)
    note The full stack trace of the root cause is available in the Apache Tomcat/5.5.17 logs.
    Apache Tomcat/5.5.17
    =======================================END================================
    Error: "According to TLD or attribute directive in tag file, attribute dataSource does not accept any expressions" - but according to documentation such parameter possible.
    BUT WHEN JOINING With DATABASE FROM SERVLET ALL WORK FINE.
    I read this doc - [http://tomcat.apache.org/tomcat-5.5-doc/jndi-datasource-examples-howto.html], this applicable if I Tomcat Admin, but i'am not Admin
    I simply user, i.e. I want to place its database on virtual host (Tomcat+(JSP-JSTL)+MySQL).
    There is idea how can resolve this problem
    Thank you in advance ;)

    For all how have similar problem.
    Decision instead of these ways
    <%@ taglib prefix="c" uri="http://java.sun.com/jstl/core" %>
    <%@ taglib prefix="sql" uri="http://java.sun.com/jstl/sql" %>
    it is necessary to indicate these
    <%@ taglib prefix="sql" uri="http://java.sun.com/jsp/jstl/sql" %>
    <%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core" %>

  • Yesterday I was able to connect Azure SQL Database - Today I am not

    Hello Everyone,
    I have problem with establishing connection with Azure SQL Database. I have read many articles here, tried some solutions but none worked.
    0. On last Friday everything worked well - today it does not.
    1. I added my public IP Address in Azure Management Portal earlier.
    2. I tried different types of login-ways: login@nameserver, I used numeric addresses instead of server names, I set TCP connection manually, added encryption in one case either, tried do establish connection with particular database
    3. Firewall does not block 1433 out connection
    4. My IP address is static
    5. I have no error message displayed using Microsoft SQL Server Management Studio - it just hangs.. - no response at all
    6. I cannot ping the machine but its name is resolved correctly - maybe it does not respond using echo reply on purpose
    7. Status of my database is Active - I am able to connect it and manage via browser and management portal at the moment
    8. When I am trying to connect database via Visual Studio - it hangs.. - VS must be stopped manually via task manager
    9. My local CloudService has problem with connection to the db either
    10. Currently I am not able to deploy my CloudService because when I am trying to Publish it - VS hangs as soon as first Publish dialog window appears. Looks that I am able to deploy cloud service via Management portal only.
    I am still trying to dive into the problem but at this moment I would be grateful for any clues.
    Regards,

    Hi Mekh, hi everyone
    PROBLEM SOLVED.
    Yestarday I updated Azure Firewall rule and database-level firewall rules (master, my_database). I added special input / output protocols (IP, TCP, UDP) rules to my COMODO firewall (MSSMS could send anything and receive anything using IP, TCP and UDP). Status
    of my computer -> database connection was set to ESTABLISHED in netstat output but MSSMS was still unavailable (no response at all - no error message).
    I DECIDED TO UNINSTALL COMODO AT ALL and then if it does not work - reinstall local SQL Server, MSSMS and finally Visual Studio. When Comodo was gone - problem was gone either. Now I have connection with my database using MSSMS and I do not have to reinstall
    anything more.
    Regards,

  • Connecting to an Azure SQL Database from a Windows C# Form

    Hi,
    Is it possible to connect to an SQL database in Azure from Visual Studio C# 2010 or 2012? If so how is this done. Is it the same as if you were connecting to SQL Express database with the use of a connection string? Any directions or tutorials would be of
    great help!
    Thanks!

    Hi,
    >>Thanks for the reply Paul, That is disappointing. I am trying to get my students to create a C# application that will connect with a database in Azure. Is there another approach besides SQL that I could use?
    Using SQL Azure will work fine (see below), if the students are familiar with SQL Server and SQL Databases it will be great for them to see how it works in the cloud. As an alternative you could explore Azure Storage, using Table Storage, Blob Storage or
    the new Document Database features.
    >>Azure enforces a firewall that prevents direct external access to the database server. You can add a firewall rule allowing external access, but the rules only support connecting from a fixed IP address because you have to specify the numeric IP
    from which connection will be allowed.
    You can specify ranges here, so you could cover a range of IP addresses. You can even specify 0.0.0.0 to 255.255.255.255 and allow all IP addresses, this could be an option if you don't know where the students will be connecting from, and you are using a
    database for the exercise where you don't care too much about the security.
    When I have run classes I typically use an IP address range, for example XXX.YYY.ZZZ.0 to XXX.YYY.ZZZ.255 if the students are accessing from the same classroom, and the external IP address may vary. You may find that they all have the same external IP address
    if they are on the same internal network.
    Also, with many students accessing the same database, you may get throttling if they place a lot of load on it. This is cool, as you can also teach them about transient fault handling and resource throttling :-).
    Regards,
    Alan
    Free e-book: Windows Azure Service Bus Developer Guide.

  • Connecting to an Azure SQL Database from VB6

    We have an old Application that is accessing a database located on a client site. We currently access this database using ADO and SQL Authentication. Would it be possible to migrate to Azure SQL Server and connect to it from the VB6 Application by just changing
    the connection string?

    Yes, but you have to make sure that you are not using any features that SQL Azure doesn't support. And make sure that the SQL Azure server address is open for connection from outside. You also need to be concerned about data security.
    Frank

  • How can i connect to remote database from netbeans

    Hi,
    I have got MySQL database server installed and running on a different machine. Is there any way to connect and browse database remotely using netbeans 5.5?
    I have added connector/driver for that database. i can connect and browse the database with host: "localhost" and port number. But when i specified the ip address of that machine, it gives me error.
    Can anyone help please.
    cheers.

    well, its not working in App server either.
    In App server admin console, on that connection pool if i define servername as "localhost", it works fine. If i change it to the remote machine's ip address, then it doesn't work.
    Any idea will be appreciated.
    cheers.

  • Running an older Visual Studio app on Server 2012R2 can't connect to SQL Database

    I have a database driven app written in Visual Studio 2005 or the release before.
    It works fine on windows xp, 7x64, server 2008R2.
    I installed on Server 2012R2, and it will not connect to the database. (which is a SqlServerExpress2014 database)
    System>Runtime.InteropServices.COMException (0x80004005): [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified at ADODB.ConnectionClass.Open(String ConnectionString, Strin UserID, String Password, Int32 Option) an
    ####.ModGlobal.OpenDB()
    1. My connection string is: Provider=SQLOLEDB.1;Password=XXXXX;Persist Security Info=True;User ID=sa;Initial Catalog=BuilderVT;Data Source=ENET-2012R2\SQLEXPRESS
    > I created & verified this as in a UDL file with OLEDB Core Services- the connection tested OK.
    > I used this same string on a Win7 system, and it connects to the database fine
    > I tried connecting to an older database on another system, and it fails.
    I suspect that there's a 32 to 64 bit mismatch, but, am lost at the moment

    My connection string is: Provider=SQLOLEDB.1;Password=
    Hello,
    Please lookup in Windows Registry if you have a key "HKEY_CLASSES_ROOT\SQLOLEDB.1" and/or HKEY_CLASSES_ROOT\SQLOLEDB". If you have only SQLOLEDB, then remove .1 from the Connection string.
    Olaf Helper
    [ Blog] [ Xing] [ MVP]

  • How can I connect to Oracle database from Iplanet webserver running on a Linux box and a database running on a Solaris box?

    Hi - I'm new to this group and wonders whether you guys can help me.
    I'm trying to connect to my Oracle9i database via a Java servlet but
    got the following error message in the web browser:
    Internal error: exception thrown from the servlet service function
    (uri=/servlet/HelloWWW6): java.lang.NullPointerException, Stack:
    java.lang.NullPointerException
    at oracle.jdbc.oci8.OCIDBAccess.check_error(OCIDBAccess.java:1743)
    at oracle.jdbc.oci8.OCIEnv.getEnvHandle(OCIEnv.java:69)
    at oracle.jdbc.oci8.OCIDBAccess.logon(OCIDBAccess.java:452)
    at oracle.jdbc.driver.OracleConnection.(OracleConnection.java:287)
    at oracle.jdbc.driver.OracleDriver.getConnectionInstance
    (OracleDriver.java:442)
    at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:321)
    at java.sql.DriverManager.getConnection(DriverManager.java:512)
    at java.sql.DriverManager.getConnection(DriverManager.java:172)
    at HelloWWW6.doGet(HelloWWW6.java:40)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at
    com.iplanet.server.http.servlet.NSServletRunner.invokeServletService
    (NSServletRunner.java:897)
    at com.iplanet.server.http.servlet.NSServletRunner.Service
    (NSServletRunner.java:464)
    My class path is:
    Java VM
    classpath: /u01/iplanet/servers/plugins/servlets/examples/legacy/beans
    .10/SDKBeans10.jar:/usr/local/javamail-1.2/mail.jar:/usr/local/jaf-
    1.0.1/activation.jar:/u02/app/oracle/product/9i/lib:/u02/app/oracle/pr
    oduct/9i/jdbc/lib:/u02/app/oracle/product/9i/jdbc/lib/classes12.zip:/u
    02/app/oracle/product/9i/jdbc/lib/nls_charset12.zip:/u01/iplanet/serve
    rs/bin/https/jar/NSServletLayer.jar:/u01/iplanet/servers/bin/https/jar
    /NSJavaUtil.jar:/u01/iplanet/servers/bin/https/jar/NSJavaMiscUtil.jar:
    /u01/iplanet/servers/bin/https/jar/servlet.jar:/u01/iplanet/servers/bi
    n/https/jar/servlet-2.3-filters-
    api.jar:/u01/iplanet/servers/bin/https/jar/jsp092.jar:/u01/iplanet/ser
    vers/bin/https/jar/jaxp.jar:/u01/iplanet/servers/bin/https/jar/crimson
    .jar:/u01/iplanet/servers/bin/https/jar/xalan.jar:/u01/iplanet/servers
    /bin/https/jar/jspengine.jar:
    My LD_LIBRARY_PATH is:
    /u02/app/oracle/product/9i/lib:/u02/app/oracle/product/9i/jdbc/lib:/u0
    2/app/oracle/product/9i/jdbc/lib/classes12.zip:/u02/app/oracle/product
    /9i/jdbc/lib/nls_charset12.zip
    Can anyone help? This is currently driving me nuts. I was able to
    connect when I changed it to an application.
    I am using the Iplanet Webserver 6.0 on a Linux 7.2 platform. Like I
    said, sqlplus works fine, standard java application works fine but
    when I change it to a servlet (which means it now goes through the
    webserver, I get this error message)
    Does anyone know what the source code is trying to do at
    OCIDBAccess.java:1743 ?
    Thanks guys!

    Tony, could you please explain me better the procedure that you wrote?
    What are the boxes? My situation is similar:
    | ServerSocket (1) |
    | (192.168.1.100, 5555) |
    |
    |
    |
    |
    | Proxy |
    | Someone wants to connect to the ServerSocket (1) |
    That is not true. You CAN do it but you need a box
    outside the firewall with proper IP address to help
    you. I am not sure if Sergio still wants the answer
    today after more than a year from the original post (I
    did not see the post until today when I try to search
    for something else). Anyway, if such a box is
    available (I call it 2nd box), you could first
    establish a socket between the two boxes by HTTP
    tunneling (I assume it is a http proxy). You have to
    initiate the socket from the 1st box. Then start
    another server socket on the 2nd box, forwarding the
    traffic it gets from outside back to the 1st box using
    the established channel. That is it.
    Tony

  • Unable to connect the SQL database from servlet

    Hi!
    My servlet connects with an SQL server on some other machine.
    I have create the servlet and deploy it on tomcat.
    I first create this servlet on eclipse that I deploy it on tomcat manually.
    While using it form eclipse it gave no error in connecting with the server.
    But when I deploy the same code on tomcat manually and access the page it gave me an error saying
    [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'
    I used the following code for cenneting the server
    Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
                   out.println("Calling For Class Name success Now calling database <br>");
                   jdbcConnection = DriverManager.getConnection("jdbc:odbc:Driver={SQL Server};Server=MyServerName;Database=MyDatabaseName","","");
    Message was edited by:
    nitin403

    Hi!
    Sorry for not formating my previous message properly.
    My servlet connects with an SQL server on some remote machine.
    I have create the servlet and deploy it on tomcat.
    I first create this servlet on eclipse that I deploy it on tomcat manually.
    While using it form eclipse it gave no error in connecting with the server.
    But when I deploy the same code on tomcat manually and access the page it gave me an error saying
    [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'
    I used the following code for connecting the server
    Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
    jdbcConnection = DriverManager.getConnection("jdbc:odbc:Driver={SQL Server};Server=MyServerName;Database=MyDatabaseName","","");
    Thanx for your help in advance
    Message was edited by:
    nitin403

  • Can SQL Server SSIS on VM access Azure SQL database?

    I have SQL Server BI on Azure VM.
    Can SSIS Access Azure SQL database? I need to fetch data.
    Kenny_I

    Hi,
    You an able to do this by running ssis locally and connect Azure SQL. Below link expains this well in detail.
    http://beyondrelational.com/modules/2/blogs/84/posts/13234/how-to-use-sql-server-integration-services-ssis-to-migrate-data-from-sql-server-to-sql-azure-paras-d.aspx
    Regards,
    Santhosh.
    www.jijitechnologies.com

  • Can No Longer Connect to Azure SQL Databases

    As of this morning, I am no longer to connect to any of my Azure SQL databases by any (apparent) means. I checked the configuration in the azure portal and my IP address is listed as an allowed IP, however:
    I am unable to connect via SQL Server Management Studio
    My request times out when attempting to visit https://{server_name}.database.windows.net
    What might have caused this?

    Hi ,
    Thanks for posting here.
    To resolve the issue you can try the following steps (in that order):
                    Check the application’s connection string to make sure that it is correctly configured. For example, make sure that the connection string specifies the correct port
    (1433) and the fully qualified server name.                
    Note You can follow these steps to obtain the connection string from the Azure Management Portal:                  
                          Log on to the
    Azure Management Portal.                    
                          In the left navigation pane, click
    SQL Databases.                    
                          Select your Azure SQL Database server.                    
                          Click
    Dashboard.                    
                          On the right side, go to the
    quick glance section, and then click Show connection strings.                    
                    Make sure that TCP IP is enabled as a client protocol on the application server. For more information on how to do this, see
    Configure client protocols. On application servers where you do not have SQL Server tools installed, you can check this by running cliconfg.exe (SQL Server Client Network Utility).              
                    Test the connectivity between the application server and the Azure SQL database by using a UDL file, ping, and telnet. For more information about how to do this,
    see
    Azure SQL Database connectivity troubleshooting guide and
    Troubleshooting SQL Server connectivity issues.                
    Note As a troubleshooting step, you can also try to test the connectivity on a different client computer.                
                    Try increasing the connection
    timeout. Microsoft recommends using a connection timeout of at least 30 seconds.              
                    As a best practice ensure retry logic is in place. For more information about the retry logic, see
    Azure SQL Database best practices to prevent request denials or connection termination.              
                  If the previous steps do not resolve your problem, follow these steps to collect more data and contact support:              
                      If your application is a cloud service, enable the logging. This step returns a UTC time stamp of the failure. Additionally, SQL Azure returns the tracing
    ID.
    Microsoft Customer Support Services can use this information.                
                      For more information about how to enable the logging, see
    how to enable diagnostic logging for Azure Web sites and Developing SQL Database Applications section in
    Azure SQL Database Development Considerations.
    Please write back with the exact Error message/ Error Code if this doesn't help.
    Regards,
    Shirisha Paderu.

  • Cannot Connect to Azure SQL Database in Visual Studio 2013

    Beyond Frustrated here.
    I am trying to connect to an Azure SQL database - it has been created, has tables etc. I am trying to create a new Data Connection from within Visual Studio 2013, latest release for VS and Azure. I continue to receive 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)
    I have ensured that TCP is allowed and above Named Pipes in the Configuration Manager. The associated IP address is allowed on Azure Firewall. Certificate has been added to VS etc. But still no connection. I can see the database in the Azure section in Server
    Explorer, but cannot add a Data Connection. What is equally as frustrating is I have a MacBook Pro running Win 7 sitting right next to my office computer and it can access Azure fine, not problems.
    If anyone has any other ideas on how I might be able to solve this I would love to hear them. Thanks in advance.
    Jeff

    Hi,
     The Error message "   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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53) "
    The issue comes up mainly because the application is not able to connect to the server.
    To resolve this issue, try the following steps (in that order):
     Make sure that TCP IP is enabled as a client protocol on the application server. For more information on how to do this, see
    Configure client protocols. On application servers where you do not have SQL Server tools installed, you can check this by running cliconfg.exe (SQL Server Client Network Utility).              
     2.  Check the application’s connection string to make sure that it is correctly configured. For example, make sure that the connection string specifies the correct port (1433) and the fully qualified server name.                
    Note You can follow these steps to obtain the connection string from the Azure Management Portal:                  
                          Log on to the
    Azure Management Portal.                    
                          In the left navigation pane, click
    SQL Databases.                    
                          Select your Azure SQL Database server.                    
                          Click
    Dashboard.                    
                          On the right side, go to the
    quick glance section, and then click Show connection strings.                    
    Test the connectivity between the application server and the Azure SQL database by using a UDL file, ping, and telnet. For more information about how to do this, see
    Azure SQL Database connectivity troubleshooting guide and
    Troubleshooting SQL Server connectivity issues.                
    Note As a troubleshooting step, you can also try to test the connectivity on a different client computer.                
    Try increasing the connection timeout. Microsoft recommends using a connection timeout of at least 30 seconds.              
    As a best practice ensure retry logic is in place. For more information about the retry logic, see
    Azure SQL Database best practices to prevent request denials or connection termination.              
          If these  steps do not resolve your problem, follow the below steps to collect more data and contact support:              
       If your application is a cloud service, enable the logging. This step returns a UTC time stamp of the failure. Additionally, SQL Azure returns the tracing ID.
    Microsoft Customer Support Services can use this information.                   
       For more information about how to enable the logging, see
    how to enable diagnostic logging for Azure Web sites and Developing SQL Database Applications section in
    Azure SQL Database Development Considerations.                
      Check out
    the list of best practices for Connecting to Windows Azure SQL Database.
    Regards,
    Shirisha Paderu.

Maybe you are looking for