Showing posts with label instance. Show all posts
Showing posts with label instance. Show all posts

Friday, March 30, 2012

Is it possible to Migrate 2005 database to 2000 engine?

Hi,
We have been developing a new database using 2005 with the understanding
that the deployment would be on a 2005 production instance. Now we learn
that the target server is running 2000. We could create a separate 2005
instance on the same server but it seems that the additional administration
of security and object ownership will be more hassle that downgrading the
empty data objects to 2000. So far, the database consists of about 20
tables with accompanying meta data (table/column descriptions). I was
planning to use sql scripts generated in 2005 to recreate the tables on a
2000 instance but realize that some modifications will be required to
recreate the metadata.
Does anyone have any suggestions on the migration of a 2005 database to
2000?
Thanks, Simon
No easy way ... Try your own manual migration and come up with a white
paper ... Read below link
http://searchsqlserver.techtarget.co...301536,00.html
Keppe on posting the issues you face so that we can help...
Thanks,
Sree
[Please specify the version of Sql Server as we can save one thread and time
asking back if its 2000 or 2005]
"Simon" wrote:

> Hi,
> We have been developing a new database using 2005 with the understanding
> that the deployment would be on a 2005 production instance. Now we learn
> that the target server is running 2000. We could create a separate 2005
> instance on the same server but it seems that the additional administration
> of security and object ownership will be more hassle that downgrading the
> empty data objects to 2000. So far, the database consists of about 20
> tables with accompanying meta data (table/column descriptions). I was
> planning to use sql scripts generated in 2005 to recreate the tables on a
> 2000 instance but realize that some modifications will be required to
> recreate the metadata.
> Does anyone have any suggestions on the migration of a 2005 database to
> 2000?
> Thanks, Simon
>
>
sql

Wednesday, March 28, 2012

Is it possible to Migrate 2005 database to 2000 engine?

Hi,
We have been developing a new database using 2005 with the understanding
that the deployment would be on a 2005 production instance. Now we learn
that the target server is running 2000. We could create a separate 2005
instance on the same server but it seems that the additional administration
of security and object ownership will be more hassle that downgrading the
empty data objects to 2000. So far, the database consists of about 20
tables with accompanying meta data (table/column descriptions). I was
planning to use sql scripts generated in 2005 to recreate the tables on a
2000 instance but realize that some modifications will be required to
recreate the metadata.
Does anyone have any suggestions on the migration of a 2005 database to
2000?
Thanks, SimonNo easy way ... Try your own manual migration and come up with a white
paper ... Read below link
http://searchsqlserver.techtarget.c...x301536,00.html
Keppe on posting the issues you face so that we can help...
Thanks,
Sree
[Please specify the version of Sql Server as we can save one thread and
time
asking back if its 2000 or 2005]
"Simon" wrote:

> Hi,
> We have been developing a new database using 2005 with the understanding
> that the deployment would be on a 2005 production instance. Now we learn
> that the target server is running 2000. We could create a separate 2005
> instance on the same server but it seems that the additional administratio
n
> of security and object ownership will be more hassle that downgrading the
> empty data objects to 2000. So far, the database consists of about 20
> tables with accompanying meta data (table/column descriptions). I was
> planning to use sql scripts generated in 2005 to recreate the tables on a
> 2000 instance but realize that some modifications will be required to
> recreate the metadata.
> Does anyone have any suggestions on the migration of a 2005 database to
> 2000?
> Thanks, Simon
>
>

Is it possible to Migrate 2005 database to 2000 engine?

