Applying SQL hotfixes to a SQL cluster

Gurus,
Running two instances of SQL on a SQL Server 2000 cluster. Windows Server
2003 SP1 is the OS. Are there any special rules I must follow to execute
the SQL hotfix on each node of the cluster? I am assuming I just need to
apply the SQL hotfix to each cluster node and that's it. I am hoping it is
that easy.
SpinRecent hotfix installers are typically cluster aware. So in general you don'
t
need to apply the hotfix on each node. Apply the hotfix on the one that owns
the SQL instance, and the installer will apply the fix to the other nodes fo
r
you.
But read the documentation for your particular hotfix to make sure that is
indeed the case.
Linchi
"Spin" wrote:

> Gurus,
> Running two instances of SQL on a SQL Server 2000 cluster. Windows Server
> 2003 SP1 is the OS. Are there any special rules I must follow to execute
> the SQL hotfix on each node of the cluster? I am assuming I just need to
> apply the SQL hotfix to each cluster node and that's it. I am hoping it i
s
> that easy.
> --
> Spin
>
>|||Make sure Windows Task Schedular is running on both machines, the setup uses
it to apply the hotfix to the other node.
Tony Rogerson
SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a SQL
Server Consultant
http://sqlserverfaq.com - free video tutorials
"Spin" <Spin@.spin.com> wrote in message
news:4ifir0F3grg8U1@.individual.net...
> Gurus,
> Running two instances of SQL on a SQL Server 2000 cluster. Windows Server
> 2003 SP1 is the OS. Are there any special rules I must follow to execute
> the SQL hotfix on each node of the cluster? I am assuming I just need to
> apply the SQL hotfix to each cluster node and that's it. I am hoping it
> is that easy.
> --
> Spin
>

Applying SQL hotfixes to a SQL cluster

Gurus,
Running two instances of SQL on a SQL Server 2000 cluster. Windows Server
2003 SP1 is the OS. Are there any special rules I must follow to execute
the SQL hotfix on each node of the cluster? I am assuming I just need to
apply the SQL hotfix to each cluster node and that's it. I am hoping it is
that easy.
--
SpinRecent hotfix installers are typically cluster aware. So in general you don't
need to apply the hotfix on each node. Apply the hotfix on the one that owns
the SQL instance, and the installer will apply the fix to the other nodes for
you.
But read the documentation for your particular hotfix to make sure that is
indeed the case.
Linchi
"Spin" wrote:
> Gurus,
> Running two instances of SQL on a SQL Server 2000 cluster. Windows Server
> 2003 SP1 is the OS. Are there any special rules I must follow to execute
> the SQL hotfix on each node of the cluster? I am assuming I just need to
> apply the SQL hotfix to each cluster node and that's it. I am hoping it is
> that easy.
> --
> Spin
>
>|||Make sure Windows Task Schedular is running on both machines, the setup uses
it to apply the hotfix to the other node.
--
Tony Rogerson
SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a SQL
Server Consultant
http://sqlserverfaq.com - free video tutorials
"Spin" <Spin@.spin.com> wrote in message
news:4ifir0F3grg8U1@.individual.net...
> Gurus,
> Running two instances of SQL on a SQL Server 2000 cluster. Windows Server
> 2003 SP1 is the OS. Are there any special rules I must follow to execute
> the SQL hotfix on each node of the cluster? I am assuming I just need to
> apply the SQL hotfix to each cluster node and that's it. I am hoping it
> is that easy.
> --
> Spin
>|||Hi gurus,
I have a problem. For security purposes I work with two databases; I
use one as production DB (pdb) and the other (cdb) serves as a secure
copy of the production database; and I want to regularly update the
secure copy with the work that I do in the production databasse i.e.
update exsiting stored procedures, tables, views and diagrams or copy
new ones into the secure copy.
A program that at the end of each session in the production db asks if
I want to update the secure copy.
Anyone has an idea for a begginner?
Thanks
Yao
Tony Rogerson wrote:
> Make sure Windows Task Schedular is running on both machines, the setup uses
> it to apply the hotfix to the other node.
> --
> Tony Rogerson
> SQL Server MVP
> http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a SQL
> Server Consultant
> http://sqlserverfaq.com - free video tutorials
>
> "Spin" <Spin@.spin.com> wrote in message
> news:4ifir0F3grg8U1@.individual.net...
> > Gurus,
> >
> > Running two instances of SQL on a SQL Server 2000 cluster. Windows Server
> > 2003 SP1 is the OS. Are there any special rules I must follow to execute
> > the SQL hotfix on each node of the cluster? I am assuming I just need to
> > apply the SQL hotfix to each cluster node and that's it. I am hoping it
> > is that easy.
> >
> > --
> > Spin
> >
> >sql

app_data: a strange folder

hi,

I noticed that inVWD i can create my sql database and place it in a special folder called app_data, what is this new?
i think it is imposible because sql server is a serverdb and not a file based db like access!It's for Sql Express 2005, which is more or less a file DB. Also, the default membership provider model takes advantage of SQL Express 2005 (ASPNETDB.MDF file) automatically created under this directory.|||what are the main differences between "normal" and express edition, which is more performant?
does sql eXpress allow external connections (webs in other servers or clients)?|||It's still a server-based db, that's just it's data file. The server process will just spawn when you first try to access it.

