I have a SQL 7.0 Clustered Server with SP3. Sometimes a DB (16GB) becomes
suspect and the only way to get it back online is to reboot the server and
that gets it back to normal. This happens every week.
Any ideas?
Also can you tell me how to change the location where Microsoft Clustered
Server changes the Temporary file location. Currently on my server it is
c:\winnt which we want to change
Thanks
Rod
Rod,
You are probably better off calling Microsoft PSS to troubleshoot this
issue.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Rod wrote:
> I have a SQL 7.0 Clustered Server with SP3. Sometimes a DB (16GB) becomes
> suspect and the only way to get it back online is to reboot the server and
> that gets it back to normal. This happens every week.
> Any ideas?
> Also can you tell me how to change the location where Microsoft Clustered
> Server changes the Temporary file location. Currently on my server it is
> c:\winnt which we want to change
> Thanks
> Rod
Showing posts with label back. Show all posts
Showing posts with label back. Show all posts
Monday, March 19, 2012
CLUSTER
I have a SQL 7.0 Clustered Server with SP3. Sometimes a DB (16GB) becomes
suspect and the only way to get it back online is to reboot the server and
that gets it back to normal. This happens every week.
Any ideas?
Also can you tell me how to change the location where Microsoft Clustered
Server changes the Temporary file location. Currently on my server it is
c:\winnt which we want to change
Thanks
RodRod,
You are probably better off calling Microsoft PSS to troubleshoot this
issue.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Rod wrote:
> I have a SQL 7.0 Clustered Server with SP3. Sometimes a DB (16GB) becomes
> suspect and the only way to get it back online is to reboot the server and
> that gets it back to normal. This happens every week.
> Any ideas?
> Also can you tell me how to change the location where Microsoft Clustered
> Server changes the Temporary file location. Currently on my server it is
> c:\winnt which we want to change
> Thanks
> Rod
suspect and the only way to get it back online is to reboot the server and
that gets it back to normal. This happens every week.
Any ideas?
Also can you tell me how to change the location where Microsoft Clustered
Server changes the Temporary file location. Currently on my server it is
c:\winnt which we want to change
Thanks
RodRod,
You are probably better off calling Microsoft PSS to troubleshoot this
issue.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Rod wrote:
> I have a SQL 7.0 Clustered Server with SP3. Sometimes a DB (16GB) becomes
> suspect and the only way to get it back online is to reboot the server and
> that gets it back to normal. This happens every week.
> Any ideas?
> Also can you tell me how to change the location where Microsoft Clustered
> Server changes the Temporary file location. Currently on my server it is
> c:\winnt which we want to change
> Thanks
> Rod
Friday, February 24, 2012
clients sometimes get locked and can't write
I have an SQL 2000 back end. We have a couple of databases with about 12-20
tables a piece. About once or twice a month there are times for up to an
hour or so where no one can write from any of the front end applications to
the SQL 2000 back end. Each application gives their own error which all are
basically a time out waiting to write. Often times the system will just
start working again on its own.
When this happens the first thing we check in the Enterprise Manager is for
any locks and there are none. We then check to see if one of the other
applications like Access 2003, Labview or others can write to the database
and we see they cannot. Next we see if we can open the table on the SQL
server and edit or append and we CAN from the Enterprise Manager?
Thinking that there might be someone locking a record or a page we kick
everyone out and just let one person (sometimes myself as an admin) try to
work and they cannot. We then restart the SQL server and the workstations
and have someone try again and they still fail.
The only thing that I have seen help get it out of this state is when I go
to my daily maintenance jobs and run both my integrity check and my
optimization plan. The Integrety Check plan was done with the wizard and
it:
1. Checks the integrity of all user database
2. Includes indexes
3. Attempts to repair minor problems.
4. Run every day at 12:00 AM
The Optimization plan is set to:
1. Reorganize Data and Index Pages
2. Change free space to 10%
3. Run every day at 1:30 AM
Finally, when I look in the Event Viewer logs for anything strange I really
do not see anything in the app, security, or system logs anywhere near the
time of the start of the errors.
Sounds like the SQL Server Agents for the SQL Server instances aren't
running sometimes. Goto start->administrative tools->services and
look for the SQL Server Agent (your server instance name) entries and
see their status. Should be in "Started" state. If not started,
click on the entry and click start in top left corner of pane.
SQL Server Agents are the programs that act as proxies to enable
remote access to a SQL server instance. If they are not running,
nobody will be able to gain access to the server, and will receive
time out errors instead.
Some programs, such as backups, may stop the agents so they can take a
snapshot of the database. These programs should start the agents as
soon as they are done. If you find the agents in a stopped state in
the next outage, you should try to trace down what program was
executing at the time they were stopped, and check if that program is
configured properly.
|||I don't think it is the agent because the users are able to read the data
remotely. Also, the only maintenance that is done is done at 1-3 AM. This
problem happens randomly mid day.
"Andy" <anedza@.infotek-consulting.com> wrote in message
news:e1159a72-4a2a-449d-a8d7-d22be76d6595@.q78g2000hsh.googlegroups.com...
> Sounds like the SQL Server Agents for the SQL Server instances aren't
> running sometimes. Goto start->administrative tools->services and
> look for the SQL Server Agent (your server instance name) entries and
> see their status. Should be in "Started" state. If not started,
> click on the entry and click start in top left corner of pane.
> SQL Server Agents are the programs that act as proxies to enable
> remote access to a SQL server instance. If they are not running,
> nobody will be able to gain access to the server, and will receive
> time out errors instead.
> Some programs, such as backups, may stop the agents so they can take a
> snapshot of the database. These programs should start the agents as
> soon as they are done. If you find the agents in a stopped state in
> the next outage, you should try to trace down what program was
> executing at the time they were stopped, and check if that program is
> configured properly.
>
>
>
tables a piece. About once or twice a month there are times for up to an
hour or so where no one can write from any of the front end applications to
the SQL 2000 back end. Each application gives their own error which all are
basically a time out waiting to write. Often times the system will just
start working again on its own.
When this happens the first thing we check in the Enterprise Manager is for
any locks and there are none. We then check to see if one of the other
applications like Access 2003, Labview or others can write to the database
and we see they cannot. Next we see if we can open the table on the SQL
server and edit or append and we CAN from the Enterprise Manager?
Thinking that there might be someone locking a record or a page we kick
everyone out and just let one person (sometimes myself as an admin) try to
work and they cannot. We then restart the SQL server and the workstations
and have someone try again and they still fail.
The only thing that I have seen help get it out of this state is when I go
to my daily maintenance jobs and run both my integrity check and my
optimization plan. The Integrety Check plan was done with the wizard and
it:
1. Checks the integrity of all user database
2. Includes indexes
3. Attempts to repair minor problems.
4. Run every day at 12:00 AM
The Optimization plan is set to:
1. Reorganize Data and Index Pages
2. Change free space to 10%
3. Run every day at 1:30 AM
Finally, when I look in the Event Viewer logs for anything strange I really
do not see anything in the app, security, or system logs anywhere near the
time of the start of the errors.
Sounds like the SQL Server Agents for the SQL Server instances aren't
running sometimes. Goto start->administrative tools->services and
look for the SQL Server Agent (your server instance name) entries and
see their status. Should be in "Started" state. If not started,
click on the entry and click start in top left corner of pane.
SQL Server Agents are the programs that act as proxies to enable
remote access to a SQL server instance. If they are not running,
nobody will be able to gain access to the server, and will receive
time out errors instead.
Some programs, such as backups, may stop the agents so they can take a
snapshot of the database. These programs should start the agents as
soon as they are done. If you find the agents in a stopped state in
the next outage, you should try to trace down what program was
executing at the time they were stopped, and check if that program is
configured properly.
|||I don't think it is the agent because the users are able to read the data
remotely. Also, the only maintenance that is done is done at 1-3 AM. This
problem happens randomly mid day.
"Andy" <anedza@.infotek-consulting.com> wrote in message
news:e1159a72-4a2a-449d-a8d7-d22be76d6595@.q78g2000hsh.googlegroups.com...
> Sounds like the SQL Server Agents for the SQL Server instances aren't
> running sometimes. Goto start->administrative tools->services and
> look for the SQL Server Agent (your server instance name) entries and
> see their status. Should be in "Started" state. If not started,
> click on the entry and click start in top left corner of pane.
> SQL Server Agents are the programs that act as proxies to enable
> remote access to a SQL server instance. If they are not running,
> nobody will be able to gain access to the server, and will receive
> time out errors instead.
> Some programs, such as backups, may stop the agents so they can take a
> snapshot of the database. These programs should start the agents as
> soon as they are done. If you find the agents in a stopped state in
> the next outage, you should try to trace down what program was
> executing at the time they were stopped, and check if that program is
> configured properly.
>
>
>
clients sometimes get locked and can't write
I have an SQL 2000 back end. We have a couple of databases with about 12-20
tables a piece. About once or twice a month there are times for up to an
hour or so where no one can write from any of the front end applications to
the SQL 2000 back end. Each application gives their own error which all are
basically a time out waiting to write. Often times the system will just
start working again on its own.
When this happens the first thing we check in the Enterprise Manager is for
any locks and there are none. We then check to see if one of the other
applications like Access 2003, Labview or others can write to the database
and we see they cannot. Next we see if we can open the table on the SQL
server and edit or append and we CAN from the Enterprise Manager'
Thinking that there might be someone locking a record or a page we kick
everyone out and just let one person (sometimes myself as an admin) try to
work and they cannot. We then restart the SQL server and the workstations
and have someone try again and they still fail.
The only thing that I have seen help get it out of this state is when I go
to my daily maintenance jobs and run both my integrity check and my
optimization plan. The Integrety Check plan was done with the wizard and
it:
1. Checks the integrity of all user database
2. Includes indexes
3. Attempts to repair minor problems.
4. Run every day at 12:00 AM
The Optimization plan is set to:
1. Reorganize Data and Index Pages
2. Change free space to 10%
3. Run every day at 1:30 AM
Finally, when I look in the Event Viewer logs for anything strange I really
do not see anything in the app, security, or system logs anywhere near the
time of the start of the errors.Sounds like the SQL Server Agents for the SQL Server instances aren't
running sometimes. Goto start->administrative tools->services and
look for the SQL Server Agent (your server instance name) entries and
see their status. Should be in "Started" state. If not started,
click on the entry and click start in top left corner of pane.
SQL Server Agents are the programs that act as proxies to enable
remote access to a SQL server instance. If they are not running,
nobody will be able to gain access to the server, and will receive
time out errors instead.
Some programs, such as backups, may stop the agents so they can take a
snapshot of the database. These programs should start the agents as
soon as they are done. If you find the agents in a stopped state in
the next outage, you should try to trace down what program was
executing at the time they were stopped, and check if that program is
configured properly.|||I don't think it is the agent because the users are able to read the data
remotely. Also, the only maintenance that is done is done at 1-3 AM. This
problem happens randomly mid day.
"Andy" <anedza@.infotek-consulting.com> wrote in message
news:e1159a72-4a2a-449d-a8d7-d22be76d6595@.q78g2000hsh.googlegroups.com...
> Sounds like the SQL Server Agents for the SQL Server instances aren't
> running sometimes. Goto start->administrative tools->services and
> look for the SQL Server Agent (your server instance name) entries and
> see their status. Should be in "Started" state. If not started,
> click on the entry and click start in top left corner of pane.
> SQL Server Agents are the programs that act as proxies to enable
> remote access to a SQL server instance. If they are not running,
> nobody will be able to gain access to the server, and will receive
> time out errors instead.
> Some programs, such as backups, may stop the agents so they can take a
> snapshot of the database. These programs should start the agents as
> soon as they are done. If you find the agents in a stopped state in
> the next outage, you should try to trace down what program was
> executing at the time they were stopped, and check if that program is
> configured properly.
>
>
>
tables a piece. About once or twice a month there are times for up to an
hour or so where no one can write from any of the front end applications to
the SQL 2000 back end. Each application gives their own error which all are
basically a time out waiting to write. Often times the system will just
start working again on its own.
When this happens the first thing we check in the Enterprise Manager is for
any locks and there are none. We then check to see if one of the other
applications like Access 2003, Labview or others can write to the database
and we see they cannot. Next we see if we can open the table on the SQL
server and edit or append and we CAN from the Enterprise Manager'
Thinking that there might be someone locking a record or a page we kick
everyone out and just let one person (sometimes myself as an admin) try to
work and they cannot. We then restart the SQL server and the workstations
and have someone try again and they still fail.
The only thing that I have seen help get it out of this state is when I go
to my daily maintenance jobs and run both my integrity check and my
optimization plan. The Integrety Check plan was done with the wizard and
it:
1. Checks the integrity of all user database
2. Includes indexes
3. Attempts to repair minor problems.
4. Run every day at 12:00 AM
The Optimization plan is set to:
1. Reorganize Data and Index Pages
2. Change free space to 10%
3. Run every day at 1:30 AM
Finally, when I look in the Event Viewer logs for anything strange I really
do not see anything in the app, security, or system logs anywhere near the
time of the start of the errors.Sounds like the SQL Server Agents for the SQL Server instances aren't
running sometimes. Goto start->administrative tools->services and
look for the SQL Server Agent (your server instance name) entries and
see their status. Should be in "Started" state. If not started,
click on the entry and click start in top left corner of pane.
SQL Server Agents are the programs that act as proxies to enable
remote access to a SQL server instance. If they are not running,
nobody will be able to gain access to the server, and will receive
time out errors instead.
Some programs, such as backups, may stop the agents so they can take a
snapshot of the database. These programs should start the agents as
soon as they are done. If you find the agents in a stopped state in
the next outage, you should try to trace down what program was
executing at the time they were stopped, and check if that program is
configured properly.|||I don't think it is the agent because the users are able to read the data
remotely. Also, the only maintenance that is done is done at 1-3 AM. This
problem happens randomly mid day.
"Andy" <anedza@.infotek-consulting.com> wrote in message
news:e1159a72-4a2a-449d-a8d7-d22be76d6595@.q78g2000hsh.googlegroups.com...
> Sounds like the SQL Server Agents for the SQL Server instances aren't
> running sometimes. Goto start->administrative tools->services and
> look for the SQL Server Agent (your server instance name) entries and
> see their status. Should be in "Started" state. If not started,
> click on the entry and click start in top left corner of pane.
> SQL Server Agents are the programs that act as proxies to enable
> remote access to a SQL server instance. If they are not running,
> nobody will be able to gain access to the server, and will receive
> time out errors instead.
> Some programs, such as backups, may stop the agents so they can take a
> snapshot of the database. These programs should start the agents as
> soon as they are done. If you find the agents in a stopped state in
> the next outage, you should try to trace down what program was
> executing at the time they were stopped, and check if that program is
> configured properly.
>
>
>
Client Tools for SQL Express
I am looking for information on Client tools for SQL Express. I am mainly looking for a way to script out the objects and then Add them back into a new file. I wish to do this so that I can ship the SQL Scripts for an application so that the user can load them up once distributed, and also to allow me to create the objects and load them at design time. I used to be able to have a common set of tables that I would use inside applications, and when working on a project load them if they were needed.
One of the other reasons is the problem with the Beta2 and RC engines and the changes that have been made. I know that the two versions do not work well together and I want to be able to script out the objects and put them into either the RC or in turn the RTM Version.
I know that there are the management tools that ship with the full sql product (Not Express), but I fell that there should not be a need to install these as there should be some command line tools that can do the job. I have seen the command line tool on the MSDN Download site, but could not see how to script out the objects.
One of the other reasons is the problem with the Beta2 and RC engines and the changes that have been made. I know that the two versions do not work well together and I want to be able to script out the objects and put them into either the RC or in turn the RTM Version.
I know that there are the management tools that ship with the full sql product (Not Express), but I fell that there should not be a need to install these as there should be some command line tools that can do the job. I have seen the command line tool on the MSDN Download site, but could not see how to script out the objects.
Maybe I could use the SQLCMD tool but I can not work out how to connect to the mdf file as I do not have a server running as it is the express edition. (Even though it ships with the express edition).I'm not sure I understand the following statement: "Maybe I could use the SQLCMD tool but I can not work out how to connect to the mdf file as I do not have a server running as it is the express edition."
In order to use SQL Server Express the SQL Server service must be running. Once it's running you can connect using SQLCMD (sqlcmd -S .\SQLEXPRESS -E).
Best of luck,
Dan|||Thanks for that, I have been able to connect to the SQL Express engine using the SQLEUtil (I think thats it) that you can download from the Microsoft downloads site, but still trying to script out the database objects.
What I have started looking at is the SQL-SMO System (http://www.ircomm.net/blogs/mykre/archive/2005/10/18/615.aspx), with this I hope to develop a system that I can use to script out the Database objects (Table structure and all). This way I will be able to use this system to store my SQL Scripts in a source code management system, or publish the scripts that I develop with my applications.
One of the main reasons at present is that I have been running Beta 2 of the framework at home, and am now running the RC version at work. When I tried to move an application from home to work the MDF Files where not compatible and I needed to recreate them. As the Release draws near I am worried as I have Beta 2 database files that I am working with and when new version is released how am I going to recreate the files.
I also can for see a problem here at work which I have posted in the following post, http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=111170.
Thursday, February 16, 2012
Client Network Utility Service Pack
2 Questions:
1) I am getting back into SQL more than before, in my new job. I need to find the service pack installed on the clients who have the Client Network Utility installed. I do not remember how to do this.
2) Running 'Select @.@.VERSION' on the server returns 7.00.1063 but does not indicate the service pack. Does this still mean sp4 has been installed?
I'm trying to ensure we'll all up to date since our dual 700 procs are acting eratic...jumps between 10 - 95% or so.
Server info:
NT Server SP6
SQL 7.0
2GB Ram
2 procs @. 700Mhz
Roughly 80 network connections.
No other programs running on server except Antivirus.
Thank you!Yes - sp4 is installed. Also, antivirus can cause several issues with any application. When you say jumping from 10% to 95%, are you isolating the application that is causing this ?|||Originally posted by rnealejr
Yes - sp4 is installed. Also, antivirus can cause several issues with any application. When you say jumping from 10% to 95%, are you isolating the application that is causing this ?
Thanks for the reply! Based on the Perf Monitor, sqlservr.exe uses up most of the CPU. VNC is what I am using to connect to it to monitor it remotely, which does take up some of the CPU. There are only a couple other programs that will take up 1 or 2 of the CPU, but that doesn't even seem worthy of mentioning.
There is only one database that is about 4.5 GB large. It is essentially an out of the box CRM system database, not custom built.
I have read an online resource for using Performance Monitor which was very helpful, but I haven't been able to determine what exactly SQL is doing to cause it to spike.
There are no jobs running while I am monitoring the performance. Memory doesn't seem to be a problem at all, and my indexes appear to be fine.
Thanks again!|||I would trash vnc and install terminal services (the administrative mode /not application) to remotely connect to your sql server machine. vnc causes cpu spikes. rtvscan is an antivirus application that causes spikes as well. When it hits 95% what applications are consuming the resource (is it only sql) ?
1) I am getting back into SQL more than before, in my new job. I need to find the service pack installed on the clients who have the Client Network Utility installed. I do not remember how to do this.
2) Running 'Select @.@.VERSION' on the server returns 7.00.1063 but does not indicate the service pack. Does this still mean sp4 has been installed?
I'm trying to ensure we'll all up to date since our dual 700 procs are acting eratic...jumps between 10 - 95% or so.
Server info:
NT Server SP6
SQL 7.0
2GB Ram
2 procs @. 700Mhz
Roughly 80 network connections.
No other programs running on server except Antivirus.
Thank you!Yes - sp4 is installed. Also, antivirus can cause several issues with any application. When you say jumping from 10% to 95%, are you isolating the application that is causing this ?|||Originally posted by rnealejr
Yes - sp4 is installed. Also, antivirus can cause several issues with any application. When you say jumping from 10% to 95%, are you isolating the application that is causing this ?
Thanks for the reply! Based on the Perf Monitor, sqlservr.exe uses up most of the CPU. VNC is what I am using to connect to it to monitor it remotely, which does take up some of the CPU. There are only a couple other programs that will take up 1 or 2 of the CPU, but that doesn't even seem worthy of mentioning.
There is only one database that is about 4.5 GB large. It is essentially an out of the box CRM system database, not custom built.
I have read an online resource for using Performance Monitor which was very helpful, but I haven't been able to determine what exactly SQL is doing to cause it to spike.
There are no jobs running while I am monitoring the performance. Memory doesn't seem to be a problem at all, and my indexes appear to be fine.
Thanks again!|||I would trash vnc and install terminal services (the administrative mode /not application) to remotely connect to your sql server machine. vnc causes cpu spikes. rtvscan is an antivirus application that causes spikes as well. When it hits 95% what applications are consuming the resource (is it only sql) ?
Subscribe to:
Posts (Atom)