I decided the try to restore the database with T-SQL, with T-SQL the restore completed successfully! Another advantage of using T-SQL is that T-SQL gave more logging. This logging shows me that the BAK file (delivered from a third party) is not a SQL Server 2005 backup but presumably a SQL Server 2000 database backup …

DECLARE
  @BackupFile varchar(8000),
  @sql varchar(8000)
  SET @BackupFile = 'E:\DB2000.BAK'
  SET @sql = 'RESTORE DATABASE ADB01 FROM DISK = ''' + @backupfile + ''' WITH FILE = 1,  
    MOVE N''DB2000_dat'' TO N''E:\mssql\data\ADB01\ADB01_01.mdf'',  
    MOVE N''DB2000_log'' TO N''F:\mssql\tlog\ADB01\ADB01_01.ldf'',  
    NOUNLOAD,  REPLACE,  STATS = 10, RECOVERY'
  exec (@sql)
go
 
10 percent processed.
20 percent processed.
30 percent processed.
40 percent processed.
50 percent processed.
60 percent processed.
70 percent processed.
80 percent processed.
90 percent processed.
100 percent processed.
Processed 2792 pages for database 'ADB01', file 'DB2000_dat' on file 1.
Processed 1 pages for database 'ADB01', file 'DB2000_log' on file 1.
Converting database 'ADB01' from version 539 to the current version 611.
Database 'ADB01' running the upgrade step from version 539 to version 551.
Database 'ADB01' running the upgrade step from version 551 to version 552.
Database 'ADB01' running the upgrade step from version 552 to version 553.
Database 'ADB01' running the upgrade step from version 553 to version 554.
Database 'ADB01' running the upgrade step from version 554 to version 589.
Database 'ADB01' running the upgrade step from version 589 to version 590.
Database 'ADB01' running the upgrade step from version 590 to version 593.
Database 'ADB01' running the upgrade step from version 593 to version 597.
Database 'ADB01' running the upgrade step from version 597 to version 604.
Database 'ADB01' running the upgrade step from version 604 to version 605.
Database 'ADB01' running the upgrade step from version 605 to version 606.
Database 'ADB01' running the upgrade step from version 606 to version 607.
Database 'ADB01' running the upgrade step from version 607 to version 608.
Database 'ADB01' running the upgrade step from version 608 to version 609.
Database 'ADB01' running the upgrade step from version 609 to version 610.
Database 'ADB01' running the upgrade step from version 610 to version 611.
RESTORE DATABASE successfully processed 2793 pages in 1.513 seconds (15.118 MB/sec).
 

Specify non default tcp ports

C:\>osql -Stcp:<hostname>,<portname>[\<instance_name>] -E
1>

See http://support.microsoft.com/kb/313295

execute sp_dboption

1> exec sp_dboption 'testdb01', 'single user', 'FALSE';
2> go
Msg 5064, Level 16, State 1, Server REMIDIAN01, Line 1
Changes to the state or options of database 'testdb01' cannot be made at this
time. The database is in single-user mode, and a user is currently connected to
it.
Msg 5069, Level 16, State 1, Server REMIDIAN01, Line 1
ALTER DATABASE statement failed.
sp_dboption command failed.

Now I can use TSQL below to find all the database sesions connected to this database.

TSQL script to retrieve client sessions per database.

select d.name, d.dbid, spid, login_time, nt_domain, nt_username, loginame
  from sysprocesses p inner join sysdatabases d on p.dbid = d.dbid
 where d.name = 'testdb01'
go
 

Kill the particular session(s) with the ;kill’ command.

1> kill 51
2> go
1>

Now I can ‘remove’ the database from Sinlge user mode.

1> exec sp_dboption 'testdb01', 'single user', 'FALSE'
2> go
1>

Enterprise Manager Grid Control System Monitoring Plug-in for Microsoft SQL Server

I have been busy deploying Microsoft SQL Server in our Oracle Enterpise GRID Control using the ‘Oracle Enterprise Manager Grid Control
System Monitoring Plug-in for Microsoft SQL Server’ http://www.oracle.com/technology/products/oem/extensions/plugin-ms_sql.html.

The final step in the configuration is the configuration of your SQL Server target in the GRID Control ‘configure target’ page for that SQL Server. One of the fields required is ‘JDBC URL’ (and ‘JDBC Driver’).

The Microsoft SQL Server 2005 JDBC Driver comes with two sample programs in sqljdbc_1.2\enu\help\samples\connections (connectDS.java and connectURL.java). Since one of the prerequisities I read on metalink is ‘make sure remote JDBC connections with your SQL Server work’ I left the Oracle GRID console and tried to get this sample program to connect to my SQL Server succesfully.

It took my quit some time to get the right connection values (my SQL Server listened on TCP port 1204 instead of 1433), and because I got a little tired of having to compile the provided java test pogram every time I wanted to try new connection details I decided to rewrite this program into a program that ‘asks’ for the connection values. This way I can provide the entries connection details at run time (instead of at compile time).

jdbcMSSql.java

import java.io.Console;
import java.sql.*;

 
public class jdbcMSSql {

  public static void main(String[] args) {

    // prepare console 
    Console c = System.console();
    if (c == null) {
              System.err.println("No console.");
              System.exit(1);
    }
 
    // read from console
    String servername = c.readLine("Enter servername  : ");
    String portnumber = c.readLine("Enter portnumber  : ");
    String database   = c.readLine("Enter database    : ");
    String username   = c.readLine("Enter username    : ");
      // !! readPassword 'needs' JDK 1.6
    char [] password   = c.readPassword("Enter password    : ");

    // Construct connetionurl 
    String conUrl = "jdbc:sqlserver://" +
      servername + ":" + portnumber + ";databaseName=" + database +";" +
      "integratedSecurity=false;";

    // Declare the JDBC objects.
    Connection con = null;
    Statement stmt = null;
    ResultSet rs = null;
 
    try {      
      // Establish the connection.
      Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver");
      con = DriverManager.getConnection( conUrl, username, new String(password));

      stmt = con.createStatement();
      rs = stmt.executeQuery( "SELECT @@servername, @@spid");
 
      // Iterate through the data in the result set and display it.
      while (rs.next()) {
        System.out.println("Connection test OK:  '" +
        rs.getString(1) + "' (pid is '" + rs.getString(2) + "').");  
      }
    }
 
    // Handle any errors that may have occurred.
    catch (Exception e) {
      e.printStackTrace();
    }

    finally {
      if (con != null) try { con.close(); } catch(Exception e) {}
    }
  }
}

 

Compile and Execute

To compile this you must of course have the JDBC driver class in you %CLASSPATH% ($CLASSPATH) environment variable. See example below.

Compile jdbcMSSql.java

C:\\oracle\\jdbc-test>echo %CLASSPATH%
.;C:\\oracle\\agent10g\\sysman\\jlib\\sqljdbc_1.2\\enu\\sqljdbc.jar
 
C:\\oracle\\jdbc-test>javac jdbcMSSql.java

Execute jdbcMSSql.class

C:\\oracle\\jdbc-test>java jdbcMSSql
Enter servername  : REMIDIAN01
Enter portnumber  : 1204
Enter database    : master
Enter username    : sa
Enter password    :
Connection test OK:  'REMIDIAN01\\MSSQL01' (pid is '51').
 
C:\\oracle\\jdbc-test>

Oracle GRID SQL Server Target Configuration

Now that I have the correct connection details I can go back the Oracle GRID console and provide the correct connection details in the Target Configuration page for the SQL Server target:

JDBC URL : jdbc:sqlserver://remidian:1204;integratedSecurity=false;instanceName=MSSQL01
JDBC Driver: com.microsoft.sqlserver.jdbc.SQLServerDriver
 
 
 

N.B. – JDK 1.6 required

Program requires JDK 1.6 for the ‘console.readPassword’ is new in 1.6, read here http://blogs.sun.com/DaveB/en_US/entry/new_improved_in_java_se1. When you have < 1.6 simply change:

// char [] password   = c.readPassword("Enter password    : ");
String password   = c.readLine("Enter password    : ");
 
// con = DriverManager.getConnection( conUrl, username, new String(password));
con = DriverManager.getConnection( conUrl, username, password);

Java version banner

C:\\oracle\\jdbc-test>java -version
java version "1.6.0_02"
Java(TM) SE Runtime Environment (build 1.6.0_02-b06)
Java HotSpot(TM) Client VM (build 1.6.0_02-b06, mixed mode, sharing)
 
C:\\oracle\\jdbc-test>

Create database

See syntax below for the CREATE DATABASE statement.

Create NORTHWIND database

1> use master
2> go
1> create database [NORTHWIND]
2>     on ( name        = N'NORTHWIND_dat',
3>          filename    = N'C:\\mssql\\data\\iDEFAULT\\NORTHWIND\\NORTHWIND_01.mdf' ,
4>          size        = 10,
5>          filegrowth  = 1,
6>          maxsize     = 1024
7>        )
8> log on ( name        = N'NORTHWIND_log',
9>          filename    = N'C:\\mssql\\tlog\\iDEFAULT\\NORTHWIND\\NORTHWIND_01.ldf' ,
10>         size        = 10,
11>         filegrowth  = 1,
12>         maxsize     = 1024
13>        )
14>  collate Latin1_General_CI_AS
15>
16> go
The CREATE DATABASE process is allocating 10.00 MB on disk 'NORTHWIND_dat'.
The CREATE DATABASE process is allocating 10.00 MB on disk 'NORTHWIND_log'.
1>

Drop database

A database can be dropped using the DROP DATABASE statement. All database datafiles and logfiles are removed from the os.

Dropping a database

1> use master
2> go
1> drop database [NORTHWIND]
2> go
Deleting database file 'C:\\mssql\\tlog\\iDEFAULT\\NORTHWIND\\NORTHWIND_01.ldf'.
Deleting database file 'C:\\mssql\\data\\iDEFAULT\\NORTHWIND\\NORTHWIND_01.mdf'.
1>

Rename database

A database can be renamed with the stored procedure SP_RENAMEDB. (VERY easy compared to oracle …)

Rename the NORTHWIND database to ‘WESTWIND’

1> use master
2> go
1> select dbid, left( name, 10) name
2>   from sysdatabases
3>  where name = 'NORTHWIND'
4> go
 dbid   name
 ------ ----------
     17 NORTHWIND
 
(1 row affected)
1>
2> exec sp_renamedb 'NORTHWIND', 'WESTWIND'
3> go
The database name 'WESTWIND' has been set.
1>
2> select dbid, left( name, 10) name
3>   from sysdatabases
4>  where dbid = 17
5> go
 dbid   name
 ------ ----------
     17 WESTWIND
 
(1 row affected)
1>

IF THEN ELSE

The IF THEN ELSE syntax in TSQL is kinda weird if you ask me … I forget them ‘all the time’, created examples below for my reference.

IF THEN

if 1 = 1
begin 
  print 'true'
end
 
go
 

IF THEN – short notation

if 1 = 1
  print 'true'
 
go
 

IF THEN ELSE

if 1 = 1
begin
  print 'true'
end
 
else  

begin
  print 'false'
end
 
go
 

IF THEN ELSE – short notation

if 1 = 1
  print 'true'
else  
  print 'false'

go
 

Multiple IF THEN ELSE blocks

if 1 = 1
begin
  print '1 = 1'
end
else  
if 1 = 2
  begin
    print '1 = 2'
  end
else
if 1 = 3
begin
  print '1 = 3'
end
 
go
 

CASE

TSQL has the CASE control structure …

declare @i int, @r int
 
set @i = 1
 
set @r = 
  case @i
    when 1 then 1
    when 2 then 2
      else 0
  end
 
print @r
 
go
 

WHILE

Eternal loop

while 1 = 1 
  print 'true'
 
go
 

Simple WHILE loop

declare @i int
set @i = 0
 
while @i < 10
begin
  print @i
  set @i = @i + 1
end
 
go
 

The contents of your tracefile will become more meanigfull and not unimportant small …

Filter out ‘internal’ sql server proceses

Filter on ‘ApplicationName’

-- --
-- ApplicationName
 
-- SQL Profiler sessions
exec sp_trace_setfilter @TraceID, 10, 0, 7, N'SQL Profiler'
 
-- SQL executed by the SQL Agent
exec sp_trace_setfilter @TraceID, 10, 0, 7, N'SQLAgent%'
exec sp_trace_setfilter @TraceID, 10, 0, 7, N'SQLDMO_1%'
 

Filter on ‘LoginName’

-- --
-- LoginName
 
exec sp_trace_setfilter @TraceID, 11, 0, 7, N'remivisser'
exec sp_trace_setfilter @TraceID, 11, 0, 7, N'<username>'

Simple cursor loop

Example below is the most straight forward example of walking through a CURSOR with a WHILE loop in tsql. The cursor is declared, opened and and a FETCH NEXT is done while @@fetch_status equals 0.

The behaviour of a FETCH [ NEXT ] call is that it returns the value(s) for the column(s) specified in the DECLARE CURSOR as a single-row result set.

Basic cursor example with FETCH returning row as single-row result set

1> declare c1 cursor
2> for
3> select left( name, 32)            as name,
4>        cast( dbid as varchar(10)) as dbid
5>   from master.dbo.sysdatabases
6>  where dbid < 5
7>
8> open c1
9> fetch next from c1
10>
11> -- while @@fetch_status != -1 and @@fetch_status != -2
12> while @@fetch_status = 0
13>    fetch next from c1
14>
15> close c1
16> deallocate c1
17>
18> go
 name                             dbid
 -------------------------------- ----------
 master                           1
 
 name                             dbid
 -------------------------------- ----------
 tempdb                           2
 
 name                             dbid
 -------------------------------- ----------
 model                            3
 
 name                             dbid
 -------------------------------- ----------
 msdb                             4
 
 name                             dbid
 -------------------------------- ----------
 
1>

@@fetch_status

@@fetch_status is a built in variable returning the exit code of the latest fetch call.

FETCH INTO

The ‘FETCH INTO’ option is used to return values from a cursor (instead of getting it returned as a single-row result set) into pre-defined variables.

Example below displays how to perform a FETCH INTO with a single column.

1> declare @s_name    varchar(32)
2> declare c1 cursor
3> for
4> select name
5>   from master.dbo.sysdatabases
6>  where dbid < 5
7>
8> open c1
9> fetch next from c1 into @s_name
10>
11> while @@fetch_status = 0
12> begin
13>   print 'name = ' + @s_name
14>   fetch next from c1 into @s_name
15> end
16>
17> close c1
18> deallocate c1
19>
20> go
name = master
name = tempdb
name = model
name = msdb
1>

Example below displays how to perform a FETCH INTO with multiple columns.

1> declare @s_name    varchar(32),
2>         @i_dbid    smallint
3> declare c1 cursor
4> for
5> select name,
6>        dbid
7>   from master.dbo.sysdatabases
8>  where dbid < 5
9>
10> open c1
11> fetch next from c1 into @s_name, @i_dbid
12>
13> while @@fetch_status = 0
14> begin
15>   print 'DB = ' + cast( @i_dbid as varchar(8)) + ':' + @s_name
16>   fetch next from c1 into @s_name, @i_dbid
17> end
18>
19> close c1
20> deallocate c1
21>
22> go
DB = 1:master
DB = 2:tempdb
DB = 3:model
DB = 4:msdb
1>

Scrollable cursors

All examples above are so-called ‘forward only cursors’ (the default cursor type). When you want to be able to scroll through your cursor the cursor most be declared through the SCROLL CURSOR declaration.

Whenever a cursor is declared as a SCROLL CURSOR the following FETCH options become available:

Fetch Options

• PRIOR
• FIRST
• LAST
• ABSOLUTE { n | @nvar }
• RELATIVE { n | @nvar }

All examples below are done with ‘demo’ table listed below.

demo table

1> select * from demo order by k
2> go
 k
 -----------
           0
           1
           2
           3
           4
           5
           6
           7
           8
           9
 
(10 rows affected)
1>

FETCH NEXT and FETCH PRIOR

1> declare @i as int
2> declare c1 scroll cursor
3> for
4> select k
5>   from demo
6> order by k
7>
8>
9>
10> open c1
11>
12>
13> print 'FETCH NEXT ' + char(10)
14> print '=================================='
15>
16> fetch next from c1 into @i
17> while @@fetch_status = 0
18> begin
19>   print cast(@i as char(1)) + ' @@fetch_status ' + cast(@@fetch_status as char)
20>   fetch next from c1 into @i
21> end
22>
23> fetch next from c1 into @i
24> print cast(@i as char(1)) + ' @@fetch_status ' + cast(@@fetch_status as char)
25>
26>
27> print char(10) + 'FETCH PRIOR ' + char(10)
28> print '=================================='
29>
30> fetch prior from c1 into @i
31> while @@fetch_status = 0
32> begin
33>   print cast(@i as char(1)) + ' @@fetch_status ' + cast(@@fetch_status as char)
34>   fetch prior from c1 into @i
35> end
36>
37> fetch prior from c1 into @i
38> print cast(@i as char(1)) + ' @@fetch_status ' + cast(@@fetch_status as char)
39>
40>
41> close c1
42> deallocate c1
43>
44>
45>
46> go
FETCH NEXT
==================================
0 @@fetch_status 0
1 @@fetch_status 0
2 @@fetch_status 0
3 @@fetch_status 0
4 @@fetch_status 0
5 @@fetch_status 0
6 @@fetch_status 0
7 @@fetch_status 0
8 @@fetch_status 0
9 @@fetch_status 0
9 @@fetch_status -1
 
FETCH PRIOR
==================================
9 @@fetch_status 0
8 @@fetch_status 0
7 @@fetch_status 0
6 @@fetch_status 0
5 @@fetch_status 0
4 @@fetch_status 0
3 @@fetch_status 0
2 @@fetch_status 0
1 @@fetch_status 0
0 @@fetch_status 0
0 @@fetch_status -1
1>

FETCH LAST / FETCH PRIOR

1> declare @i as int
2> declare c1 scroll cursor
3> for
4> select k
5>   from demo
6> order by k
7>
8>
9>
10> open c1
11>
12>
13> print char(10) + 'FIRST LAST PRIOR ' + char(10)
14> print '=================================='
15> fetch last from c1 into @i
16> print 'FETCH LAST  = ' + cast(@i as char(1)) +
17>         ' @@fetch_status = ' + cast(@@fetch_status as char)
18> fetch prior from c1 into @i
19> print 'FETCH PRIOR = ' + cast(@i as char(1)) +
20>         ' @@fetch_status = ' + cast(@@fetch_status as char)
21> fetch first from c1 into @i
22> print 'FETCH FIRST = ' + cast(@i as char(1)) +
23>         ' @@fetch_status = ' + cast(@@fetch_status as char)
24> fetch prior from c1 into @i
25> print 'FETCH PRIOR = ' + cast(@i as char(1)) +
26>         ' @@fetch_status = ' + cast(@@fetch_status as char)
27> fetch next from c1 into @i
28> print 'FETCH NEXT  = ' + cast(@i as char(1)) +
29>         ' @@fetch_status = ' + cast(@@fetch_status as char)
30> fetch next from c1 into @i
31> print 'FETCH NEXT  = ' + cast(@i as char(1)) +
32>         ' @@fetch_status = ' + cast(@@fetch_status as char)
33>
34>
35> close c1
36> deallocate c1
37>
38>
39>
40> go
 
FIRST LAST PRIOR
==================================
FETCH LAST  = 9 @@fetch_status = 0
FETCH PRIOR = 8 @@fetch_status = 0
FETCH FIRST = 0 @@fetch_status = 0
FETCH PRIOR = 0 @@fetch_status = -1
FETCH NEXT  = 0 @@fetch_status = 0
FETCH NEXT  = 1 @@fetch_status = 0
1>

FETCH ABSOLUTE

1> declare @i as int
2> declare c1 scroll cursor
3> for
4> select k
5>   from demo
6> order by k
7>
8> open c1
9>
10> print char(10) + 'FETCH ABSOLUTE ' + char(10)
11> print '======================================'
12> fetch absolute 2 from c1 into @i
13> print 'FETCH ABSOLUTE 2 = ' + cast(@i as char(1)) +
14>         ' @@fetch_status = ' + cast(@@fetch_status as char)
15> fetch absolute 8 from c1 into @i
16> print 'FETCH ABSOLUTE 8 = ' + cast(@i as char(1)) +
17>         ' @@fetch_status = ' + cast(@@fetch_status as char)
18>
19> close c1
20> deallocate c1
21>
22> go
 
FETCH ABSOLUTE
======================================
FETCH ABSOLUTE 2 = 1 @@fetch_status = 0
FETCH ABSOLUTE 8 = 7 @@fetch_status = 0
1>

FETCH RELATIVE

1> declare @i as int
2> declare c1 scroll cursor
3> for
4> select k
5>   from demo
6> order by k
7>
8>
9>
10> open c1
11>
12>
13> print char(10) + 'FETCH RELATIVE' + char(10)
14> print '======================================='
15> fetch relative 1 from c1 into @i
16> print 'FETCH RELATIVE 1   = ' + cast( @i as varchar(1)) +
17>         ' @@fetch_status = ' + cast(@@fetch_status as char)
18>
19> fetch relative -1 from c1 into @i
20> print 'FETCH RELATIVE -1  = ' + cast( @i as varchar(1)) +
21>         ' @@fetch_status = ' + cast(@@fetch_status as char)
22>
23> fetch relative -2 from c1 into @i
24> print 'FETCH RELATIVE -2  = ' + cast( @i as varchar(1)) +
25>         ' @@fetch_status = ' + cast(@@fetch_status as char)
26>
27> fetch relative 3 from c1 into @i
28> print 'FETCH RELATIVE 3   = ' + cast( @i as varchar(1)) +
29>         ' @@fetch_status = ' + cast(@@fetch_status as char)
30>
31> fetch relative 100 from c1 into @i
32> print 'FETCH RELATIVE 100 = ' + cast( @i as varchar(1)) +
33>         ' @@fetch_status = ' + cast(@@fetch_status as char)
34>
35> fetch relative -1 from c1 into @i
36> print 'FETCH RELATIVE -1  = ' + cast( @i as varchar(1)) +
37>         ' @@fetch_status = ' + cast(@@fetch_status as char)
38>
39>
40> close c1
41> deallocate c1
42>
43>
44>
45> go
 
FETCH RELATIVE
=======================================
FETCH RELATIVE 1   = 0 @@fetch_status = 0
FETCH RELATIVE -1  = 0 @@fetch_status = -1
FETCH RELATIVE -2  = 0 @@fetch_status = -1
FETCH RELATIVE 3   = 2 @@fetch_status = 0
FETCH RELATIVE 100 = 2 @@fetch_status = -1
FETCH RELATIVE -1  = 9 @@fetch_status = 0
1>

Scenario

The example below displays the number of objects per database. The following steps are involved.

• open a cursor for the select * from master.dbo.sysdatabases statement (cursor is a while loop),
• inside the cursor a dynamic sql statement is defined ,
• at last the stored procedure sp_executesql is used to retrieve the output of this defined sql statement into tsql variables .

sp_execute example to return values into variables

1> declare @s_dtb  sysname
2> declare @s_sql  nvarchar(2000)
3> declare @i_obj  int
4> declare c1     cursor
5> for
6> select name
7>   from master.dbo.sysdatabases
8>
9>
10> open c1
11> fetch c1 into @s_dtb
12>
13> while @@fetch_status >= 0
14> begin
15>
16>   -- construct sql statement
17>   set @s_sql = 'select @count = count(*)
18>                  from ' + QuoteName(@s_dtb) + '.dbo.sysobjects'
19>
20>   -- execute dynamic sql and map output variable @count to variable @i_obj
21>   exec sp_executesql
22>     @s_sql,
23>     N'@count int output',
24>     @count = @i_obj output
25>
26>   print @s_dtb + ' db has ' + cast( @i_obj as varchar) + ' objects'
27>
28>   fetch c1 into @s_dtb
29>
30> end
31>
32> close c1
33> deallocate c1
34>
35>
36> go
master db has 1324 objects
model db has 54 objects
msdb db has 454 objects
Northwind db has 146 objects
tempdb db has 54 objects
1>

Extremely handy I would say. – Whenever you want to perform an operation (execute tsql) on all your databases.

Whoami

In MSSQL (2000) there’s not an easy way to see in which database you are. Script below creates a view ‘whoami’ that gives you the information;

create view dbo.whoami
as
select @@spid as '@@spid',
       cast( user as varchar(12)) as 'user',
       cast( p.dbid as varchar(6)) + ':' + cast( d.name as varchar(14)) as 'database',
       cast( p.loginame as varchar(16)) loginame,
       cast( p.hostname as varchar(16)) as 'hostname',
       cast( p.nt_username as varchar(16)) nt_username
   from master.dbo.sysprocesses p left join master.dbo.sysdatabases d
      on d.dbid = p.dbid
   where spid = @@spid
 
go
 
grant select on dbo.whoami to public
go
 

1> select * from whoami
2> go
 @@spid user         database              loginame         hostname         nt_username
 ------ ------------ --------------------- ---------------- ---------------- ----------------
     51 dbo          1:master              NYC01\\remivisser NYC01            remivisser
 
(1 row affected)
1>