How to use Kerberos authentication in SQL Server

On Situation like;

  This could be either because of a network problem (i.e. the machine could not
connect to the domain controller for authenticating the user) or the user
account (KUT01\SQL_rest_test_3 ) running sqlservr.exe does not have
permission to query the domain controller (KU). The later could happen if
sqlservr.exe is running using an domain account
(KUT01\SQL_rest_test_3) different from the user 'KU\SQLService' above 
the machine is on a different domain (KUT01) than 'KU\SQLService' and there
is no two-way trust.

        When you invoke the BULK Insert  from computer T080 , 
         inserting data into SQL Server on  T081\SQLTest03,

         and specifying a data_file on third computer
by using a UNC path         
             \\Box3\Share_Data\

Use below;

How to use Kerberos authentication in SQL Server

Powered by ScribeFire.

"Unable to validate product key" during installation of SQL Server 2000 Standard Edition.

"Unable to validate product key" during installation of SQL Server 2000 Standard Edition.

 Faced this problem today on Windows 2000 Advanced server with SP4.

Just followed as advised on the KB# 555496, it resolved the problem.

Powered by ScribeFire.

SQL Server - How To Tell If There Is A Trace Running

 

Server-side tracing is the process of having your SQL Server machine save events to a physical file on that machine without using the Profiler client tool. Server-side tracing is enabled and controlled by using SQL Server system-supplied stored procedures and functions. With these system-supplied processes, you can identify what to trace, when to start and stop tracing, what traces are running, and view trace information stored in the trace file.


Here is how you view the number of traces currently running:



SELECT count(*) FROM :: fn_trace_getinfo(default)
WHERE property = 5 and value = 1




Here is how you can find more detail about the running traces:

 SELECT * FROM :: fn_trace_getinfo(default)




You can terminate a trace with the 'sp_trace_setstatus' stored procedure using the traceid:

EXEC sp_trace_setstatus 1, @status = 0

EXEC sp_trace_setstatus 1, @status = 2



setting the status to 0 stops the trace
setting the status to 2 closes the trace and deletes its definition from the server

Powered by ScribeFire.