a database restore technique question...

background sql2k on nt4.
one of the disk stripe went bad during the weekend and our network admin
rebuilt the box and reinstalled sql2k w/ sp2 but he didnt' check what was
installed origionally. his restore is like this:
1. origional sql excutables and database files are located at d:\mssql\, he
renamed it to d:\mssql_x\
2. he reinstalled sql2k and system databases to d:\mssql\, after that he was
able to start the sql service again.
3. he then renamed d:\mssql\ to d:\mssql_y\, and renamed d:\mssql_x\ back to
d:\mssql\
but the sql service wouldn't start. he said that tenique worked a couple of
times at other occasions.
my questions:
1. what might go wrong this time?
2. what's wrong with this technique, there is no backup or restore involved.
almost sounds too easy to be true.
thank you.
What he should have done was copy over the old database files to the new
folder. It appears that perhaps the old executables got corrupted.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Steve Lin" <lins@.nospam.portptld.com> wrote in message
news:%234$J1ViJEHA.1392@.TK2MSFTNGP09.phx.gbl...
background sql2k on nt4.
one of the disk stripe went bad during the weekend and our network admin
rebuilt the box and reinstalled sql2k w/ sp2 but he didnt' check what was
installed origionally. his restore is like this:
1. origional sql excutables and database files are located at d:\mssql\, he
renamed it to d:\mssql_x\
2. he reinstalled sql2k and system databases to d:\mssql\, after that he was
able to start the sql service again.
3. he then renamed d:\mssql\ to d:\mssql_y\, and renamed d:\mssql_x\ back to
d:\mssql\
but the sql service wouldn't start. he said that tenique worked a couple of
times at other occasions.
my questions:
1. what might go wrong this time?
2. what's wrong with this technique, there is no backup or restore involved.
almost sounds too easy to be true.
thank you.
|||"...copy over the old database files to the new..."
does that include system files such as master, msdb and so on?
if that's the case, wouldn't you need to 'attach' all the databases?
his tenique simple renamed the original directory to the new directory.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:#cXyfpiJEHA.2412@.TK2MSFTNGP12.phx.gbl...
> What he should have done was copy over the old database files to the new
> folder. It appears that perhaps the old executables got corrupted.
> --
> Tom
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com/sql
>
> "Steve Lin" <lins@.nospam.portptld.com> wrote in message
> news:%234$J1ViJEHA.1392@.TK2MSFTNGP09.phx.gbl...
> background sql2k on nt4.
> one of the disk stripe went bad during the weekend and our network admin
> rebuilt the box and reinstalled sql2k w/ sp2 but he didnt' check what was
> installed origionally. his restore is like this:
> 1. origional sql excutables and database files are located at d:\mssql\,
he
> renamed it to d:\mssql_x\
> 2. he reinstalled sql2k and system databases to d:\mssql\, after that he
was
> able to start the sql service again.
> 3. he then renamed d:\mssql\ to d:\mssql_y\, and renamed d:\mssql_x\ back
to
> d:\mssql\
> but the sql service wouldn't start. he said that tenique worked a couple
of
> times at other occasions.
> my questions:
> 1. what might go wrong this time?
> 2. what's wrong with this technique, there is no backup or restore
involved.
> almost sounds too easy to be true.
> thank you.
>
|||For everything to be in synch, then yes, you would have to move all
databases - assuming none were corrupted. Simply renaming the directory
would make it point to all of the old stuff - including the executables. If
the original SQL Server had been shut down properly, you wouldn't need to
attach anything.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Steve Lin" <lins@.nospam.portptld.com> wrote in message
news:OsUOquiJEHA.228@.TK2MSFTNGP10.phx.gbl...
"...copy over the old database files to the new..."
does that include system files such as master, msdb and so on?
if that's the case, wouldn't you need to 'attach' all the databases?
his tenique simple renamed the original directory to the new directory.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:#cXyfpiJEHA.2412@.TK2MSFTNGP12.phx.gbl...
> What he should have done was copy over the old database files to the new
> folder. It appears that perhaps the old executables got corrupted.
> --
> Tom
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com/sql
>
> "Steve Lin" <lins@.nospam.portptld.com> wrote in message
> news:%234$J1ViJEHA.1392@.TK2MSFTNGP09.phx.gbl...
> background sql2k on nt4.
> one of the disk stripe went bad during the weekend and our network admin
> rebuilt the box and reinstalled sql2k w/ sp2 but he didnt' check what was
> installed origionally. his restore is like this:
> 1. origional sql excutables and database files are located at d:\mssql\,
he
> renamed it to d:\mssql_x\
> 2. he reinstalled sql2k and system databases to d:\mssql\, after that he
was
> able to start the sql service again.
> 3. he then renamed d:\mssql\ to d:\mssql_y\, and renamed d:\mssql_x\ back
to
> d:\mssql\
> but the sql service wouldn't start. he said that tenique worked a couple
of
> times at other occasions.
> my questions:
> 1. what might go wrong this time?
> 2. what's wrong with this technique, there is no backup or restore
involved.
> almost sounds too easy to be true.
> thank you.
>

