problem in CPU utilization

I have windows 2003 server with SQL Server installed on it for live calls billing but the CPU utilization is reaching the maximam and it's average above 60% which is causing lot of problems specially for the live environment. I have enough memory and free hard disk space is more than 40GB,

so where is the problem?!

Have you run done any performance analysis? Is SQL Server the only application running on the server? Have you looked for any long running queries that might cause the problem? Have you look for blocks and locking issues? Have you kept the server and SQL Server up to date will all Service Packs, and patches? You need to provide a little more information to get any kind of usefull answer to your question.

Brad Feaker|||

the problem solved.

There ware triggers running every second on the server

problem in CPU utilization

I have windows 2003 server with SQL Server installed on it for live calls billing but the CPU utilization is reaching the maximam and it's average above 60% which is causing lot of problems specially for the live environment. I have enough memory and free hard disk space is more than 40GB,

so where is the problem?!

Have you run done any performance analysis? Is SQL Server the only application running on the server? Have you looked for any long running queries that might cause the problem? Have you look for blocks and locking issues? Have you kept the server and SQL Server up to date will all Service Packs, and patches? You need to provide a little more information to get any kind of usefull answer to your question.

Brad Feaker
|||

the problem solved.

There ware triggers running every second on the server

Problem creating ASPNETDB under SQL Server 2005

Hi All... We're cloning an application currently under development on Server 2003 / SQL Server 2005 / dotnet 2.0. The clone's going to live on an XPSP2 box with SQL Server 2003 - it's for demo purposes... The application's able to get to our own database, but it's having a hard time creating the ASPNETDB that dot net likes to have.

Aside from the OS, the only difference between the two SQL Servers is that on the working system, we're using windows authentication on the database while on the non-working system, we're using SQL Server authentication. But we've tuned the connection strings appropriately - again, we can get to our own db just fine.

We have the following lines in our web.config:

<connectionstrings>
<clear />
<add name="LocalSqlServer" connectionstring="Server=localhost; Database=ASPNETDB; UID=sa; PWD=mypassword" />
</connectionstring>

On the working system, the Server is an actual IP address, integrated security is set to true, and of course the uid/pwd is a bit different. But again, using a very similar connection string, we able to get to OUR database on the non-working system...

The error we're getting at runtime is:

Cannot open database "ASPNETDB" requested by the login. The login failed. Login failed for user 'sa'.

When we poke into the database from SQL Server Management Studio - on a remote machine - we can see our own database is there, but the ASPNETDB isnt there. Yet... I suspect it failing getting in to just create the db...

Any thoughts? Thanks for the help!!! -- Curt

Did you Attach the aspnet db to the server?

|||

Thanks for the reply, Lock. Good question - and the answer is no. I did that and it worked. I guess somehow I thought ASPNET would create the database if it wasnt there - after all, I swear when using 2005 Express, if I delete the mdf, it magically comes back. Perhaps not... Back on my bike though - many thanks. -- Curt

Problem connection to FoxPro database via ole db

Hi,
I'm accessing a FoxPro database via ole db and ths works fine on my local
report server. However, when I deploy the report to the live report server
I'm getting the error 'Invalid path or file name'
The FoxPro database is on a separate server and the connection string is :
string connectionString = @."provider=vfpoledb;" +
@."data source='\\server\data\foxpro.dbc';" +
"password='';user id=''";
I've read a few articles explaining that it's a permissions problem. I've
tried granting full permissions to the data folder for myself and 'Network
Service' but this still occurs. The web.config file for the report server has
impersonate set to true and IIS is configured for 'Integrated Windows
authentication' and does not use anonymous access.
Any ideas would be much appreciated.
Regards
MikeHi Mike,
Does the report server's account have permissions to the directory?
--
Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy_winegarden@.msn.com www.cindywinegarden.com
"MikeD" <MikeD@.discussions.microsoft.com> wrote in message
news:9A295512-41F7-48A0-B406-08AE86F55CA8@.microsoft.com...
> Hi,
> I'm accessing a FoxPro database via ole db and ths works fine on my local
> report server. However, when I deploy the report to the live report server
> I'm getting the error 'Invalid path or file name'
> The FoxPro database is on a separate server and the connection string is :
> string connectionString = @."provider=vfpoledb;" +
> @."data source='\\server\data\foxpro.dbc';" +
> "password='';user id=''";
> I've read a few articles explaining that it's a permissions problem. I've
> tried granting full permissions to the data folder for myself and 'Network
> Service' but this still occurs. The web.config file for the report server
> has
> impersonate set to true and IIS is configured for 'Integrated Windows
> authentication' and does not use anonymous access.
> Any ideas would be much appreciated.
> Regards
> Mike