Queries going to Suspend state with wait type ASYNC_NETWORK_IO

Recently we observed a problem. We are running stored procedure through our c# code. Three machines access the server and update or insert in the required tables in the server. If there is no data in the server, on installing first time our application usually our database is clean. then stored procedure works fine, it takes around 10 to 15 sec to execute. Next time if execute the time goes up to minutes like 15 mins. Next time it goes for hours around 4 hrs. Even to update 4 or 5 records it takes time. Initially we thought it was because of the size of the data and we tried to re tune on indexes, it did not solve. But now what we observe is even with less number of records in server also it wouldn't come of the execution for hours.
Now are executing the just the SP in the SQL manager studio to see the time. That one also is executing for hours. when looked at the activity monitor the process goes to suspend state with wait type ASYNC_NETWORK_IO.

When we comment one of the query is working fine.
Is this something to do with the query I am not sure. If that is the case it should not work every time.

The query makes any sence or is there any way to write it in better way

'UPDATE [server].[dbo].[DocumentMetadata] SET DocumentInfoID = b.DocumentInfoID, [Name] = b.[Name], MetadataType = b.MetadataType,
[Value] = b.[Value], ValueType = b.ValueType
FROM [server].[dbo].[DocumentMetadata] a WITH (UPDLOCK)
INNER JOIN (SELECT c.DocumentInfoID, c.[Name], c.MetadataType, c.[Value], c.ValueType
FROM MACHINENAME.[Client].[dbo].[DocumentMetadata] c
INNER JOIN MACHINENAME.[Client].dbo.DocumentInfo DINF ON c.DocumentInfoID = DINF.DocumentInfoID
INNER JOIN MACHINENAME.[Client].dbo.Path d on DINF.NativeFileID = d.PathID
INNER JOIN MACHINENAME.[Client].dbo.ActiveDataSource ADS ON d.DataSourceID = ADS.DataSourceID
WHERE ADS.ProjectID = ''' + @.ProjID + ''') b
ON a.DocumentInfoID = b.DocumentInfoID AND a.[Name] = b.[Name]'

'INSERT INTO [server].[dbo].[DocumentMetadata]
(DocumentInfoID, [Name], MetadataType, [Value], ValueType)
SELECT c.DocumentInfoID, c.[Name], c.MetadataType, c.[Value], c.ValueType
FROM MACHINENAME.[Client].[dbo].[DocumentMetadata] c
INNER JOIN MACHINENAME.[Client].dbo.DocumentInfo DINF ON c.DocumentInfoID = DINF.DocumentInfoID
INNER JOIN MACHINENAME.[Client].dbo.Path d on DINF.NativeFileID = d.PathID
INNER JOIN MYCLI.[Client].dbo.ActiveDataSource ADS ON d.DataSourceID = ADS.DataSourceID
WHERE ADS.ProjectID = ''' + @.ProjID + '''
AND Ltrim(rtrim(c.DocumentInfoID))+ ltrim(rtrim(c.[Name])) NOT IN
(SELECT Ltrim(rtrim(DocumentInfoID))+ ltrim(rtrim([Name])) FROM [server].[dbo].[DocumentMetadata])'

We have been fighting it out for so many days.
Can anybody help

Thanks
knvdssr

ASYNC_NETWORK_IO means SQL server is waiting for network...

How may rows your select statement for INSERT it is returning?

You are using ltrim and rtrim functions against column which result a table scan and it can't use index...

Try to change the query or just comment the query and test it to make it is the issue.

|||It appears you are using a LINKED SERVER to access another server?

If this is the case, try looking at activity monitor on the source. I would suspect you are getting a deadlock or lock problem or something on the linked server.

The wait you are seeing indicates it is waiting on the linked server to finish the query and send records.

|||When you use 4-part name, all of the data from the remote server is pulled across before the join is formulated. If the remote table is large, you will have to wait for a long time for all the data to cross over. Try using openquery() to only pull/update the necessary remote data.

You can lookup some examples here:
http://groups.google.com/groups?q=sqlserver%20oj%20openquery%20update|||

We commented the query which I mentioned earlier, to see if that one is causing the problem. Then the whole Stored procedure finished executing in minutes.

We changed the the query with our using the NOT IN in that query.

Now first time it is taking only 10 minutes for more than 100,000 records.

