Sponsored Links


  • 1. SQL 2005 Express Install issue on Vista 32bit
    Hi, I hope someone can help or shed some light on what is gonig wrong for me here! I am attempting to install SQL 2005 Express (I know that I will need to install SP2 post intall if I ever get that far haha!) but I keep on hitting the followiong brick wall: The installer installs the componants but once it gets to configuring the SQL Server I get: SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user 'sa'. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online. I have uninstalled several times and deleted the folders, rebooted looked for SQL reporter services but still to no avail! I have an install file from an application that installs SQL 2005 EX with sp2 and even when I try that file I hit exactly the same brickwall! I am completely out of ideas and just dont know enough about Vista to make any more educated guesses. Anyone got any ideas or help? Thanks in advance, VivyG
  • 2. How do I remove my development server log from my client site during login?
    Hi all. I have devleoped a MSSQL 2005 database for my client. I detached and copied the mdf and ldf files a CD then attached to my clients MSSQL. However when logging in it shows a list of servers and my server is on the list. How do I remove /edit this ? This happends after we have connected to MSSQL and are now attempting to connect to the database it seems. Clear as mud? It has to be something in the mdf or ldf files because it is the name of my server at my office and nothing at my client matches. Robert
  • 3. SQL Server Upgrade
    Hi All, I have a SQL server 2000(standard edition) running on Windows 2000 server. I want to upgrade the SQL server 2000 to SQL server 2000 Enterprise edition and upgrade the OS to Windows 2003 Enterprise server in order to increase scalability. My db size is 60 GB now. Can anyone tell how the migration can be done effectively with lesser server downtime. Regards, Manoharan


Postby Frank Leake » Fri, 17 Oct 2003 00:17:36 GMT

 I have a number of jobs I've added to the SqlServerAgent.  Most of these
run continuously.  However, after starting 12 of them, subsequent jobs get a
'Waiting for worker thread'.   I've upped the # of worker threads from 255
gradually up to 1000, but still get exactly the same message.

Any idea how to fix this?


Re: SQLScheduler

Postby Sue Hoegemeier » Fri, 17 Oct 2003 00:57:12 GMT

The worker threads for SQL Server doesn't have anything to
do with the issue with Agent jobs. The registry has entries
for SQL Agent subsystems which control the maximum number of
worker threads for each subsystem - CmdExec, ActiveX and
there is a default for T-SQL of 20 but the key can be added
in the registry to change the maximum number of threads for
this subsystem. CmdExec and ActiveX are set to 10 by default
so I'd guess you have some type of combination of jobs where
one of the subsystems worker threads is hitting the max. 
The subsystem settings for a default install of SQL 2000 are
The last number of the in the registry string for the
individual subsystems control the max worker threads for
that subsystem. If you change the number, you have restart
SQL Server Agent for the changes to take effect.
You can also view the max worker threads per subsystem by


On Wed, 15 Oct 2003 10:17:36 -0500, "Frank Leake"



Who is online

Users browsing this forum: No registered users and 89 guest