Returning Somthing unique about the machine

From: Michael Tissington (michael_at_nospam.com)
Date: 05/10/04 

Date: Mon, 10 May 2004 10:44:59 -0700

I'd like to issue some SQL to return something unique about the machine that
SQL server is running on. The machine may not be part of a domain (as in the
case when MSDE is installed).

I had thought of using the NetBIOS domain name but SQL server does not seem
able to return this information easily.

Basically I'm looking for a unique piece of information about the machine
that SQL is able to return to the client.

Any other ideas please? 

-- 
Michael Tissington
http://www.oaklodge.com
http://www.tabtag.com

Relevant Pages

  • Re: Returning Somthing unique about the machine
    ... hostname etc are not necessarily unique. ... > I had thought of using the NetBIOS domain name but SQL server does not ...
    (microsoft.public.sqlserver.programming)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I think it will ameliorate the situation if you clean up the client as ... And to come back to my problem: I think with help of the SQL Server admins ... closed connections - but all of these errors are in the version which used ... Every new client opens again 30 connections if I open 30 tables ...
    (microsoft.public.sqlserver.connect)
  • Re: Best way to populate webpages from multiple tables
    ... tables within hash tables, custom classes etc. ... > Set a session expiring cookie at the client that stores the Customer ID. ... > send it to the client, instead store it in your session mgmt sql server - ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Best way to populate webpages from multiple tables
    ... tables within hash tables, custom classes etc. ... > Set a session expiring cookie at the client that stores the Customer ID. ... > send it to the client, instead store it in your session mgmt sql server - ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... an Access database in former times this was a lot of work which took me ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... client for programming easy, fast and good applications. ...
    (microsoft.public.sqlserver.connect)