But the second one is not coming out at all. This time the server is having lot of rows because is already updated once.

All that we see is the process in suspend state or comes out as timed out.

If I am getting a dead lock on the linked server is there any way to solve it?

Could any body help please

|||

Again, take a look at openquery/openrowset. Bringing the entire resultset back is not recommended when the remote table is large.

Q: Windows Authentication

Is Windows Authentication possible without a domain controller?
I am running a testbed with two Win2K machines without firewalls. One
computer contains the MSDE 2000A, set for Windows Authentication
only. Running MS Access on the other computer under the Administrator
account causes a connection failure error message:
Microsoft SQL Server Login
Connection failed:
SQLState: '01000'
SQL Server Error: 87
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen
(Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 6
[Microsoft][ODBC SQL Server Driver][DBNETLIB]Specified SQL server not
found.
Lou Arnold,
Ottawa, Canada
PS...This is a peer-to peer network...no domain controller.
On Sun, 18 Jul 2004 03:53:19 GMT, Lou_Arnold@.nospam.com (Lou Arnold)
wrote:

>Is Windows Authentication possible without a domain controller?
>I am running a testbed with two Win2K machines without firewalls. One
>computer contains the MSDE 2000A, set for Windows Authentication
>only. Running MS Access on the other computer under the Administrator
>account causes a connection failure error message:
>Microsoft SQL Server Login
>--
>Connection failed:
>SQLState: '01000'
>SQL Server Error: 87
>[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen
>(Connect()).
>Connection failed:
>SQLState: '08001'
>SQL Server Error: 6
>[Microsoft][ODBC SQL Server Driver][DBNETLIB]Specified SQL server not
>found.
>Lou Arnold,
>Ottawa, Canada
|||Try substituting WORKGROUP\USERNAME for DOMAIN\USERNAME. Your error looks
like something other than authentication, however. The two machines can see
each other? Are they in the same workgroup? Maybe try connecting by IP
address instead of machine name and make sure your SQL Server service is
running.
Thanks,
Michael C.
"Lou Arnold" <Lou_Arnold@.nospam.com> wrote in message
news:40f9f68a.19289767@.nntp.flfrd.phub.net.cable.r ogers.com...
> PS...This is a peer-to peer network...no domain controller.
> On Sun, 18 Jul 2004 03:53:19 GMT, Lou_Arnold@.nospam.com (Lou Arnold)
> wrote:
>
|||Michael, Pls see my replies below.
On Sun, 18 Jul 2004 05:18:01 GMT, "Michael C" <nospam@.lol.net> wrote:

>Try substituting WORKGROUP\USERNAME for DOMAIN\USERNAME.
I don't understand where to specify this. There is no domain name as
there is no domain controller.

>Your error looks
>like something other than authentication, however.
> The two machines can see
>each other? Are they in the same workgroup? Maybe try connecting by IP
>address instead of machine name and make sure your SQL Server service is
>running.
Yes, the machines can see each other. File and Printer sharing is
enabled and i can see shares on each computer from the other.
Yes, The work group name WORKGROUP for each computer.
Yes, the SQL server instance is running. (it is a named instance)
Yes, I tried using <ipaddr>\<instancename> and got the same error
message.
Lou Arnold
Ottawa, Canada
|||"Lou Arnold" <Lou_Arnold@.nospam.com> wrote in message
news:40fa18ff.473050@.nntp.flfrd.phub.net.cable.rog ers.com...
> Michael, Pls see my replies below.
> On Sun, 18 Jul 2004 05:18:01 GMT, "Michael C" <nospam@.lol.net> wrote:
> I don't understand where to specify this. There is no domain name as
> there is no domain controller.
If you were connected to a Domain Controller, you would specify
DOMAIN\USERNAME. If you are working on a small LAN with no domain
controller, you can specify WORKGROUP\USERNAME instead; or possibly
MACHINENAME\USERNAME (like this: "MSHOME\BOB" or "COMPUTER1\BOB"). You
might also try connecting using the sa username/password.

> Yes, the machines can see each other. File and Printer sharing is
> enabled and i can see shares on each computer from the other.
> Yes, The work group name WORKGROUP for each computer.
> Yes, the SQL server instance is running. (it is a named instance)
> Yes, I tried using <ipaddr>\<instancename> and got the same error
> message.
>
Do you have a default instance running, or just a named instance? Try
connecting to just <ipaddr> if it's the default instance.
Cheers,
Michael C.
|||In reply:
The instance is a single named instance.
I tried connecting with the SA username and password, but it failed
with the same error message. This was expected since the server is set
up for Windows Authentication only.
Re the Workgroup/Domain name: I understand your explanation, but I
still don't know where (or how) to enter the
workgroup-name/computer-name. Can you be specific about the window
and field that this info should be entered? I am still using the
ipaddr/instance-name in the MIcrosoft SQL Server Database Wizard
Dialog box. This box is the first box displayed when, in MS Access,
you try to create a new Access project. The field has the text label:
"What SQL Server would you like to use for this database?"
Lou
On Sun, 18 Jul 2004 17:42:49 GMT, "Michael C" <nospam@.lol.net> wrote:

>"Lou Arnold" <Lou_Arnold@.nospam.com> wrote in message
>news:40fa18ff.473050@.nntp.flfrd.phub.net.cable.ro gers.com...
>If you were connected to a Domain Controller, you would specify
>DOMAIN\USERNAME. If you are working on a small LAN with no domain
>controller, you can specify WORKGROUP\USERNAME instead; or possibly
>MACHINENAME\USERNAME (like this: "MSHOME\BOB" or "COMPUTER1\BOB"). You
>might also try connecting using the sa username/password.
>
>Do you have a default instance running, or just a named instance? Try
>connecting to just <ipaddr> if it's the default instance.
>Cheers,
>Michael C.
>
|||Michael...here are a few more details:
On the server computer, I have used the SQL Server Network Utility to
disable all but TCP/IP connections. Also, the server is set to use
port 1433. Is this appropriate?
On the client computer, I have used the SQL Server Client Network
Utility to disable all but TCP/IP, and to set the default port value
for TCP/IP to use 1433. Is this appropriate?
Lou.
|||Michael...Sorry I was in error. I enabled File and Printer Sharing and
Client for MS Network on the server computer. Doing this got me past
the connect error I gave in the initial post. However, no database was
created, and no error message was generated. Again, I wonder if this a
Windows Authentication problem.
The symptom is now tthis:
The MS SQL Server Database Wizard apparently connects to the server,
after which a dialog box appears saying that it has all the info it
needs. When I Click Finish, a dialog box appears for a split second.
This dialog box is a progress bar that shows the progress of creating
the new database on the server. This bar shows no progress and quickly
disappears. Why does this happen?
Why is Client for MS Networks and File and Printer Sharing required to
make the connection to the server?
Lou Arnold
|||OK, I'm a little lost now. I was under the assumption that you were trying
to connect to your SQL Server via SQL Enterprise Manager and set up
permissions on an account using that. Now I'm not so sure. Just a couple
of questions so I can try to help you a little better:
1. What exactly are you trying to do?
2. Do you have SQL Server 2K on one computer or both?
3. Are both computers in the same Workgroup (right-click on My Computer >
Properties > Computer Name)?
4. Are both computers set up in the same IP range with the same Subnet
(TCP/IP settings)?
5. Are you running any firewall software?
Thanks,
Michael C.
"Lou Arnold" <Lou_Arnold@.nospam.com> wrote in message
news:40fbcf8b.2586869@.nntp.flfrd.phub.net.cable.ro gers.com...
> Michael...Sorry I was in error. I enabled File and Printer Sharing and
> Client for MS Network on the server computer. Doing this got me past
> the connect error I gave in the initial post. However, no database was
> created, and no error message was generated. Again, I wonder if this a
> Windows Authentication problem.
> The symptom is now tthis:
> The MS SQL Server Database Wizard apparently connects to the server,
> after which a dialog box appears saying that it has all the info it
> needs. When I Click Finish, a dialog box appears for a split second.
> This dialog box is a progress bar that shows the progress of creating
> the new database on the server. This bar shows no progress and quickly
> disappears. Why does this happen?
> Why is Client for MS Networks and File and Printer Sharing required to
> make the connection to the server?
> Lou Arnold
|||Michael...see my replies below.
On Tue, 20 Jul 2004 00:36:08 GMT, "Michael C" <nospam@.lol.net> wrote:

>OK, I'm a little lost now. I was under the assumption that you were trying
>to connect to your SQL Server via SQL Enterprise Manager and set up
>permissions on an account using that. Now I'm not so sure. Just a couple
>of questions so I can try to help you a little better:
Don't blame you for being lost.

>1. What exactly are you trying to do?
The objective is to establish a testbed of two Win2K computers. This
is to be a peer network without a domain controller. The intent is to
establish a configuration whereby these two computers can be used for
development. The server is to be used with Windows Authentication
security only unless this proves impossible. We can play with settings
such as TCP/IP, File and Printer sharing and internet port numbers as
long as we establish a minimum configuration and the reason for each
setting.
>2. Do you have SQL Server 2K on one computer or both?
Only one computer (I'll call it the server computer) has the SQL
Server installed. Only one server is installed and this is a named
instance. The server is set to use port 1433. The other computer (the
client computer) has MS Access installed. This is a requirement for
this testbed. No other computers are connected to these computers.
Both computers are run only under the Windows Administrator account to
avoid the cofiguration of permissions.

>3. Are both computers in the same Workgroup (right-click on My Computer >
>Properties > Computer Name)?
Yes, both are in the same workgroup.

>4. Are both computers set up in the same IP range with the same Subnet
>(TCP/IP settings)?
Yes. they run thru a router and so have adjacent addresses, and the
subnet mask of 255.255.255.0. The router's internet connection is
disabled.
BTW: both TCP/IP and Named Pipes are enabled on both client and server
machines using the client and server network utilities.

>5. Are you running any firewall software?
No. No firewalls have been installed.
More info:
In my initial post, MS Access generated a connection error. After some
trials, it was found that networking components "File and Printer
Sharing" and "Client for MS Networks" had to be enabled on both
computers for the connection to work (why is unclear and must be
investigated). After enabling these two networking components, the
connection appears to succeed, but creation of the database fails and
no error message is generated.
In my mind are the following possible causes:
1) Windows Authentication cannot work because there is no domain
controller. Therefore SQL Server authentication must be used. We must
be sure that this is the only recourse before we abandon Windows
Authentication.
Or
2) Somehow the client's Windows Administrator account is not
recognized by the Server as having permission to create a database,
despite the fact that Windows Administrators should have that
permission by default.
Lou.

Q: Windows Authentication

Is Windows Authentication possible without a domain controller?
I am running a testbed with two Win2K machines without firewalls. One
computer contains the MSDE 2000A, set for Windows Authentication
only. Running MS Access on the other computer under the Administrator
account causes a connection failure error message:
Microsoft SQL Server Login
--
Connection failed:
SQLState: '01000'
SQL Server Error: 87
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen
(Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 6
[Microsoft][ODBC SQL Server Driver][DBNETLIB]Specified SQL serve
r not
found.
Lou Arnold,
Ottawa, CanadaPS...This is a peer-to peer network...no domain controller.
On Sun, 18 Jul 2004 03:53:19 GMT, Lou_Arnold@.nospam.com (Lou Arnold)
wrote:

>Is Windows Authentication possible without a domain controller?
>I am running a testbed with two Win2K machines without firewalls. One
>computer contains the MSDE 2000A, set for Windows Authentication
>only. Running MS Access on the other computer under the Administrator
>account causes a connection failure error message:
>Microsoft SQL Server Login
>--
>Connection failed:
>SQLState: '01000'
>SQL Server Error: 87
>[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen
>(Connect()).
>Connection failed:
>SQLState: '08001'
>SQL Server Error: 6
>[Microsoft][ODBC SQL Server Driver][DBNETLIB]Specified SQL serv
er not
>found.
>Lou Arnold,
>Ottawa, Canada|||Try substituting WORKGROUP\USERNAME for DOMAIN\USERNAME. Your error looks
like something other than authentication, however. The two machines can see
each other? Are they in the same workgroup? Maybe try connecting by IP
address instead of machine name and make sure your SQL Server service is
running.
Thanks,
Michael C.
"Lou Arnold" <Lou_Arnold@.nospam.com> wrote in message
news:40f9f68a.19289767@.nntp.flfrd.phub.net.cable.rogers.com...
> PS...This is a peer-to peer network...no domain controller.
> On Sun, 18 Jul 2004 03:53:19 GMT, Lou_Arnold@.nospam.com (Lou Arnold)
> wrote:
>
>|||Michael, Pls see my replies below.
On Sun, 18 Jul 2004 05:18:01 GMT, "Michael C" <nospam@.lol.net> wrote:

>Try substituting WORKGROUP\USERNAME for DOMAIN\USERNAME.
I don't understand where to specify this. There is no domain name as
there is no domain controller.

>Your error looks
>like something other than authentication, however.
> The two machines can see
>each other? Are they in the same workgroup? Maybe try connecting by IP
>address instead of machine name and make sure your SQL Server service is
>running.
Yes, the machines can see each other. File and Printer sharing is
enabled and i can see shares on each computer from the other.
Yes, The work group name WORKGROUP for each computer.
Yes, the SQL server instance is running. (it is a named instance)
Yes, I tried using <ipaddr>\<instancename> and got the same error
message.
Lou Arnold
Ottawa, Canada|||"Lou Arnold" <Lou_Arnold@.nospam.com> wrote in message
news:40fa18ff.473050@.nntp.flfrd.phub.net.cable.rogers.com...
> Michael, Pls see my replies below.
> On Sun, 18 Jul 2004 05:18:01 GMT, "Michael C" <nospam@.lol.net> wrote:
>
> I don't understand where to specify this. There is no domain name as
> there is no domain controller.
If you were connected to a Domain Controller, you would specify
DOMAIN\USERNAME. If you are working on a small LAN with no domain
controller, you can specify WORKGROUP\USERNAME instead; or possibly
MACHINENAME\USERNAME (like this: "MSHOME\BOB" or "COMPUTER1\BOB"). You
might also try connecting using the sa username/password.

> Yes, the machines can see each other. File and Printer sharing is
> enabled and i can see shares on each computer from the other.
> Yes, The work group name WORKGROUP for each computer.
> Yes, the SQL server instance is running. (it is a named instance)
> Yes, I tried using <ipaddr>\<instancename> and got the same error
> message.
>
Do you have a default instance running, or just a named instance? Try
connecting to just <ipaddr> if it's the default instance.
Cheers,
Michael C.|||In reply:
The instance is a single named instance.
I tried connecting with the SA username and password, but it failed
with the same error message. This was expected since the server is set
up for Windows Authentication only.
Re the Workgroup/Domain name: I understand your explanation, but I
still don't know where (or how) to enter the
workgroup-name/computer-name. Can you be specific about the window
and field that this info should be entered? I am still using the
ipaddr/instance-name in the MIcrosoft SQL Server Database Wizard
Dialog box. This box is the first box displayed when, in MS Access,
you try to create a new Access project. The field has the text label:
"What SQL Server would you like to use for this database?"
Lou
On Sun, 18 Jul 2004 17:42:49 GMT, "Michael C" <nospam@.lol.net> wrote:

>"Lou Arnold" <Lou_Arnold@.nospam.com> wrote in message
>news:40fa18ff.473050@.nntp.flfrd.phub.net.cable.rogers.com...
>If you were connected to a Domain Controller, you would specify
>DOMAIN\USERNAME. If you are working on a small LAN with no domain
>controller, you can specify WORKGROUP\USERNAME instead; or possibly
>MACHINENAME\USERNAME (like this: "MSHOME\BOB" or "COMPUTER1\BOB"). You
>might also try connecting using the sa username/password.
>
>Do you have a default instance running, or just a named instance? Try
>connecting to just <ipaddr> if it's the default instance.
>Cheers,
>Michael C.
>|||Michael...here are a few more details:
On the server computer, I have used the SQL Server Network Utility to
disable all but TCP/IP connections. Also, the server is set to use
port 1433. Is this appropriate?
On the client computer, I have used the SQL Server Client Network
Utility to disable all but TCP/IP, and to set the default port value
for TCP/IP to use 1433. Is this appropriate?
Lou.|||Michael...Sorry I was in error. I enabled File and Printer Sharing and
Client for MS Network on the server computer. Doing this got me past
the connect error I gave in the initial post. However, no database was
created, and no error message was generated. Again, I wonder if this a
Windows Authentication problem.
The symptom is now tthis:
The MS SQL Server Database Wizard apparently connects to the server,
after which a dialog box appears saying that it has all the info it
needs. When I Click Finish, a dialog box appears for a split second.
This dialog box is a progress bar that shows the progress of creating
the new database on the server. This bar shows no progress and quickly
disappears. Why does this happen?
Why is Client for MS Networks and File and Printer Sharing required to
make the connection to the server'
Lou Arnold|||OK, I'm a little lost now. I was under the assumption that you were trying
to connect to your SQL Server via SQL Enterprise Manager and set up
permissions on an account using that. Now I'm not so sure. Just a couple
of questions so I can try to help you a little better:
1. What exactly are you trying to do?
2. Do you have SQL Server 2K on one computer or both?
3. Are both computers in the same Workgroup (right-click on My Computer >
Properties > Computer Name)?
4. Are both computers set up in the same IP range with the same Subnet
(TCP/IP settings)?
5. Are you running any firewall software?
Thanks,
Michael C.
"Lou Arnold" <Lou_Arnold@.nospam.com> wrote in message
news:40fbcf8b.2586869@.nntp.flfrd.phub.net.cable.rogers.com...
> Michael...Sorry I was in error. I enabled File and Printer Sharing and
> Client for MS Network on the server computer. Doing this got me past
> the connect error I gave in the initial post. However, no database was
> created, and no error message was generated. Again, I wonder if this a
> Windows Authentication problem.
> The symptom is now tthis:
> The MS SQL Server Database Wizard apparently connects to the server,
> after which a dialog box appears saying that it has all the info it
> needs. When I Click Finish, a dialog box appears for a split second.
> This dialog box is a progress bar that shows the progress of creating
> the new database on the server. This bar shows no progress and quickly
> disappears. Why does this happen?
> Why is Client for MS Networks and File and Printer Sharing required to
> make the connection to the server'
> Lou Arnold|||Michael...see my replies below.
On Tue, 20 Jul 2004 00:36:08 GMT, "Michael C" <nospam@.lol.net> wrote:

>OK, I'm a little lost now. I was under the assumption that you were trying
>to connect to your SQL Server via SQL Enterprise Manager and set up
>permissions on an account using that. Now I'm not so sure. Just a couple
>of questions so I can try to help you a little better:
Don't blame you for being lost.

>1. What exactly are you trying to do?
The objective is to establish a testbed of two Win2K computers. This
is to be a peer network without a domain controller. The intent is to
establish a configuration whereby these two computers can be used for
development. The server is to be used with Windows Authentication
security only unless this proves impossible. We can play with settings
such as TCP/IP, File and Printer sharing and internet port numbers as
long as we establish a minimum configuration and the reason for each
setting.
>2. Do you have SQL Server 2K on one computer or both?
Only one computer (I'll call it the server computer) has the SQL
Server installed. Only one server is installed and this is a named
instance. The server is set to use port 1433. The other computer (the
client computer) has MS Access installed. This is a requirement for
this testbed. No other computers are connected to these computers.
Both computers are run only under the Windows Administrator account to
avoid the cofiguration of permissions.

>3. Are both computers in the same Workgroup (right-click on My Computer >
>Properties > Computer Name)?
Yes, both are in the same workgroup.

>4. Are both computers set up in the same IP range with the same Subnet
>(TCP/IP settings)?
Yes. they run thru a router and so have adjacent addresses, and the
subnet mask of 255.255.255.0. The router's internet connection is
disabled.
BTW: both TCP/IP and Named Pipes are enabled on both client and server
machines using the client and server network utilities.

>5. Are you running any firewall software?
No. No firewalls have been installed.
More info:
In my initial post, MS Access generated a connection error. After some
trials, it was found that networking components "File and Printer
Sharing" and "Client for MS Networks" had to be enabled on both
computers for the connection to work (why is unclear and must be
investigated). After enabling these two networking components, the
connection appears to succeed, but creation of the database fails and
no error message is generated.
In my mind are the following possible causes:
1) Windows Authentication cannot work because there is no domain
controller. Therefore SQL Server authentication must be used. We must
be sure that this is the only recourse before we abandon Windows
Authentication.
Or
2) Somehow the client's Windows Administrator account is not
recognized by the Server as having permission to create a database,
despite the fact that Windows Administrators should have that
permission by default.
--
Lou.