Hi,
We have been developing a new database using 2005 with the understanding
that the deployment would be on a 2005 production instance. Now we learn
that the target server is running 2000. We could create a separate 2005
instance on the same server but it seems that the additional administration
of security and object ownership will be more hassle that downgrading the
empty data objects to 2000. So far, the database consists of about 20
tables with accompanying meta data (table/column descriptions). I was
planning to use sql scripts generated in 2005 to recreate the tables on a
2000 instance but realize that some modifications will be required to
recreate the metadata.
Does anyone have any suggestions on the migration of a 2005 database to
2000?
Thanks, SimonNo easy way :(... Try your own manual migration and come up with a white
paper :)... Read below link
http://searchsqlserver.techtarget.com/expert/KnowledgebaseAnswer/0,289625,sid87_gci1149585_tax301536,00.html
Keppe on posting the issues you face so that we can help...
--
Thanks,
Sree
[Please specify the version of Sql Server as we can save one thread and time
asking back if its 2000 or 2005]
"Simon" wrote:
> Hi,
> We have been developing a new database using 2005 with the understanding
> that the deployment would be on a 2005 production instance. Now we learn
> that the target server is running 2000. We could create a separate 2005
> instance on the same server but it seems that the additional administration
> of security and object ownership will be more hassle that downgrading the
> empty data objects to 2000. So far, the database consists of about 20
> tables with accompanying meta data (table/column descriptions). I was
> planning to use sql scripts generated in 2005 to recreate the tables on a
> 2000 instance but realize that some modifications will be required to
> recreate the metadata.
> Does anyone have any suggestions on the migration of a 2005 database to
> 2000?
> Thanks, Simon
>
>

Is it possible to install the third instance?

Hi everyone,
I have active-passive two node cluster server, it's already installed two
instances with associated two network names and IP addresses. Is there
possible to install the third instance in this cluster server, if give the
specific network name and IP address but no physical node 3?
Regards,
-Chen
Yes. The Active-Passive, Active-Active nomenclature is left over from SQL
7.0 and no longer accurately represents the clustering capabilities of SQL
Server 2000. The short version is you can have up to 16 instances on a
cluster, regardless of the number of nodes. You can choose which instances
should be on which nodes during normal operating conditions. You do have to
have a unique network name, IP address, and disk resource for each instance.
You also need to make sure you have enough physical resources (memory, CPU,
IO capacity) on each node to handle the work load, even during a failover
condition.
The correct current terms are single-instance and multiple-instance
clusters.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Chen" <Chen@.discussions.microsoft.com> wrote in message
news:430C357E-407A-4F73-8764-DDAFD3203DC2@.microsoft.com...
> Hi everyone,
> I have active-passive two node cluster server, it's already installed two
> instances with associated two network names and IP addresses. Is there
> possible to install the third instance in this cluster server, if give the
> specific network name and IP address but no physical node 3?
> Regards,
> -Chen
>
sql

Monday, March 26, 2012

is it possible to install MSDE after SQL2000?

i installed MSDE _AFTER_ i installed sql2000. i finally got the install to work by specifying the instance name, but i can't connect to my msde instance via enterprise manager. i tried \mycomputer\vsdotnet (the instance name) but it says it's not there. any ideas?nevermind, the instance was netsdk, not vsdotnet.

Friday, March 9, 2012

Is it necessary to install Intergration Service for different instance ?

