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.
Use below;
How to use Kerberos authentication in SQL Server
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,
inserting data into SQL Server on T081\SQLTest03,
and specifying a data_file on third computer
by using a UNC path
\\Box3\Share_Data\
by using a UNC path
\\Box3\Share_Data\
Use below;
How to use Kerberos authentication in SQL Server
Powered by ScribeFire.
No comments:
Post a Comment