Michael,
Mmm. Topic changes.
1. Ok, I have never seen problem 1, but I found this thread:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1404000&SiteID=1
Here the solution seems to have been to install SQL Server 2005 SP2 and make
sure to install SP2 for the client tools as well, not just the server.
(Synopsis of thread.)
So, your first problem could possibly be aggravated by a server / client
tools mismatch.
2. Log is getting huge. Leads to the standard log questions.
How often do you do log backups? If you are reloading the database daily
(Is that what you mean by 'put data in the database every day') should you
be running the BULK-LOGGED (or if you don't need the logs, SIMPLE) recovery
model for this database?
Do you have an old transaction still open? DBCC OPENTRAN(DatabaseName) will
tell you about the oldest open transaction.
(The transaction log can grow to many times the size of the database if not
backed up regularly. It just keeps growing and growing and growing. Also,
if I update the current date column on a million rows, the database will not
change size, but the transaction log will now grow by two million rows
(before and after images) plus overhead.)
RLF
Post by MichaelMany thanks again for the support.
We only use TCP/IP protocol and disable Named Piped. There are other
problems with this new database, which maybe are related each other.
1. We could not create maintenance plan, the error message shows
Could not load type"Microsoft
.SqlServer.Management.Smo.Agent.JobBaseConnection'from assembly
'Microsoft.SqlServer.Smo,
Version=9.0.242.0,Culture=neutral.PublicKeyToken=89845dcd8080cc91'.
[Microsoft.SqlServer.MaintenancePlanTasks]
2. The transaction log boosts dramatically but database file keeps the same
in the last two weeks.
We migrated the database from previous server to the current server two
weeks ago, and we put the data into the database everyday. But when I check
the size of database and transaction log, the transaction log boosts from
73MB to 6GB whereas the primary file keeps the same, doesn't increase.
I think something wrong with this database, but don't know how to fix it.
Post by Russell FieldsCould be load balancing between NICs. Is TCP/IP your primary protocol or
Named Pipes? Make TCP/IP first if it is not. Et cetera.
RLF
Post by MichaelMany thanks for your reply. At frist, I thought it was the network problem. I
changed the newtwork switch, cable and network card for new server. But it
didn't work. So I think it is still a SQL sever issue.
Post by Russell FieldsMichael,
This message generally means that your network is having a problem,
not
the
SQL Server. If the network connections are unstable, you will have this
problem. Talk to the network guys about what is going on.
RLF
Post by MichaelWe have accounting system, APS, which is sitted in SQL2005 stnd.
Last
week,
because of shortage of hardware resource, we move the whole database
to
new
server. there is no error in the first week after migration. But
later,
most
of client users have been getting the error message sereral times
casually
a
day. The error messages as below
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionWrite
(send()).NumADOErrors:2 err(10054) [Microsoft][ODBC SQL Server
Driver][DBNETLIB]ConnectionWrite (send()). err(11) [Microsoft][ODBC SQL
Server Driver][DBNETLIB]General network error. Check your network
documentation.
Is someone here to help me to fix this issue?
Notes: previous server is SQL 2005 workgroup but current server is
SQL
2005
stnd.
Many thanks in advance