Post reply

Machine ID

  • January 24, 2002 at 5:25 pm

    #422640

    Don;t think so. I get this for trusted connections for sa.

    Steve Jones

    steve@dkranch.net

  • January 28, 2002 at 10:36 am

    #422743

    Hi Deuce,

    Well not really.. Because my app connects all users as the same SQL login after I do the intial security check using a lot of group hierarchy within my application. Therefore I am not sure that is going to work.

    But the host_name again, like Steve/Andy pointed out cannot be unique because two machines can have the same name hardcoded.

    Bottomline I am not sure "a way" that is going to work in all scenarios.

    Thanks

  • January 28, 2002 at 10:52 am

    #422749

    Back to my original response. Pass the machine name in from the front end. A trigger would catch the changes made by different applications. Maybe you need both?

    Good luck!

  • January 28, 2002 at 12:28 pm

    #422760

    Rather than the machine name, rigorously enforce user names that are unique to each user and apss this in.

    Steve Jones

    steve@dkranch.net

  • January 28, 2002 at 1:47 pm

    #422775

    Steve,

    You are right! I wish I could do that...

    Well I am going to tell it to my customers and basically tell them the downside to not adhering to the law of the user names not being unique. It si upto them, If they want the data to be correct then they got to enforce it otherwise "sorry ,cant help you"

    Deuce, I am going to basically tell them this..

    Thanks guys!! you guys are very helpful

  • January 28, 2002 at 9:00 pm

    #422790

    Have you tried SELECT SYSTEM_USER?

    I know when I use this it gives my username where the other user_name() gives dbo for the same login.

    Robert Marda

    Robert W. Marda
    Billing and OSS Specialist - SQL Programmer
    MCL Systems

  • January 29, 2002 at 11:45 am

    #422813

    nice, forgot about that. Thanks Robert!!

    Steve Jones

    steve@dkranch.net

  • January 29, 2002 at 12:06 pm

    #422818

    Hi Robert,

    Well my problem is, the app uses "sa" as the id to connect to the db. All the security process is taken care of in the application. Therefore it will not work in my case. Thanks for the tip though!! I can proably use it in another place:)

  • January 29, 2002 at 12:56 pm

    #422831

    FYI. I'd change that first. Using Sa, as I'm sure most would agree, is a Worst Practice.

    Steve Jones

    steve@dkranch.net

  • January 29, 2002 at 1:46 pm

    #422834

    Hi Steve,

    You are right. It is the worst but that is going to be done at a later date as per the project priority.

Viewing 10 posts - 16 through 24 (of 24 total)

You must be logged in to reply to this topic. Login to reply