Warning: Creating default object from empty value in /home/agilemed/aendeavors.com/wp-includes/ms-load.php on line 138

Warning: session_start(): Cannot send session cookie - headers already sent by (output started at /home/agilemed/aendeavors.com/wp-includes/ms-load.php:138) in /home/agilemed/aendeavors.com/wp-content/plugins/amazon-product-in-a-post-plugin/amazon-product-in-a-post.php on line 102

Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /home/agilemed/aendeavors.com/wp-includes/ms-load.php:138) in /home/agilemed/aendeavors.com/wp-content/plugins/amazon-product-in-a-post-plugin/amazon-product-in-a-post.php on line 102
Deploying to SQL Azure » Agile Tech




Deploying to SQL Azure

Warning: file_get_contents(https://ecs.amazonaws.com/onca/xml?AWSAccessKeyId=AKIAILRMGOER5ORIOURA&AssociateTag=agile08-20&IdType=ASIN&ItemId=1430229616&Operation=ItemLookup&ResponseGroup=ItemAttributes%2CImages%2COffers&Service=AWSECommerceService&Timestamp=2017-03-29T11%3A06%3A28Z&Version=2009-03-31&Signature=URSKNPxyhDuws6GgbtrFnS84QJypzcmBe6rhDbf6TOY%3D): failed to open stream: HTTP request failed! HTTP/1.1 400 Bad Request in /home/agilemed/aendeavors.com/wp-content/plugins/amazon-product-in-a-post-plugin/inc/aws_signed_request.php on line 404

SQL Azure and SQL Server Management Studio

During our migration from SQL Express which we had been using for development to SQL Azure, we were having issues connecting to the deployment from SQL Server Managment Studio. If you’re running into issues connection with Management Studio, try the following:

  1. Server Name: Should be the instance name from the Azure web interface (servername.database.windows.net)
  2. Login: Should be your username, as of this post, appending @host was unnecessary for a successful connection from Studio 2008 R2
  3. Before logging in, click on the “Options” button and select the “Connection Properties” tab. Under “Connect to database”, type in the name of your database. Leaving it set as <default> will result in a failed connection
  4. Try a different physical location. Many locations (hotels, airports, schools) block outgoing database connections. If you’re receiving a message like the one below, it’s possible that your current location has an outgoing port blocked:
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)

Leave a Reply

Your email address will not be published.


You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>