a database restore technique question...

background sql2k on nt4.
one of the disk stripe went bad during the weekend and our network admin
rebuilt the box and reinstalled sql2k w/ sp2 but he didnt' check what was
installed origionally. his restore is like this:
1. origional sql excutables and database files are located at d:\mssql\, he
renamed it to d:\mssql_x\
2. he reinstalled sql2k and system databases to d:\mssql\, after that he was
able to start the sql service again.
3. he then renamed d:\mssql\ to d:\mssql_y\, and renamed d:\mssql_x\ back to
d:\mssql\
but the sql service wouldn't start. he said that tenique worked a couple of
times at other occasions.
my questions:
1. what might go wrong this time?
2. what's wrong with this technique, there is no backup or restore involved.
almost sounds too easy to be true.
thank you.What he should have done was copy over the old database files to the new
folder. It appears that perhaps the old executables got corrupted.
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Steve Lin" <lins@.nospam.portptld.com> wrote in message
news:%234$J1ViJEHA.1392@.TK2MSFTNGP09.phx.gbl...
background sql2k on nt4.
one of the disk stripe went bad during the weekend and our network admin
rebuilt the box and reinstalled sql2k w/ sp2 but he didnt' check what was
installed origionally. his restore is like this:
1. origional sql excutables and database files are located at d:\mssql\, he
renamed it to d:\mssql_x\
2. he reinstalled sql2k and system databases to d:\mssql\, after that he was
able to start the sql service again.
3. he then renamed d:\mssql\ to d:\mssql_y\, and renamed d:\mssql_x\ back to
d:\mssql\
but the sql service wouldn't start. he said that tenique worked a couple of
times at other occasions.
my questions:
1. what might go wrong this time?
2. what's wrong with this technique, there is no backup or restore involved.
almost sounds too easy to be true.
thank you.|||"...copy over the old database files to the new..."
does that include system files such as master, msdb and so on?
if that's the case, wouldn't you need to 'attach' all the databases?
his tenique simple renamed the original directory to the new directory.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:#cXyfpiJEHA.2412@.TK2MSFTNGP12.phx.gbl...
> What he should have done was copy over the old database files to the new
> folder. It appears that perhaps the old executables got corrupted.
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com/sql
>
> "Steve Lin" <lins@.nospam.portptld.com> wrote in message
> news:%234$J1ViJEHA.1392@.TK2MSFTNGP09.phx.gbl...
> background sql2k on nt4.
> one of the disk stripe went bad during the weekend and our network admin
> rebuilt the box and reinstalled sql2k w/ sp2 but he didnt' check what was
> installed origionally. his restore is like this:
> 1. origional sql excutables and database files are located at d:\mssql\,
he
> renamed it to d:\mssql_x\
> 2. he reinstalled sql2k and system databases to d:\mssql\, after that he
was
> able to start the sql service again.
> 3. he then renamed d:\mssql\ to d:\mssql_y\, and renamed d:\mssql_x\ back
to
> d:\mssql\
> but the sql service wouldn't start. he said that tenique worked a couple
of
> times at other occasions.
> my questions:
> 1. what might go wrong this time?
> 2. what's wrong with this technique, there is no backup or restore
involved.
> almost sounds too easy to be true.
> thank you.
>|||For everything to be in synch, then yes, you would have to move all
databases - assuming none were corrupted. Simply renaming the directory
would make it point to all of the old stuff - including the executables. If
the original SQL Server had been shut down properly, you wouldn't need to
attach anything.
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Steve Lin" <lins@.nospam.portptld.com> wrote in message
news:OsUOquiJEHA.228@.TK2MSFTNGP10.phx.gbl...
"...copy over the old database files to the new..."
does that include system files such as master, msdb and so on?
if that's the case, wouldn't you need to 'attach' all the databases?
his tenique simple renamed the original directory to the new directory.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:#cXyfpiJEHA.2412@.TK2MSFTNGP12.phx.gbl...
> What he should have done was copy over the old database files to the new
> folder. It appears that perhaps the old executables got corrupted.
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com/sql
>
> "Steve Lin" <lins@.nospam.portptld.com> wrote in message
> news:%234$J1ViJEHA.1392@.TK2MSFTNGP09.phx.gbl...
> background sql2k on nt4.
> one of the disk stripe went bad during the weekend and our network admin
> rebuilt the box and reinstalled sql2k w/ sp2 but he didnt' check what was
> installed origionally. his restore is like this:
> 1. origional sql excutables and database files are located at d:\mssql\,
he
> renamed it to d:\mssql_x\
> 2. he reinstalled sql2k and system databases to d:\mssql\, after that he
was
> able to start the sql service again.
> 3. he then renamed d:\mssql\ to d:\mssql_y\, and renamed d:\mssql_x\ back
to
> d:\mssql\
> but the sql service wouldn't start. he said that tenique worked a couple
of
> times at other occasions.
> my questions:
> 1. what might go wrong this time?
> 2. what's wrong with this technique, there is no backup or restore
involved.
> almost sounds too easy to be true.
> thank you.
>

