Dual-boot with SQL 2000

A client has a program that uses a SQL database. They already have a Windows
2003 + SQL 2000 SP3a server they had planned to use with this app, then
discovered the vendor only will not support Windows 2003 + SQL 2000 SP3a
until the end of the year.
Our thought is to install Windows 2000 + SQL 2000 as a dual-boot with the
existing Windows 2003 + SQL 2000 installation. Set the SQL database and log
folders to the same folders in both installations, and when the vendor
certifies Windows 2003, boot into 2003 and immediately resume operations
with minimal downtime.
Is this workable? Or do we need to keep the two SQL installations completely
separate and do a backup from Win2000/SQL2000 and then restore to
Win2003/SQL2000?
--
Jeff Vandervoort
JRVsystems
http://jrvsystems.comAssuming that the folder for all database files are the same and the machine name is the same, yes
it should work. Not supported, though.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Jeff Vandervoort" <jeffv @. jrvsystems dot com> wrote in message
news:%2390OgxPnDHA.3612@.TK2MSFTNGP11.phx.gbl...
> A client has a program that uses a SQL database. They already have a Windows
> 2003 + SQL 2000 SP3a server they had planned to use with this app, then
> discovered the vendor only will not support Windows 2003 + SQL 2000 SP3a
> until the end of the year.
> Our thought is to install Windows 2000 + SQL 2000 as a dual-boot with the
> existing Windows 2003 + SQL 2000 installation. Set the SQL database and log
> folders to the same folders in both installations, and when the vendor
> certifies Windows 2003, boot into 2003 and immediately resume operations
> with minimal downtime.
> Is this workable? Or do we need to keep the two SQL installations completely
> separate and do a backup from Win2000/SQL2000 and then restore to
> Win2003/SQL2000?
> --
> Jeff Vandervoort
> JRVsystems
> http://jrvsystems.com
>|||Thanks for your reply, Tibor.
--
Jeff Vandervoort
JRVsystems
http://jrvsystems.com
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
wrote in message news:%235lyAISnDHA.2312@.TK2MSFTNGP12.phx.gbl...
> Assuming that the folder for all database files are the same and the
machine name is the same, yes
> it should work. Not supported, though.
> --
> Tibor Karaszi, SQL Server MVP
> Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>
> "Jeff Vandervoort" <jeffv @. jrvsystems dot com> wrote in message
> news:%2390OgxPnDHA.3612@.TK2MSFTNGP11.phx.gbl...
> > A client has a program that uses a SQL database. They already have a
Windows
> > 2003 + SQL 2000 SP3a server they had planned to use with this app, then
> > discovered the vendor only will not support Windows 2003 + SQL 2000 SP3a
> > until the end of the year.
> >
> > Our thought is to install Windows 2000 + SQL 2000 as a dual-boot with
the
> > existing Windows 2003 + SQL 2000 installation. Set the SQL database and
log
> > folders to the same folders in both installations, and when the vendor
> > certifies Windows 2003, boot into 2003 and immediately resume operations
> > with minimal downtime.
> >
> > Is this workable? Or do we need to keep the two SQL installations
completely
> > separate and do a backup from Win2000/SQL2000 and then restore to
> > Win2003/SQL2000?
> >
> > --
> >
> > Jeff Vandervoort
> > JRVsystems
> > http://jrvsystems.com
> >
> >
>

dual NIC cards SQL Server does not exist

