<table cellpadding='5' cellspacing='1' class='quote'><tr><td valign='top' nowrap width='11'><img src='http://www.sqlservercentral.com/forums/images/quoteicon.gif' width='11' alt='quote' height='13' align='absmiddle'></td><td width='99%'>

Just ADD the line here if you don't use IE and the code will come out as below

</td></tr></table>

Because you said the file comes from unix I would try changing:

ROWTERMINATOR = '\n\r'

)

to

ROWTERMINATOR = '\n'

)

Just keep in mind that because you are using 2005 you have to enable that feature before using any ROWSET function.

Windows users are *always* bound by windows password policies

>>>>>The "Not for replication" option isn't what we want either, because that would stop the keys themselves being replicated ... <<<<

That is *not* correct NOT FOR REPLICATION just means...

select suser_sname(SID)

YES

select name, is_policy_checked

from sys.sql_logins

--where name ='LoginName'

are you experiencing autogrows ?

I second John's view on this. 10% seems like a BUG to me

I had *STRUGLED* with that problem for a looooonnnngggg time. The issue in my case was Windows 2003 Server! It can't handle under certain conditions many connection "open" requests at...

sysxlogins has always been undocumented. you get compatibility views only on on documented catalog tables ( and sometimes not even that).

you should change your code to use "sys.server_principals"

Isablelle,

Unless the tables on the database have explicitly been granted "SELECT" permissions to the "public" role you should receive a message like this:

Msg 229, Level 14, State 5, Line 2

The...

Excellent idea. There is one little problem though and is that the trigger is coded for "single-row" inserts. I don't really know if SQL Profiler ever is going to submit...

You simply set replication back. Now, there are *many* tricks in which your environment could handle it and those are very dependent on your availability.

The plan on some places is...