a database restore technique question...

background sql2k on nt4.
one of the disk stripe went bad during the weekend and our network admin
rebuilt the box and reinstalled sql2k w/ sp2 but he didnt' check what was
installed origionally. his restore is like this:
1. origional sql excutables and database files are located at d:\mssql\, he
renamed it to d:\mssql_x\
2. he reinstalled sql2k and system databases to d:\mssql\, after that he was
able to start the sql service again.
3. he then renamed d:\mssql\ to d:\mssql_y\, and renamed d:\mssql_x\ back to
d:\mssql\
but the sql service wouldn't start. he said that tenique worked a couple of
times at other occasions.
my questions:
1. what might go wrong this time?
2. what's wrong with this technique, there is no backup or restore involved.
almost sounds too easy to be true.
thank you.What he should have done was copy over the old database files to the new
folder. It appears that perhaps the old executables got corrupted.
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Steve Lin" <lins@.nospam.portptld.com> wrote in message
news:%234$J1ViJEHA.1392@.TK2MSFTNGP09.phx.gbl...
background sql2k on nt4.
one of the disk stripe went bad during the weekend and our network admin
rebuilt the box and reinstalled sql2k w/ sp2 but he didnt' check what was
installed origionally. his restore is like this:
1. origional sql excutables and database files are located at d:\mssql\, he
renamed it to d:\mssql_x\
2. he reinstalled sql2k and system databases to d:\mssql\, after that he was
able to start the sql service again.
3. he then renamed d:\mssql\ to d:\mssql_y\, and renamed d:\mssql_x\ back to
d:\mssql\
but the sql service wouldn't start. he said that tenique worked a couple of
times at other occasions.
my questions:
1. what might go wrong this time?
2. what's wrong with this technique, there is no backup or restore involved.
almost sounds too easy to be true.
thank you.|||"...copy over the old database files to the new..."
does that include system files such as master, msdb and so on?
if that's the case, wouldn't you need to 'attach' all the databases?
his tenique simple renamed the original directory to the new directory.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:#cXyfpiJEHA.2412@.TK2MSFTNGP12.phx.gbl...
> What he should have done was copy over the old database files to the new
> folder. It appears that perhaps the old executables got corrupted.
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com/sql
>
> "Steve Lin" <lins@.nospam.portptld.com> wrote in message
> news:%234$J1ViJEHA.1392@.TK2MSFTNGP09.phx.gbl...
> background sql2k on nt4.
> one of the disk stripe went bad during the weekend and our network admin
> rebuilt the box and reinstalled sql2k w/ sp2 but he didnt' check what was
> installed origionally. his restore is like this:
> 1. origional sql excutables and database files are located at d:\mssql\,
he
> renamed it to d:\mssql_x\
> 2. he reinstalled sql2k and system databases to d:\mssql\, after that he
was
> able to start the sql service again.
> 3. he then renamed d:\mssql\ to d:\mssql_y\, and renamed d:\mssql_x\ back
to
> d:\mssql\
> but the sql service wouldn't start. he said that tenique worked a couple
of
> times at other occasions.
> my questions:
> 1. what might go wrong this time?
> 2. what's wrong with this technique, there is no backup or restore
involved.
> almost sounds too easy to be true.
> thank you.
>|||For everything to be in synch, then yes, you would have to move all
databases - assuming none were corrupted. Simply renaming the directory
would make it point to all of the old stuff - including the executables. If
the original SQL Server had been shut down properly, you wouldn't need to
attach anything.
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Steve Lin" <lins@.nospam.portptld.com> wrote in message
news:OsUOquiJEHA.228@.TK2MSFTNGP10.phx.gbl...
"...copy over the old database files to the new..."
does that include system files such as master, msdb and so on?
if that's the case, wouldn't you need to 'attach' all the databases?
his tenique simple renamed the original directory to the new directory.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:#cXyfpiJEHA.2412@.TK2MSFTNGP12.phx.gbl...
> What he should have done was copy over the old database files to the new
> folder. It appears that perhaps the old executables got corrupted.
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com/sql
>
> "Steve Lin" <lins@.nospam.portptld.com> wrote in message
> news:%234$J1ViJEHA.1392@.TK2MSFTNGP09.phx.gbl...
> background sql2k on nt4.
> one of the disk stripe went bad during the weekend and our network admin
> rebuilt the box and reinstalled sql2k w/ sp2 but he didnt' check what was
> installed origionally. his restore is like this:
> 1. origional sql excutables and database files are located at d:\mssql\,
he
> renamed it to d:\mssql_x\
> 2. he reinstalled sql2k and system databases to d:\mssql\, after that he
was
> able to start the sql service again.
> 3. he then renamed d:\mssql\ to d:\mssql_y\, and renamed d:\mssql_x\ back
to
> d:\mssql\
> but the sql service wouldn't start. he said that tenique worked a couple
of
> times at other occasions.
> my questions:
> 1. what might go wrong this time?
> 2. what's wrong with this technique, there is no backup or restore
involved.
> almost sounds too easy to be true.
> thank you.
>

