Anmelden
 
HomeLibraryDownloadsSupportWebcasts & EventsCommunityForenBlogs
Ressourcen für IT-Professionals >
> 
> 
GPP Data Sources - SQL With Username & Password

Beantwortet GPP Data Sources - SQL With Username & Password

  • Mittwoch, 4. April 2012 08:59
     
     
    Anmelden
    0

    Hi,

    I have been attempting to configure a SQL ODBC data source via GPP and just keep failing. After a lot of searching it appears as though the SQL data source does not recognise having a username and password.

    So, my question is: If I need to create a SQL ODBC data source via GPP which has to have a username and password attached, how can I do it? Is it even possible?

    Thanks.

    Pete.


    • Bearbeitet pshankland Mittwoch, 4. April 2012 08:59
    •  
     

Alle Antworten

  • Donnerstag, 5. April 2012 02:34
    Moderator
     
     
    Anmelden
    0
     

    Hi,

    According to the problem description, this issue is related to SQL Server. For SQL Server issue, the best resource is SQL Server forum.

     

    Based on the current situation, you’d better submit a new question to SQL Server forum for further assistance. In this way, your issue can be resolved effectively.

    SQL Server

    http://social.technet.microsoft.com/Forums/en-us/category/sqlserver

    Thanks for your understanding!

    Regards,

    Arthur Li

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.

    Arthur Li

    TechNet Community Support

     
  • Donnerstag, 5. April 2012 07:06
     
     
    Anmelden
    0
     
    > After a lot of searching it appears as though the SQL data source does
    > not recognise having a username and password.
     
    Seems your search engine was broken at the time ((-:
     
     
    sincerely, Martin
     
    NO THEY ARE NOT EVIL, if you know what you are doing: Good or bad GPOs?
    Wenn meine Antwort hilfreich war, freue ich mich über eine Bewertung! If my answer was helpful, I'm glad about a rating!
     
  • Donnerstag, 5. April 2012 10:51
     
     
    Anmelden
    0
     
    > After a lot of searching it appears as though the SQL data source does
    > not recognise having a username and password.
     
    Seems your search engine was broken at the time ((-:
     
     
    Think you need to read the URL's you post as the author talks about that working with trusted connections and my question was about having to use a static username and password. So, not a helpful post.
     
  • Donnerstag, 5. April 2012 10:54
     
     
    Anmelden
    0

    No, this is nothing to do with a SQL Server issue as I can manually create the ODBC data source with no problems. The issue appears when I try to use a GPP to deploy the ODBC data source.

    The ODBC data source in question uses a default username and password to connect to the table, it is not based on the users own credentials. Therefore the question is still valid within this forum: Can I add a username and password to a GPP ODBC data source for SQL?

    Thanks.

     
  • Donnerstag, 5. April 2012 11:10
     
     
    Anmelden
    0
     
    > Think you need to read the URL's you post as the author talks about
    > that working with trusted connections and my question was about having
    > to use a static username and password. So, not a helpful post.
     
    Let me cite a sentence on this site: The problem is, because of the not
    scriptable
    password in MS SQL Driver. Acces/MySQL whatever will work :-)
     
    Maybe that doesn't help you out, but will explain the DSN failure in GPP.
     
    On the other hand, maybe I'm totally wrong (-:
     
    sincerely, Martin
     
    NO THEY ARE NOT EVIL, if you know what you are doing: Good or bad GPOs?
    Wenn meine Antwort hilfreich war, freue ich mich über eine Bewertung! If my answer was helpful, I'm glad about a rating!
     
  • Donnerstag, 5. April 2012 16:23
     
     
    Anmelden
    0
     
    > Think you need to read the URL's you post as the author talks about
    > that working with trusted connections and my question was about having
    > to use a static username and password. So, not a helpful post.
     
    Let me cite a sentence on this site: The problem is, because of the not
    scriptable
    password in MS SQL Driver. Acces/MySQL whatever will work :-)
     
    Maybe that doesn't help you out, but will explain the DSN failure in GPP.
     
    On the other hand, maybe I'm totally wrong (-:

    I know what the website says as found it linked on a number of occasions while I was searching. I posted here because I thought I would get an answer as to if there was a way to to use a username and password now as the post was made on August the 14th 2008!!

    Things, I hoped, would have moved on over years!

     
  • Mittwoch, 11. April 2012 11:01
     
     Beantwortet
    Anmelden
    0

    Hi,

    The error condition occurs if you attempt to configure username and password for the DSN(Data Source Name ) policy using GPP. Username and password are not valid keywords when configuring a SQL Server DSN.

    For more information about the valid SQL Server-specific keyword/value pairs for data source configuration attribute strings, visit the following Microsoft Web site:

    http://msdn.microsoft.com/en-us/library/aa177860(SQL.80).aspx

    When configuring SQL connections, the only way to make the connection transparent for the user is to set Trusted_Connection to Yes. Otherwise, the user will be prompted for credentials when trying to connect.

    You must also ensure that attributes not listed in the above MSDN link, including username and password, are left blank (not configured) within the policy when configuring SQL connections.

    Regards,

    Denny Zhou

                                                                                                                                   

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

     
  • Freitag, 13. April 2012 09:08
     
     
    Anmelden
    0

    Hi,

    How are things going? Please let me know if my answers properly address your questions. Thanks.

    Regards,

    Denny Zhou

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

     
  • Montag, 3. Dezember 2012 21:44
     
     
    Anmelden
    0

    What a frustrasting line of enquiry. Denny Zhou's comment might contain a non-direct answer of "It is impossible" but with such vague wording, it's hard to say.

    Imagine this scenario:
    Non-Domain joined SQL Server

    That's as complex as the situation is, really. I want to use GPP to deploy connections to a SQL Server hosted in a Data-Centre. Let me try and translate Denny Zhou's crappy wording:

    "Username and password are not valid keywords when configuring a SQL Server DSN."

    Translated to actually be relevant to the question asked: "There is no way to use GPP to configure a SQL Server DSN to servers that use SQL Authentication... because Usernames and Passwords are invalid fields" (Even though they are valid fields in ODBC Admin...?)

    If anyone else has discovered any evidence to the contrary, please post your findings, otherwise I think I'll accept this is impossible to do right now.