Moving a SQL Server 2K cluster to new subet

Hi, I need to move a MSCS cluster running SQL Server 2000 Enterprise
Edition to a new subnet. Can anyone point me to or list what items I need to
be aware of in order for me to move my cluster?
Thanks
It's really not that bad, see http://support.microsoft.com/?id=244980 for
the clicks.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
"Jose Lopez-Alvarez" <jose.lopez-alvarez@.ftb.ca.gov> wrote in message
news:%23dlhyChkEHA.536@.TK2MSFTNGP11.phx.gbl...
> Hi, I need to move a MSCS cluster running SQL Server 2000 Enterprise
> Edition to a new subnet. Can anyone point me to or list what items I need
> to
> be aware of in order for me to move my cluster?
>
> Thanks
>
>
sql

move/copy database items from SS 2005 Express to SS 2005 Standard?

Can anyone refer me to good 'recipes' or sources of information on this
topic'
I have Visual Studio Tools for Office, which installs SS 2005 Express
locally to my XP box, and I want to develop in SS 2005, then copy the
tables or queries or reports etc. to a SS 2005 Standard server.
Thank you, TomYou can:
1. Using SSMS, script out the code to re-create the table, views, queries,
etc.
2. Using SSIS, Transfer the entire database, schema and/or data
3. Pull your script files from source control, thereby making sure that
nothing is moved to the production server except items that 'should' be
moved to production. (You are using source control, aren't you?)
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"tlyczko" <tlyczko@.gmail.com> wrote in message
news:1157562224.879951.99990@.e3g2000cwe.googlegroups.com...
> Can anyone refer me to good 'recipes' or sources of information on this
> topic'
> I have Visual Studio Tools for Office, which installs SS 2005 Express
> locally to my XP box, and I want to develop in SS 2005, then copy the
> tables or queries or reports etc. to a SS 2005 Standard server.
> Thank you, Tom
>|||I don't know anything yet about source control...do you mean Visual
SourceSafe'
I tried looking around a few months ago for decent documentation,
how-to, etc. about VSS 2005, and I didn't find anything, it was not
terribly intuitive either...
I don't always need to transfer the entire database either, I might
only have to transfer a query, for example.
Or I might have to refresh the tables in my dev workstation from the
main server...
Thank you,
Tom
Arnie Rowland wrote:[vbcol=seagreen]
> You can:
> 1. Using SSMS, script out the code to re-create the table, views, queries,
> etc.
> 2. Using SSIS, Transfer the entire database, schema and/or data
> 3. Pull your script files from source control, thereby making sure that
> nothing is moved to the production server except items that 'should' be
> moved to production. (You are using source control, aren't you?)
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "tlyczko" <tlyczko@.gmail.com> wrote in message
> news:1157562224.879951.99990@.e3g2000cwe.googlegroups.com...|||Visual SourceSafe is but one of many source control products, albeit one
that is included with Visual Studio.
You might find part 4 of this tutorial useful for an introductory view of
Sourcesafe.
http://msdn2.microsoft.com/en-us/library/ms167593.aspx
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"tlyczko" <tlyczko@.gmail.com> wrote in message
news:1157567635.523378.239270@.p79g2000cwp.googlegroups.com...
>I don't know anything yet about source control...do you mean Visual
> SourceSafe'
> I tried looking around a few months ago for decent documentation,
> how-to, etc. about VSS 2005, and I didn't find anything, it was not
> terribly intuitive either...
> I don't always need to transfer the entire database either, I might
> only have to transfer a query, for example.
> Or I might have to refresh the tables in my dev workstation from the
> main server...
> Thank you,
> Tom
> Arnie Rowland wrote:
>|||Visual SourceSafe didn't come with our Visual Studio...
Thank you for sending the link, I think I remember that Perforce makes
a single-user version that I could use...I'll check their website.
Thank you, Tom

> Most good judgment comes from experience.
> Most experience comes from bad judgment.
Agreed.
Thank you, Tom

move/copy database items from SS 2005 Express to SS 2005 Standard?

Can anyone refer me to good 'recipes' or sources of information on this
topic'
I have Visual Studio Tools for Office, which installs SS 2005 Express
locally to my XP box, and I want to develop in SS 2005, then copy the
tables or queries or reports etc. to a SS 2005 Standard server.
Thank you, TomYou can:
1. Using SSMS, script out the code to re-create the table, views, queries,
etc.
2. Using SSIS, Transfer the entire database, schema and/or data
3. Pull your script files from source control, thereby making sure that
nothing is moved to the production server except items that 'should' be
moved to production. (You are using source control, aren't you?)
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"tlyczko" <tlyczko@.gmail.com> wrote in message
news:1157562224.879951.99990@.e3g2000cwe.googlegroups.com...
> Can anyone refer me to good 'recipes' or sources of information on this
> topic'
> I have Visual Studio Tools for Office, which installs SS 2005 Express
> locally to my XP box, and I want to develop in SS 2005, then copy the
> tables or queries or reports etc. to a SS 2005 Standard server.
> Thank you, Tom
>|||I don't know anything yet about source control...do you mean Visual
SourceSafe'
I tried looking around a few months ago for decent documentation,
how-to, etc. about VSS 2005, and I didn't find anything, it was not
terribly intuitive either...
I don't always need to transfer the entire database either, I might
only have to transfer a query, for example.
Or I might have to refresh the tables in my dev workstation from the
main server...
Thank you,
Tom
Arnie Rowland wrote:
> You can:
> 1. Using SSMS, script out the code to re-create the table, views, queries,
> etc.
> 2. Using SSIS, Transfer the entire database, schema and/or data
> 3. Pull your script files from source control, thereby making sure that
> nothing is moved to the production server except items that 'should' be
> moved to production. (You are using source control, aren't you?)
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "tlyczko" <tlyczko@.gmail.com> wrote in message
> news:1157562224.879951.99990@.e3g2000cwe.googlegroups.com...
> > Can anyone refer me to good 'recipes' or sources of information on this
> > topic'
> >
> > I have Visual Studio Tools for Office, which installs SS 2005 Express
> > locally to my XP box, and I want to develop in SS 2005, then copy the
> > tables or queries or reports etc. to a SS 2005 Standard server.
> >
> > Thank you, Tom
> >|||Visual SourceSafe is but one of many source control products, albeit one
that is included with Visual Studio.
You might find part 4 of this tutorial useful for an introductory view of
Sourcesafe.
http://msdn2.microsoft.com/en-us/library/ms167593.aspx
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"tlyczko" <tlyczko@.gmail.com> wrote in message
news:1157567635.523378.239270@.p79g2000cwp.googlegroups.com...
>I don't know anything yet about source control...do you mean Visual
> SourceSafe'
> I tried looking around a few months ago for decent documentation,
> how-to, etc. about VSS 2005, and I didn't find anything, it was not
> terribly intuitive either...
> I don't always need to transfer the entire database either, I might
> only have to transfer a query, for example.
> Or I might have to refresh the tables in my dev workstation from the
> main server...
> Thank you,
> Tom
> Arnie Rowland wrote:
>> You can:
>> 1. Using SSMS, script out the code to re-create the table, views,
>> queries,
>> etc.
>> 2. Using SSIS, Transfer the entire database, schema and/or data
>> 3. Pull your script files from source control, thereby making sure that
>> nothing is moved to the production server except items that 'should' be
>> moved to production. (You are using source control, aren't you?)
>> --
>> Arnie Rowland, Ph.D.
>> Westwood Consulting, Inc
>> Most good judgment comes from experience.
>> Most experience comes from bad judgment.
>> - Anonymous
>>
>> "tlyczko" <tlyczko@.gmail.com> wrote in message
>> news:1157562224.879951.99990@.e3g2000cwe.googlegroups.com...
>> > Can anyone refer me to good 'recipes' or sources of information on this
>> > topic'
>> >
>> > I have Visual Studio Tools for Office, which installs SS 2005 Express
>> > locally to my XP box, and I want to develop in SS 2005, then copy the
>> > tables or queries or reports etc. to a SS 2005 Standard server.
>> >
>> > Thank you, Tom
>> >
>|||Visual SourceSafe didn't come with our Visual Studio...
Thank you for sending the link, I think I remember that Perforce makes
a single-user version that I could use...I'll check their website.
Thank you, Tom
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
Agreed.
Thank you, Tom