7.0 and 2000 .BAK incompatibility?

i just got a disk w/ a .bak file on it. when i tried to restore it on
my 2000 sql server instance it said the format was invalid. so, would i
get this error if the .bak version was created using version 7.0?
thanks,
arthur
Arthur,
7 --> 2000 shouldn't be a problem. Try using the HEADERONLY and
FILELISTONLY arguments of the RESTORE statement for the backup.
HTH
Jerry
"arthur" <alangham@.gmail.com> wrote in message
news:1129679111.225814.302070@.g14g2000cwa.googlegr oups.com...
>i just got a disk w/ a .bak file on it. when i tried to restore it on
> my 2000 sql server instance it said the format was invalid. so, would i
> get this error if the .bak version was created using version 7.0?
> thanks,
> arthur
>
|||the specific error i'm getting is RESTORE HEADERONLY is terminating
abnormally. i have no idea what the filelists are in the file. i'm
going to get w/ the peeps that made this file and see what's up. thanks.
|||Hi,
Then try using RESTORE FILELISTONLY OR use Enterprise manager -- All
tasks -- Restore
Filelistonly usage:-
Restore filelistonly from DISK='C:\Backup\backupfile.bak'
Thanks
Hari
SQL Server MVP
"arthur" <alangham@.gmail.com> wrote in message
news:1129680445.762037.102890@.g47g2000cwa.googlegr oups.com...
> the specific error i'm getting is RESTORE HEADERONLY is terminating
> abnormally. i have no idea what the filelists are in the file. i'm
> going to get w/ the peeps that made this file and see what's up. thanks.
>
|||Are you certain this is indeed a SQL Server backup file? It could just have been created with a beta
of SQL Server 7.0, but I think that SQL Server 2000 would give a more descriptive error message.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"arthur" <alangham@.gmail.com> wrote in message
news:1129680445.762037.102890@.g47g2000cwa.googlegr oups.com...
> the specific error i'm getting is RESTORE HEADERONLY is terminating
> abnormally. i have no idea what the filelists are in the file. i'm
> going to get w/ the peeps that made this file and see what's up. thanks.
>

