I have SQL Server 2005 and Visual Studio .NET 2005 installed on my
developer PC. I installed SQL Server 2005 SP2 last week and installed
Avast Antivirus this week. What I noticed was that after my reboot, I
could not get SQL Server to start. In the Surface Area Configuration,
I was getting error messages in regards to me not having permission to
start the service.
So I uninstalled Avast Antivirus (Home Edition btw), and rebooted.
Alas, SQL Server 2005 was starting up again!
I use AVG Antivirus (free of course), and was wondering if anybody
else out there has had similar problems? Is it just Avast?
Thanks."tofu.captain" <tofu.captain@.gmail.com> wrote in message
news:1176693441.180857.3870@.w1g2000hsg.googlegroups.com...
>I have SQL Server 2005 and Visual Studio .NET 2005 installed on my
> developer PC. I installed SQL Server 2005 SP2 last week and installed
> Avast Antivirus this week. What I noticed was that after my reboot, I
> could not get SQL Server to start. In the Surface Area Configuration,
> I was getting error messages in regards to me not having permission to
> start the service.
> So I uninstalled Avast Antivirus (Home Edition btw), and rebooted.
> Alas, SQL Server 2005 was starting up again!
> I use AVG Antivirus (free of course), and was wondering if anybody
> else out there has had similar problems? Is it just Avast?
Generally suggest not running an AV on a SQL Server. At the very least
suggest telling it to not scan the databases.
> Thanks.
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||Hi
"tofu.captain" wrote:
> I have SQL Server 2005 and Visual Studio .NET 2005 installed on my
> developer PC. I installed SQL Server 2005 SP2 last week and installed
> Avast Antivirus this week. What I noticed was that after my reboot, I
> could not get SQL Server to start. In the Surface Area Configuration,
> I was getting error messages in regards to me not having permission to
> start the service.
> So I uninstalled Avast Antivirus (Home Edition btw), and rebooted.
> Alas, SQL Server 2005 was starting up again!
> I use AVG Antivirus (free of course), and was wondering if anybody
> else out there has had similar problems? Is it just Avast?
> Thanks.
>
As this is a developer PC you probably do want to install an antivirus
program, but as Greg says do not scan the database files as SQL Server will
require exclusive access to these files. I would expect user databases to be
marked as suspect if the scan was occurring during start up, but SQL Server
may still start therefore the error message seems slightly spurious. Have yo
u
checked the SQL Server log and the event log for any additional information?
John
No comments:
Post a Comment