We have to install another instance to an existing SQL Server 2005 Server.
We would like to know whether it is necessary for us to select Integration
Service ? Besides, we would like to know besides Database Engine, is there
any other service we have to select ?
Moreover, we find that Reporting Services is shown as an instance when we
view "Installed Instance", we would like to know why it behaves as an
instance ?
In addition, it seems that even though we have installed default instance,
SQL Server 2005 still gives us a choice of installing Default Instance.
What will happen if we choose "Default Instance" if there is already have
one ? In SQL Server 2000, the choice of Default Instance is disabled.
Thanks
Peter> We would like to know whether it is necessary for us to select Integration Service ?
You can only have one instance of SSIS (which will serve all database engine instance that need to
use it). So, if SSIS is already installed and you select to install it again, setup will tell you
that it is already installed.
> Besides, we would like to know besides Database Engine, is there any other service we have to
> select ?
Not really. But only you know if you after installing this instance need also, say SSAS.
> Moreover, we find that Reporting Services is shown as an instance when we view "Installed
> Instance", we would like to know why it behaves as an instance ?
Because you can have several instances of RS, just the same way as you can have several instances of
the database engine.
> In addition, it seems that even though we have installed default instance, SQL Server 2005 still
> gives us a choice of installing Default Instance. What will happen if we choose "Default Instance"
> if there is already have one ?
Setup will tell you that it already is installed and won't do anything.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Peter" <Peter@.discussions.microsoft.com> wrote in message
news:e9v0AnyCIHA.4956@.TK2MSFTNGP06.phx.gbl...
> We have to install another instance to an existing SQL Server 2005 Server. We would like to know
> whether it is necessary for us to select Integration Service ? Besides, we would like to know
> besides Database Engine, is there any other service we have to select ?
> Moreover, we find that Reporting Services is shown as an instance when we view "Installed
> Instance", we would like to know why it behaves as an instance ?
> In addition, it seems that even though we have installed default instance, SQL Server 2005 still
> gives us a choice of installing Default Instance. What will happen if we choose "Default Instance"
> if there is already have one ? In SQL Server 2000, the choice of Default Instance is disabled.
> Thanks
> Peter
>|||Dear Tibor,
From your mail, my understanding is that for SSIS, only 1 instance can be
installed.
On the other hand, for others - like RS, AS, Database Engine, we can install
more than 1 instance.
Is there any other services that only installed once - Like Notification
Services ... ?
Peter
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uZ9QyvzCIHA.5328@.TK2MSFTNGP05.phx.gbl...
>> We would like to know whether it is necessary for us to select
>> Integration Service ?
> You can only have one instance of SSIS (which will serve all database
> engine instance that need to use it). So, if SSIS is already installed and
> you select to install it again, setup will tell you that it is already
> installed.
>> Besides, we would like to know besides Database Engine, is there any
>> other service we have to select ?
> Not really. But only you know if you after installing this instance need
> also, say SSAS.
>> Moreover, we find that Reporting Services is shown as an instance when we
>> view "Installed Instance", we would like to know why it behaves as an
>> instance ?
> Because you can have several instances of RS, just the same way as you can
> have several instances of the database engine.
>
>> In addition, it seems that even though we have installed default
>> instance, SQL Server 2005 still gives us a choice of installing Default
>> Instance. What will happen if we choose "Default Instance" if there is
>> already have one ?
> Setup will tell you that it already is installed and won't do anything.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Peter" <Peter@.discussions.microsoft.com> wrote in message
> news:e9v0AnyCIHA.4956@.TK2MSFTNGP06.phx.gbl...
>> We have to install another instance to an existing SQL Server 2005
>> Server. We would like to know whether it is necessary for us to select
>> Integration Service ? Besides, we would like to know besides Database
>> Engine, is there any other service we have to select ?
>> Moreover, we find that Reporting Services is shown as an instance when we
>> view "Installed Instance", we would like to know why it behaves as an
>> instance ?
>> In addition, it seems that even though we have installed default
>> instance, SQL Server 2005 still gives us a choice of installing Default
>> Instance. What will happen if we choose "Default Instance" if there is
>> already have one ? In SQL Server 2000, the choice of Default Instance is
>> disabled.
>> Thanks
>> Peter
>>
>|||Peter,
> From your mail, my understanding is that for SSIS, only 1 instance can be installed.
Correct.
> On the other hand, for others - like RS, AS, Database Engine, we can install more than 1 instance.
Also correct.
> Is there any other services that only installed once - Like Notification Services ... ?
Actually RS, AS and Db Engine are the only services for which you can install several instances.
You can only have one SQL Server browser - it doesn't make sense to have several.
You can only have one SQL Server VSS Writer - it doesn't make sense to have several.
You can only have one SSIS service
As for Notification Services (NS), you can only install it once. But you need to read about NS to
understand what that means. Installation of NS only installs some binary files (essentially). When
you develop an NS solution, you (among other things) run a program (NSCONTROL.EXE) to create the
Windows service. You can have several of these services, but that part is something you do *after*
you have installed the binary files. Also, NS will not ship with 2008, so it is essentially a dead
component which you probably don't want to build new solutions on.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Peter" <Peter@.discussions.microsoft.com> wrote in message
news:ez0wn7%23CIHA.4308@.TK2MSFTNGP06.phx.gbl...
> Dear Tibor,
> From your mail, my understanding is that for SSIS, only 1 instance can be installed.
> On the other hand, for others - like RS, AS, Database Engine, we can install more than 1 instance.
> Is there any other services that only installed once - Like Notification Services ... ?
> Peter
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:uZ9QyvzCIHA.5328@.TK2MSFTNGP05.phx.gbl...
>> We would like to know whether it is necessary for us to select Integration Service ?
>> You can only have one instance of SSIS (which will serve all database engine instance that need
>> to use it). So, if SSIS is already installed and you select to install it again, setup will tell
>> you that it is already installed.
>> Besides, we would like to know besides Database Engine, is there any other service we have to
>> select ?
>> Not really. But only you know if you after installing this instance need also, say SSAS.
>> Moreover, we find that Reporting Services is shown as an instance when we view "Installed
>> Instance", we would like to know why it behaves as an instance ?
>> Because you can have several instances of RS, just the same way as you can have several instances
>> of the database engine.
>>
>> In addition, it seems that even though we have installed default instance, SQL Server 2005 still
>> gives us a choice of installing Default Instance. What will happen if we choose "Default
>> Instance" if there is already have one ?
>> Setup will tell you that it already is installed and won't do anything.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Peter" <Peter@.discussions.microsoft.com> wrote in message
>> news:e9v0AnyCIHA.4956@.TK2MSFTNGP06.phx.gbl...
>> We have to install another instance to an existing SQL Server 2005 Server. We would like to know
>> whether it is necessary for us to select Integration Service ? Besides, we would like to know
>> besides Database Engine, is there any other service we have to select ?
>> Moreover, we find that Reporting Services is shown as an instance when we view "Installed
>> Instance", we would like to know why it behaves as an instance ?
>> In addition, it seems that even though we have installed default instance, SQL Server 2005 still
>> gives us a choice of installing Default Instance. What will happen if we choose "Default
>> Instance" if there is already have one ? In SQL Server 2000, the choice of Default Instance is
>> disabled.
>> Thanks
>> Peter
>>
>>
>