7.0 and 2000 .BAK incompatibility?

i just got a disk w/ a .bak file on it. when i tried to restore it on
my 2000 sql server instance it said the format was invalid. so, would i
get this error if the .bak version was created using version 7.0?
thanks,
arthurArthur,
7 --> 2000 shouldn't be a problem. Try using the HEADERONLY and
FILELISTONLY arguments of the RESTORE statement for the backup.
HTH
Jerry
"arthur" <alangham@.gmail.com> wrote in message
news:1129679111.225814.302070@.g14g2000cwa.googlegroups.com...
>i just got a disk w/ a .bak file on it. when i tried to restore it on
> my 2000 sql server instance it said the format was invalid. so, would i
> get this error if the .bak version was created using version 7.0?
> thanks,
> arthur
>|||the specific error i'm getting is RESTORE HEADERONLY is terminating
abnormally. i have no idea what the filelists are in the file. i'm
going to get w/ the peeps that made this file and see what's up. thanks.|||Hi,
Then try using RESTORE FILELISTONLY OR use Enterprise manager -- All
tasks -- Restore
Filelistonly usage:-
Restore filelistonly from DISK='C:\Backup\backupfile.bak'
Thanks
Hari
SQL Server MVP
"arthur" <alangham@.gmail.com> wrote in message
news:1129680445.762037.102890@.g47g2000cwa.googlegroups.com...
> the specific error i'm getting is RESTORE HEADERONLY is terminating
> abnormally. i have no idea what the filelists are in the file. i'm
> going to get w/ the peeps that made this file and see what's up. thanks.
>|||Are you certain this is indeed a SQL Server backup file? It could just have
been created with a beta
of SQL Server 7.0, but I think that SQL Server 2000 would give a more descri
ptive error message.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"arthur" <alangham@.gmail.com> wrote in message
news:1129680445.762037.102890@.g47g2000cwa.googlegroups.com...
> the specific error i'm getting is RESTORE HEADERONLY is terminating
> abnormally. i have no idea what the filelists are in the file. i'm
> going to get w/ the peeps that made this file and see what's up. thanks.
>

