Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook
Devcon 2020 Goes Virtual! LEARN MORE >

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

AlphaDAO connection to remote SQL Server

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    AlphaDAO connection to remote SQL Server

    I need to connect to a remote SQL Server that is configured to use TCP/IP (not named pipes). It appears that A5's connection string builder assumes named pipes. The connection string I use from .NET projects is:

    Data Source=Server1;Failover Partner=Server2;Network Library=DBMSSOCN;Initial Catalog=DBName;User ID=xxx;password=yyy

    I tried just using this directly (without using the connection string builder) but it appears (I'm new to A5) that A5 wants the key/value pairs spoon fed to it in a particular format (at least the error message is meaningful and gave me a couple of options). So I did this instead:

    Data Source='Server1',Failover Partner='Server2',Network Library='DBMSSOCN',Initial Catalog='DBName',User ID='xxx',password='yyy'

    When I attempt to test this connection it returns "Could not connection. Error reported was: The SQL API you requested is not installed" (Someone might want to note the grammatical errors in this message and correct them.)

    I don't know where to go with this. I Googled this particular error and a couple of people indicated it went away when they restarted A5 and someone suggested installing SQL Server express on the client running A5. I did the both, and rebooted the client as well (Window 7 x64 Ultimate) but no joy.

    I can connect to this SQL Server fine using ODBC (SQL Server native client). I can also use the resulting ODBC System DSN from A5 but I presume that this would just treat it as a generic ODBC database with some attendant limitations and possibly a performance hit of some kind. My client is unwilling to allow named pipes for remote connections. So ... I need to get this puppy working with TCP/IP. This doesn't seem like it should be rocket science and I don't see why it should be a problem for A5 if it's not for legacy ODBC.

    Can anyone help with this?
    Tags: None
    #2
    Re: AlphaDAO connection to remote SQL Server

    Hm ... I just tried this again with the connection string builder, which originally gave me the "API not installed" message, which is why I assumed it was somehow specific to named pipes. This time it worked. The difference probably is that I've since systematically worked through various checks and have installed the latest drivers and made sure the firewalls were open on both ends to port 1433.

    Now I have only one question, which is how to specify the equivalent of "Failover Partner" in my original .NET connection string, as this is not part of the GUI for building a connection string. A5 doesn't need to specifically support mirroring, it just needs to specify the failover server name in the connection string.

    Here's the successful connection that came out of the builder that I'll need to modify:

    {A5API='SQLServer','A5DBVersion=2005,Server='Server1',A5ANSINullPadWarn=Default,UserName='xxx',Password='(encrypted gobbeldygook)',Database='MyDataBase'}

    What's the key for the failover partner server name?

    By the way -- I'm using the latest (March 10) patch of v11.

    Comment

      #3
      Re: AlphaDAO connection to remote SQL Server

      I still need to know the answer to the question in my second post, but for anyone else who's curious what what actually happens if you don't specify a failover partner, take a look here:

      http://blogs.msdn.com/b/spike/archiv...ror-setup.aspx

      The short version: everything is fine so long as the Principal is up and running when you initially connect. The problem is that you can't connect when the Principal and Mirror have been swapped. The only purpose of putting the Mirror server name in the connection string is to cover that scenario. Otherwise the client (A5 in this case) gets passed the name of the Mirror by Sql Server itself, provided it can connect successfully to the Principal.

      So I'm good for testing purposes, just not production purposes.

      Comment

      Previous template Next
      Working...
      X