Cluster question

Our company are looking at purchasing 2 new servers. One will hold the databases the other will be purely an application server which amongst other things will access the database. If we cluster the two servers and setup sql server active/passive clusteri
ng can we continue to use 2nd node as application server but as failover for sql server?
Yes it is possible, but you would have to have enough resources to run all
the applications. BTW, I think you don't quite understand the
term-active-active. That refers to a specific SQL 7.0 technology that
allowed each nost node to run a separate instance. SQL 2000 either has
single-instance or multi-instance clustering with the host nodes as complete
peers.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"bert" <anonymous@.discussions.microsoft.com> wrote in message
news:3C41330A-E708-40F3-B957-5AF11CC5B984@.microsoft.com...
> Our company are looking at purchasing 2 new servers. One will hold the
databases the other will be purely an application server which amongst other
things will access the database. If we cluster the two servers and setup sql
server active/passive clustering can we continue to use 2nd node as
application server but as failover for sql server?

Cluster Instance Naming

I have a 2 node cluster - may be grown to more node ... would like to
install 4 instances, to separate databases by SLA's and workload priority
....
What are suggested naming conventions ?
I have
DBINST1 - instance 1
DBINST2\I2 - instance 2
DBINST3\I3 - instance 3
DBINST4\I4 - instance 4
Servers are 8CPU, 16GB RAM each
Just to keep things consistant, I only use Named Instances on a cluster.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
CareerBuilder.com
"Seme Rollansa" <bukusu@.gmail.com> wrote in message
news:uietPVC%23FHA.1988@.TK2MSFTNGP12.phx.gbl...
>I have a 2 node cluster - may be grown to more node ... would like to
>install 4 instances, to separate databases by SLA's and workload priority
>...
> What are suggested naming conventions ?
> I have
> DBINST1 - instance 1
> DBINST2\I2 - instance 2
> DBINST3\I3 - instance 3
> DBINST4\I4 - instance 4
> Servers are 8CPU, 16GB RAM each
>
>
|||We usually keep the default instance around just incase there are systems
out there that can not connect to a Named Instance--and there are.
As far as naming conventions go, you have virtual server names that should
follow your organization's internal server name policies, regardless of SQL
Server, then the instance names should distinguish themselves.
Two schools of thought here. One is to keep the names meaningless other
than some sort of ordering convention as you've indicated as a security
precautions. The other school of thought recommends a meaningful name that
would connote the use of the system.
In either case, as Geoff suggests, keep it consistent.
Take your pick.
Sincerely,
Anthony Thomas

"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:usi761Q%23FHA.916@.TK2MSFTNGP10.phx.gbl...
> Just to keep things consistant, I only use Named Instances on a cluster.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> CareerBuilder.com
> "Seme Rollansa" <bukusu@.gmail.com> wrote in message
> news:uietPVC%23FHA.1988@.TK2MSFTNGP12.phx.gbl...
>
sqlsql

Clueless ... SBA and ACCESS

Hello,

Hopefully I'm near the right discussion group.

I'm trying to get started with integrating some of my manufacturing company's ACCESS databases with Microsoft's Small Business Accounting (SBA). The SDK for SBA provides plenty of VB code one I get past a certain point.

Can ACCESS be used as a front end for SBA?

Can anyone offer a sample .mdb with code that logs in to the db and adds a new customer (for example)?

TIA

rick

Definitely not the right group, Rick, as Access/VBA can not directly use ADO.NET. I don't know much about SBA, but I took a quick look, and on my system SBA stores its data in a SQL Server instance called ServerName\MICROSOFTSMLBIZ. You should, as far as I know, be able to connect to it from Access using any of the standard methods commonly used to connect to any SQL Server database, e.g. ADP, ODBC-linked tables, or programmatically via ADO 'classic' or DAO. If you haven't already done so, try asking in a forum dealing with Access ADPs or Access and ODBC. -- Brendan Reynolds Access MVP wrote in message news:6f240fe4-d011-4650-a122-ad993505a198@.discussions.microsoft.com...
> Hello, >
> Hopefully I'm near the right discussion group. >
> I'm trying to get started with integrating some of my manufacturing
> company's ACCESS databases with Microsoft's Small Business Accounting
> (SBA). The SDK for SBA provides plenty of VB code one I get past a
> certain point. >
> Can ACCESS be used as a front end for SBA? >
> Can anyone offer a sample .mdb with code that logs in to the db and adds
> a new customer (for example)? >
> TIA > > >
> rick >
>

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.
>
>
>

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.
>
>
>