7.0 and 2000 .BAK incompatibility?

i just got a disk w/ a .bak file on it. when i tried to restore it on
my 2000 sql server instance it said the format was invalid. so, would i
get this error if the .bak version was created using version 7.0?
thanks,
arthurArthur,
7 --> 2000 shouldn't be a problem. Try using the HEADERONLY and
FILELISTONLY arguments of the RESTORE statement for the backup.
HTH
Jerry
"arthur" <alangham@.gmail.com> wrote in message
news:1129679111.225814.302070@.g14g2000cwa.googlegroups.com...
>i just got a disk w/ a .bak file on it. when i tried to restore it on
> my 2000 sql server instance it said the format was invalid. so, would i
> get this error if the .bak version was created using version 7.0?
> thanks,
> arthur
>|||the specific error i'm getting is RESTORE HEADERONLY is terminating
abnormally. i have no idea what the filelists are in the file. i'm
going to get w/ the peeps that made this file and see what's up. thanks.|||Hi,
Then try using RESTORE FILELISTONLY OR use Enterprise manager -- All
tasks -- Restore
Filelistonly usage:-
Restore filelistonly from DISK='C:\Backup\backupfile.bak'
Thanks
Hari
SQL Server MVP
"arthur" <alangham@.gmail.com> wrote in message
news:1129680445.762037.102890@.g47g2000cwa.googlegroups.com...
> the specific error i'm getting is RESTORE HEADERONLY is terminating
> abnormally. i have no idea what the filelists are in the file. i'm
> going to get w/ the peeps that made this file and see what's up. thanks.
>|||Are you certain this is indeed a SQL Server backup file? It could just have been created with a beta
of SQL Server 7.0, but I think that SQL Server 2000 would give a more descriptive error message.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"arthur" <alangham@.gmail.com> wrote in message
news:1129680445.762037.102890@.g47g2000cwa.googlegroups.com...
> the specific error i'm getting is RESTORE HEADERONLY is terminating
> abnormally. i have no idea what the filelists are in the file. i'm
> going to get w/ the peeps that made this file and see what's up. thanks.
>

64-bit Windows / 64-bit SQL - External Disk Array (cluster)

oops, post should have gone to this forum ....
Hi,
I read in the SQL 2005 Exam guides for clustering that (p.283 - 70-443),
that if building a cluster on 64-bit Windows then must use Fibre drives?
I'm trying to verying this with help of Google/MSDN, and not found
confirmation anywhere.
Is this the case that running a cluster on 64-bit editions places these
restrictions on hardware?
If we want to go 64-bit, are we basically forced to accept a fibre-based SAN
as I/O system?
Thank you.
Craig
Windows 2003 64-bit does not require fibre drives. You can use anything
internal for the nodes. The shared disk can be Parallel Attached SCSI
(though I would not), iSCSI or SAN based.
Now Windows 2008 will not support PAS, but it will support SAS, SAN, or
iSCSI.
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"craig_amtdatatechnologies@.discussions.mi"
<craigamtdatatechnologiesdiscussionsmi@.discussions .microsoft.com> wrote in
message news:B1B0C4B4-B45D-4217-AC25-3A2D7A4B362B@.microsoft.com...
> oops, post should have gone to this forum ....
> Hi,
> I read in the SQL 2005 Exam guides for clustering that (p.283 - 70-443),
> that if building a cluster on 64-bit Windows then must use Fibre drives?
> I'm trying to verying this with help of Google/MSDN, and not found
> confirmation anywhere.
> Is this the case that running a cluster on 64-bit editions places these
> restrictions on hardware?
> If we want to go 64-bit, are we basically forced to accept a fibre-based
> SAN
> as I/O system?
>
> Thank you.
> Craig
|||Thanks for reply re: this
"Rodney R. Fournier [MVP]" wrote:

> Windows 2003 64-bit does not require fibre drives. You can use anything
> internal for the nodes. The shared disk can be Parallel Attached SCSI
> (though I would not), iSCSI or SAN based.
>
> Now Windows 2008 will not support PAS, but it will support SAS, SAN, or
> iSCSI.
> Cheers,
> Rodney R. Fournier
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering Website
> http://msmvps.com/clustering - Blog
> http://www.clusterhelp.com - Cluster Training
> ClusterHelp.com is a Microsoft Certified Gold Partner
>
> "craig_amtdatatechnologies@.discussions.mi"
> <craigamtdatatechnologiesdiscussionsmi@.discussions .microsoft.com> wrote in
> message news:B1B0C4B4-B45D-4217-AC25-3A2D7A4B362B@.microsoft.com...
>
>

64 bit database

Does INTEGER type take 8 bytes (64 bits) or 4 bytes (32 bits) of the
disk space?
MHSmallint = 2 bytes
Integer = 4 bytes
Bigint = 8 bytes
--
Ekrem Önsoy
"Marius Horak" <nobody@.eu.con> wrote in message
news:OBgwZ0e9HHA.3916@.TK2MSFTNGP02.phx.gbl...
> Does INTEGER type take 8 bytes (64 bits) or 4 bytes (32 bits) of the
> disk space?
> MH|||... and it is the same for 32 and 64 bit. In fact, the database format is exactly the same across
32/64 bit.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Ekrem Önsoy" <ekrem@.btegitim.com> wrote in message
news:095B7B19-6006-4BFD-A0A3-D0576725BA66@.microsoft.com...
> Smallint = 2 bytes
> Integer = 4 bytes
> Bigint = 8 bytes
> --
> Ekrem Önsoy
>
> "Marius Horak" <nobody@.eu.con> wrote in message news:OBgwZ0e9HHA.3916@.TK2MSFTNGP02.phx.gbl...
>> Does INTEGER type take 8 bytes (64 bits) or 4 bytes (32 bits) of the
>> disk space?
>> MH
>

60 days of backups

I have had a request to run backups of a database to disk, and retain the
backups until they are 60 days old. I've got the job set up, but it either
appends or overwrites the previous job. Does anyone know of a way to do
this?
TIA,
KSee
http://www.nigelrivett.net/BackupAllDatabases.html
You could use the sqlmaint exe but I think backups are too
important.
>--Original Message--
>I have had a request to run backups of a database to
disk, and retain the
>backups until they are 60 days old. I've got the job set
up, but it either
>appends or overwrites the previous job. Does anyone know
of a way to do
>this?
>TIA,
>K
>
>.
>|||Use the maintenance function in SLQ and enable the SQL server agent service
--
J
www.urbanvoyeur.com
"msnews.microsoft.com" <kb@.blah.com> wrote in message
news:uet5nU7iDHA.1696@.TK2MSFTNGP12.phx.gbl...
> I have had a request to run backups of a database to disk, and retain the
> backups until they are 60 days old. I've got the job set up, but it
either
> appends or overwrites the previous job. Does anyone know of a way to do
> this?
> TIA,
> K
>|||Thanks for the help...I setup a maintenance plan and have my fingers crossed
that this will work!
K
"UrbanVoyeur" <nospam@.nospam.com> wrote in message
news:ey9Bi4AjDHA.1676@.TK2MSFTNGP09.phx.gbl...
> Use the maintenance function in SLQ and enable the SQL server agent
service
> --
> J
> www.urbanvoyeur.com
>
> "msnews.microsoft.com" <kb@.blah.com> wrote in message
> news:uet5nU7iDHA.1696@.TK2MSFTNGP12.phx.gbl...
> > I have had a request to run backups of a database to disk, and retain
the
> > backups until they are 60 days old. I've got the job set up, but it
> either
> > appends or overwrites the previous job. Does anyone know of a way to do
> > this?
> >
> > TIA,
> > K
> >
> >
>