[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access
denied
I have two NIC cards on my client machine.
NIC #1 is the corporate network where my SQLServer resides.
NIC #2 is for a local device accessed via TCP/IP.
When I try to open a connection to the corporate database I sometimes get
the error above.
If the other device on NIC #2 is powered off I always find the server.
I know the database is always on NIC card #1.
How can I force DBNETLIB to always connect to try a specific NIC card?
Does using named pipes affect this?
Eggle
Try connecting using the IP address for NIC 1.
-Sue
On Wed, 7 Mar 2007 07:22:03 -0800, RedBear
<RedBear@.discussions.microsoft.com> wrote:

>[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access
>denied
>I have two NIC cards on my client machine.
>NIC #1 is the corporate network where my SQLServer resides.
>NIC #2 is for a local device accessed via TCP/IP.
>When I try to open a connection to the corporate database I sometimes get
>the error above.
>If the other device on NIC #2 is powered off I always find the server.
>I know the database is always on NIC card #1.
>How can I force DBNETLIB to always connect to try a specific NIC card?
>Does using named pipes affect this?
|||I have tried IP Address and WINDS name.
The problem is intermittent - connect #1 works, #2 fails, more work more fail.
It seems like the connect is getting routed to NIC #2 where it fails as
expected but never tried on NIC #1 where it would have succeeded.
Can I force a connect onto a specifc NIC card?
The low level connect code should try all NIC cards and declare failure only
after all NIC cards have replied negative or timeed out.
Eggle
"Sue Hoegemeier" wrote:

> Try connecting using the IP address for NIC 1.
> -Sue
> On Wed, 7 Mar 2007 07:22:03 -0800, RedBear
> <RedBear@.discussions.microsoft.com> wrote:
>
>
|||The only way I know of to force it to a specific card is to use that
cards IP address.
Being that it's intermittent, it will be very difficult to
troubleshoot although it's more likely something on the hardware side
of the configuration - maybe something with how the dual NICs are set
up, if you have something like teaming enabled, etc.
And it could be that it's not related to the dual NICs - you could
possible have the intermittent connectivity errors with just one NIC.
The following article has a lot of troubleshooting steps:
http://support.microsoft.com/kb/328306
-Sue
On Mon, 12 Mar 2007 05:18:03 -0700, RedBear
<RedBear@.discussions.microsoft.com> wrote:

>I have tried IP Address and WINDS name.
>The problem is intermittent - connect #1 works, #2 fails, more work more fail.
>It seems like the connect is getting routed to NIC #2 where it fails as
>expected but never tried on NIC #1 where it would have succeeded.
>Can I force a connect onto a specifc NIC card?
>The low level connect code should try all NIC cards and declare failure only
>after all NIC cards have replied negative or timeed out.

Dts?

I need to do the following for a client.
1. Download by FTP a zipped file that contains 10 text files
2. Unzip the file to get to the text files
3. Import data from the text files into separate tables in SQL Server.

notes:
Text files are pipe-delimited.
This is a hosted sql server...therefore I don't have full admin rights or access to other folders on the sql box.

Can this be done using a dts? I've never used DTS, but it seems like this is possible just messing around with the DTS

designer.

Can the unzip part be scripted using a activeX/com component?

Could I use my local server to download the file, then use my local enterprise manager and create the dts to import the data into their remote db?

Thanks for any help!!!! :eek:Yes this can be done. You'll probably have to download the FTP task from www.sqldts.com (http://www.sqldts.com). I'm not sure if the zip process can be done via activeX but it can definately be done using xp_cmdshell. As far as your local server, it can be done that way but sounds risky to me for a production process. Why not deploy the DTS package to the host SQL Server and ftp the files to a network location then import the data into the tables?|||Why not just write a sproc?

And as far as it's hosted...are you saying you can't write to a local drive?

DTS Wizard question

Hi. We're trying to use the DTSWizard.exe that comes with the SQL Server 2005 client tools to move a variety of database objects from one db to another. However, it seems to be limited to only allowing tables or running a SQL script. The SQL 2000 DTS wizard enabled the copying of all database objects. Are we missing something or is this limitation in the 2005 DTS Wizard by intent? Thanks.

You're correct. DTSWizard is primarily for data import/export.

DTS was not upgraded for the new SQL 2005 objects and file definitions. You will have to use SSIS (the replacement for DTS) withSQL 2005 for advanced ETL and database migrations.

|||

arc_dev wrote:

Hi. We're trying to use the DTSWizard.exe that comes with the SQL Server 2005 client tools to move a variety of database objects from one db to another. However, it seems to be limited to only allowing tables or running a SQL script. The SQL 2000 DTS wizard enabled the copying of all database objects. Are we missing something or is this limitation in the 2005 DTS Wizard by intent? Thanks.

I believe it is not there any more...

http://www.databasejournal.com/features/mssql/article.php/3594201

|||

Mahammed,

The DTS Wizard is alive and well. However, it only imports/exports data. It does not import/export and schema objects -as the article you referenced also indicated.

You 'might' want to check using DTSWizard.exe, located in the folder:

{installLocation}\Microsoft SQL Server\90\DTS\Binn\DTSWizard.exe