Anything specific about SQL 2000 64 bit ?

Is there anything special needed to administer a 64 bit SQL Server ? We are
looking forward to deploying 64 bit on some servers and wanted to know if
there is anything I need to be aware of from an admin perspective,
installation,configuring, troubleshooting,etc..
There is a doucment for 64 bit sql server, you can read it before moving to
64 bit platform.
Thanks, Regards, Vincent
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23QRBWFKmFHA.2080@.TK2MSFTNGP10.phx.gbl...
> Is there anything special needed to administer a 64 bit SQL Server ? We
> are
> looking forward to deploying 64 bit on some servers and wanted to know if
> there is anything I need to be aware of from an admin perspective,
> installation,configuring, troubleshooting,etc..
>
|||There are two pretty important things you should be aware of relating to
administering a 64-bit instance of SQL 2000.
1) You cannot run DTS packages on the 64-bit instance. You have to have a
32-bit instance that will run the DTS packages against the 64-bit instance
databases.
2) The administrative tools (Enterprise Manager and Query Analyzer, for
example) have no 64-bit editions. Again, you have to run these tools on a
32-bit machine and connect to your 64-bit instance.
If you are planning on running 64-bit SQL 2000, I'm guessing you have an
Itanium machine (I think the 64-bit SQL 2000 edition is only for Itaniums).
SQL 2005 has both Itanium and x64 versions, with a more complete set of tools
and functionality. If you could work with 2005, you might be happier.
Bob Hodgman
"Hassan" wrote:

> Is there anything special needed to administer a 64 bit SQL Server ? We are
> looking forward to deploying 64 bit on some servers and wanted to know if
> there is anything I need to be aware of from an admin perspective,
> installation,configuring, troubleshooting,etc..
>
>

Anything specific about SQL 2000 64 bit ?

Is there anything special needed to administer a 64 bit SQL Server ? We are
looking forward to deploying 64 bit on some servers and wanted to know if
there is anything I need to be aware of from an admin perspective,
installation,configuring, troubleshooting,etc..There is a doucment for 64 bit sql server, you can read it before moving to
64 bit platform.
Thanks, Regards, Vincent
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23QRBWFKmFHA.2080@.TK2MSFTNGP10.phx.gbl...
> Is there anything special needed to administer a 64 bit SQL Server ? We
> are
> looking forward to deploying 64 bit on some servers and wanted to know if
> there is anything I need to be aware of from an admin perspective,
> installation,configuring, troubleshooting,etc..
>|||There are two pretty important things you should be aware of relating to
administering a 64-bit instance of SQL 2000.
1) You cannot run DTS packages on the 64-bit instance. You have to have a
32-bit instance that will run the DTS packages against the 64-bit instance
databases.
2) The administrative tools (Enterprise Manager and Query Analyzer, for
example) have no 64-bit editions. Again, you have to run these tools on a
32-bit machine and connect to your 64-bit instance.
If you are planning on running 64-bit SQL 2000, I'm guessing you have an
Itanium machine (I think the 64-bit SQL 2000 edition is only for Itaniums).
SQL 2005 has both Itanium and x64 versions, with a more complete set of tool
s
and functionality. If you could work with 2005, you might be happier.
Bob Hodgman
"Hassan" wrote:

> Is there anything special needed to administer a 64 bit SQL Server ? We ar
e
> looking forward to deploying 64 bit on some servers and wanted to know if
> there is anything I need to be aware of from an admin perspective,
> installation,configuring, troubleshooting,etc..
>
>

Anything specific about SQL 2000 64 bit ?

Is there anything special needed to administer a 64 bit SQL Server ? We are
looking forward to deploying 64 bit on some servers and wanted to know if
there is anything I need to be aware of from an admin perspective,
installation,configuring, troubleshooting,etc..There is a doucment for 64 bit sql server, you can read it before moving to
64 bit platform.
Thanks, Regards, Vincent
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23QRBWFKmFHA.2080@.TK2MSFTNGP10.phx.gbl...
> Is there anything special needed to administer a 64 bit SQL Server ? We
> are
> looking forward to deploying 64 bit on some servers and wanted to know if
> there is anything I need to be aware of from an admin perspective,
> installation,configuring, troubleshooting,etc..
>|||There are two pretty important things you should be aware of relating to
administering a 64-bit instance of SQL 2000.
1) You cannot run DTS packages on the 64-bit instance. You have to have a
32-bit instance that will run the DTS packages against the 64-bit instance
databases.
2) The administrative tools (Enterprise Manager and Query Analyzer, for
example) have no 64-bit editions. Again, you have to run these tools on a
32-bit machine and connect to your 64-bit instance.
If you are planning on running 64-bit SQL 2000, I'm guessing you have an
Itanium machine (I think the 64-bit SQL 2000 edition is only for Itaniums).
SQL 2005 has both Itanium and x64 versions, with a more complete set of tools
and functionality. If you could work with 2005, you might be happier.
--
Bob Hodgman
"Hassan" wrote:
> Is there anything special needed to administer a 64 bit SQL Server ? We are
> looking forward to deploying 64 bit on some servers and wanted to know if
> there is anything I need to be aware of from an admin perspective,
> installation,configuring, troubleshooting,etc..
>
>