Wednesday, March 7, 2012

Is is possible to change the "name" of an instance

theHi,
Have a named instance of SQL Server, but have discovered that the application for which the SQL Server was installed will not work with a named instance. So, is there a way to change the instance to become a default one, or will it require a full instance
to create the default instance ?
Thanks
Best bet is to install a default instance, then detach your databases on the
named instance and attach them to the default instance.
Richard Waymire, MCSE, MCDBA
This posting is provided "AS IS" with no warranties, and confers no rights.
"Al" <Al@.discussions.microsoft.com> wrote in message
news:BD6F0DF8-457F-47D6-B39D-F75420357363@.microsoft.com...
> theHi,
> Have a named instance of SQL Server, but have discovered that the
> application for which the SQL Server was installed will not work with a
> named instance. So, is there a way to change the instance to become a
> default one, or will it require a full instance to create the default
> instance ?
> Thanks
|||Thanks for that Richard. Pretty much what I figured.
We are actually using an alias to get round the problem, as only a couple of machines need to attach directly to the database.
"Richard Waymire [MSFT]" wrote:

> Best bet is to install a default instance, then detach your databases on the
> named instance and attach them to the default instance.
> --
> Richard Waymire, MCSE, MCDBA
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Al" <Al@.discussions.microsoft.com> wrote in message
> news:BD6F0DF8-457F-47D6-B39D-F75420357363@.microsoft.com...
>
>