I need to change the ip address and machine name on a server which I have sql server 7.0 enterprise edition running on. Is there any specifics to be concerned over (sql registration, etc.)
thanksHi,
AFAIK SQL Server Wont bother about the IP Address. Once
you change the machine name of SQL BOx, you have to delete
the previous registration and re-register with the new
server name.
Run SQL Server 7.0 Setup from the Product CD. This will
just update SQL Server Internally to reflect new machine
name. Once you are done with that you need to update the
SQL Server by the below two stored procedures
sp_dropserver <old_name> go
sp_addserver <newname>, local go
Stop and Restart the SQL Service.
HTH
--
Regards
THIRUMAL REDDY MARAM
Sys Admin / SQL Server DBA
>--Original Message--
>I need to change the ip address and machine name on a
server which I have sql server 7.0 enterprise edition
running on. Is there any specifics to be concerned over
(sql registration, etc.)?
>thanks
>.
>sql
Showing posts with label edition. Show all posts
Showing posts with label edition. Show all posts
Tuesday, March 27, 2012
Change from Enterprise Edition to Developer Edition
We want to install SQL Server 2005 Developer on a server that has SQL Server
2000 Enterprise edition and we are getting an error of you can't upgrade from
Enterprise to Developer. The server is not supporting production and has
never supported production; it is strictly for development activities. Is
there a way we can do that?
Thanks,
Joseph
You can uninstall Enterprise and install Developer. It will not delete any
user dbs but you should have proper backups of all dbs and scripts or a plan
to recreate logins etc if needed.
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
news:0E3E5B6A-27ED-46B2-AA2E-F4E31363E859@.microsoft.com...
> We want to install SQL Server 2005 Developer on a server that has SQL
> Server
> 2000 Enterprise edition and we are getting an error of you can't upgrade
> from
> Enterprise to Developer. The server is not supporting production and has
> never supported production; it is strictly for development activities. Is
> there a way we can do that?
> Thanks,
> Joseph
|||Thanks Andrew. I wanted to avoid uninstalling 2000 because I've never been
able to uninstall it cleanly. Also wanted to see how the upgrade in-place
works for 2005. I want to know if there's a way I can downgrade the
Enterprise to Developer and then upgrade.
Joseph
"Andrew J. Kelly" wrote:
> You can uninstall Enterprise and install Developer. It will not delete any
> user dbs but you should have proper backups of all dbs and scripts or a plan
> to recreate logins etc if needed.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
> news:0E3E5B6A-27ED-46B2-AA2E-F4E31363E859@.microsoft.com...
>
|||Not that I know of. I am pretty sure it will require you to uninstall EE.
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
news:D5495DB1-1592-4339-85EA-3536AA8A81BA@.microsoft.com...[vbcol=seagreen]
> Thanks Andrew. I wanted to avoid uninstalling 2000 because I've never
> been
> able to uninstall it cleanly. Also wanted to see how the upgrade in-place
> works for 2005. I want to know if there's a way I can downgrade the
> Enterprise to Developer and then upgrade.
> Joseph
> "Andrew J. Kelly" wrote:
|||There is no such a path is available because one of the edition is for
production\business purposes and the other one is for totally different
purpose which is development\test.
Here' s a list of available upgrade paths:
http://technet.microsoft.com/en-us/library/ms143393.aspx
Ekrem ?nsoy
"SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
news:D5495DB1-1592-4339-85EA-3536AA8A81BA@.microsoft.com...[vbcol=seagreen]
> Thanks Andrew. I wanted to avoid uninstalling 2000 because I've never
> been
> able to uninstall it cleanly. Also wanted to see how the upgrade in-place
> works for 2005. I want to know if there's a way I can downgrade the
> Enterprise to Developer and then upgrade.
> Joseph
> "Andrew J. Kelly" wrote:
2000 Enterprise edition and we are getting an error of you can't upgrade from
Enterprise to Developer. The server is not supporting production and has
never supported production; it is strictly for development activities. Is
there a way we can do that?
Thanks,
Joseph
You can uninstall Enterprise and install Developer. It will not delete any
user dbs but you should have proper backups of all dbs and scripts or a plan
to recreate logins etc if needed.
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
news:0E3E5B6A-27ED-46B2-AA2E-F4E31363E859@.microsoft.com...
> We want to install SQL Server 2005 Developer on a server that has SQL
> Server
> 2000 Enterprise edition and we are getting an error of you can't upgrade
> from
> Enterprise to Developer. The server is not supporting production and has
> never supported production; it is strictly for development activities. Is
> there a way we can do that?
> Thanks,
> Joseph
|||Thanks Andrew. I wanted to avoid uninstalling 2000 because I've never been
able to uninstall it cleanly. Also wanted to see how the upgrade in-place
works for 2005. I want to know if there's a way I can downgrade the
Enterprise to Developer and then upgrade.
Joseph
"Andrew J. Kelly" wrote:
> You can uninstall Enterprise and install Developer. It will not delete any
> user dbs but you should have proper backups of all dbs and scripts or a plan
> to recreate logins etc if needed.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
> news:0E3E5B6A-27ED-46B2-AA2E-F4E31363E859@.microsoft.com...
>
|||Not that I know of. I am pretty sure it will require you to uninstall EE.
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
news:D5495DB1-1592-4339-85EA-3536AA8A81BA@.microsoft.com...[vbcol=seagreen]
> Thanks Andrew. I wanted to avoid uninstalling 2000 because I've never
> been
> able to uninstall it cleanly. Also wanted to see how the upgrade in-place
> works for 2005. I want to know if there's a way I can downgrade the
> Enterprise to Developer and then upgrade.
> Joseph
> "Andrew J. Kelly" wrote:
|||There is no such a path is available because one of the edition is for
production\business purposes and the other one is for totally different
purpose which is development\test.
Here' s a list of available upgrade paths:
http://technet.microsoft.com/en-us/library/ms143393.aspx
Ekrem ?nsoy
"SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
news:D5495DB1-1592-4339-85EA-3536AA8A81BA@.microsoft.com...[vbcol=seagreen]
> Thanks Andrew. I wanted to avoid uninstalling 2000 because I've never
> been
> able to uninstall it cleanly. Also wanted to see how the upgrade in-place
> works for 2005. I want to know if there's a way I can downgrade the
> Enterprise to Developer and then upgrade.
> Joseph
> "Andrew J. Kelly" wrote:
Change from Enterprise Edition to Developer Edition
We want to install SQL Server 2005 Developer on a server that has SQL Server
2000 Enterprise edition and we are getting an error of you can't upgrade fro
m
Enterprise to Developer. The server is not supporting production and has
never supported production; it is strictly for development activities. Is
there a way we can do that?
Thanks,
JosephYou can uninstall Enterprise and install Developer. It will not delete any
user dbs but you should have proper backups of all dbs and scripts or a plan
to recreate logins etc if needed.
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
news:0E3E5B6A-27ED-46B2-AA2E-F4E31363E859@.microsoft.com...
> We want to install SQL Server 2005 Developer on a server that has SQL
> Server
> 2000 Enterprise edition and we are getting an error of you can't upgrade
> from
> Enterprise to Developer. The server is not supporting production and has
> never supported production; it is strictly for development activities. Is
> there a way we can do that?
> Thanks,
> Joseph|||Thanks Andrew. I wanted to avoid uninstalling 2000 because I've never been
able to uninstall it cleanly. Also wanted to see how the upgrade in-place
works for 2005. I want to know if there's a way I can downgrade the
Enterprise to Developer and then upgrade.
Joseph
"Andrew J. Kelly" wrote:
> You can uninstall Enterprise and install Developer. It will not delete any
> user dbs but you should have proper backups of all dbs and scripts or a pl
an
> to recreate logins etc if needed.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
> news:0E3E5B6A-27ED-46B2-AA2E-F4E31363E859@.microsoft.com...
>|||Not that I know of. I am pretty sure it will require you to uninstall EE.
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
news:D5495DB1-1592-4339-85EA-3536AA8A81BA@.microsoft.com...[vbcol=seagreen]
> Thanks Andrew. I wanted to avoid uninstalling 2000 because I've never
> been
> able to uninstall it cleanly. Also wanted to see how the upgrade in-place
> works for 2005. I want to know if there's a way I can downgrade the
> Enterprise to Developer and then upgrade.
> Joseph
> "Andrew J. Kelly" wrote:
>|||There is no such a path is available because one of the edition is for
production\business purposes and the other one is for totally different
purpose which is development\test.
Here' s a list of available upgrade paths:
http://technet.microsoft.com/en-us/...y/ms143393.aspx
Ekrem ?nsoy
"SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
news:D5495DB1-1592-4339-85EA-3536AA8A81BA@.microsoft.com...[vbcol=seagreen]
> Thanks Andrew. I wanted to avoid uninstalling 2000 because I've never
> been
> able to uninstall it cleanly. Also wanted to see how the upgrade in-place
> works for 2005. I want to know if there's a way I can downgrade the
> Enterprise to Developer and then upgrade.
> Joseph
> "Andrew J. Kelly" wrote:
>sql
2000 Enterprise edition and we are getting an error of you can't upgrade fro
m
Enterprise to Developer. The server is not supporting production and has
never supported production; it is strictly for development activities. Is
there a way we can do that?
Thanks,
JosephYou can uninstall Enterprise and install Developer. It will not delete any
user dbs but you should have proper backups of all dbs and scripts or a plan
to recreate logins etc if needed.
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
news:0E3E5B6A-27ED-46B2-AA2E-F4E31363E859@.microsoft.com...
> We want to install SQL Server 2005 Developer on a server that has SQL
> Server
> 2000 Enterprise edition and we are getting an error of you can't upgrade
> from
> Enterprise to Developer. The server is not supporting production and has
> never supported production; it is strictly for development activities. Is
> there a way we can do that?
> Thanks,
> Joseph|||Thanks Andrew. I wanted to avoid uninstalling 2000 because I've never been
able to uninstall it cleanly. Also wanted to see how the upgrade in-place
works for 2005. I want to know if there's a way I can downgrade the
Enterprise to Developer and then upgrade.
Joseph
"Andrew J. Kelly" wrote:
> You can uninstall Enterprise and install Developer. It will not delete any
> user dbs but you should have proper backups of all dbs and scripts or a pl
an
> to recreate logins etc if needed.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
> news:0E3E5B6A-27ED-46B2-AA2E-F4E31363E859@.microsoft.com...
>|||Not that I know of. I am pretty sure it will require you to uninstall EE.
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
news:D5495DB1-1592-4339-85EA-3536AA8A81BA@.microsoft.com...[vbcol=seagreen]
> Thanks Andrew. I wanted to avoid uninstalling 2000 because I've never
> been
> able to uninstall it cleanly. Also wanted to see how the upgrade in-place
> works for 2005. I want to know if there's a way I can downgrade the
> Enterprise to Developer and then upgrade.
> Joseph
> "Andrew J. Kelly" wrote:
>|||There is no such a path is available because one of the edition is for
production\business purposes and the other one is for totally different
purpose which is development\test.
Here' s a list of available upgrade paths:
http://technet.microsoft.com/en-us/...y/ms143393.aspx
Ekrem ?nsoy
"SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
news:D5495DB1-1592-4339-85EA-3536AA8A81BA@.microsoft.com...[vbcol=seagreen]
> Thanks Andrew. I wanted to avoid uninstalling 2000 because I've never
> been
> able to uninstall it cleanly. Also wanted to see how the upgrade in-place
> works for 2005. I want to know if there's a way I can downgrade the
> Enterprise to Developer and then upgrade.
> Joseph
> "Andrew J. Kelly" wrote:
>sql
Change from Enterprise Edition to Developer Edition
We want to install SQL Server 2005 Developer on a server that has SQL Server
2000 Enterprise edition and we are getting an error of you can't upgrade from
Enterprise to Developer. The server is not supporting production and has
never supported production; it is strictly for development activities. Is
there a way we can do that?
Thanks,
JosephYou can uninstall Enterprise and install Developer. It will not delete any
user dbs but you should have proper backups of all dbs and scripts or a plan
to recreate logins etc if needed.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
news:0E3E5B6A-27ED-46B2-AA2E-F4E31363E859@.microsoft.com...
> We want to install SQL Server 2005 Developer on a server that has SQL
> Server
> 2000 Enterprise edition and we are getting an error of you can't upgrade
> from
> Enterprise to Developer. The server is not supporting production and has
> never supported production; it is strictly for development activities. Is
> there a way we can do that?
> Thanks,
> Joseph|||Thanks Andrew. I wanted to avoid uninstalling 2000 because I've never been
able to uninstall it cleanly. Also wanted to see how the upgrade in-place
works for 2005. I want to know if there's a way I can downgrade the
Enterprise to Developer and then upgrade.
Joseph
"Andrew J. Kelly" wrote:
> You can uninstall Enterprise and install Developer. It will not delete any
> user dbs but you should have proper backups of all dbs and scripts or a plan
> to recreate logins etc if needed.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
> news:0E3E5B6A-27ED-46B2-AA2E-F4E31363E859@.microsoft.com...
> > We want to install SQL Server 2005 Developer on a server that has SQL
> > Server
> > 2000 Enterprise edition and we are getting an error of you can't upgrade
> > from
> > Enterprise to Developer. The server is not supporting production and has
> > never supported production; it is strictly for development activities. Is
> > there a way we can do that?
> >
> > Thanks,
> >
> > Joseph
>|||Not that I know of. I am pretty sure it will require you to uninstall EE.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
news:D5495DB1-1592-4339-85EA-3536AA8A81BA@.microsoft.com...
> Thanks Andrew. I wanted to avoid uninstalling 2000 because I've never
> been
> able to uninstall it cleanly. Also wanted to see how the upgrade in-place
> works for 2005. I want to know if there's a way I can downgrade the
> Enterprise to Developer and then upgrade.
> Joseph
> "Andrew J. Kelly" wrote:
>> You can uninstall Enterprise and install Developer. It will not delete
>> any
>> user dbs but you should have proper backups of all dbs and scripts or a
>> plan
>> to recreate logins etc if needed.
>> --
>> Andrew J. Kelly SQL MVP
>> Solid Quality Mentors
>>
>> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
>> news:0E3E5B6A-27ED-46B2-AA2E-F4E31363E859@.microsoft.com...
>> > We want to install SQL Server 2005 Developer on a server that has SQL
>> > Server
>> > 2000 Enterprise edition and we are getting an error of you can't
>> > upgrade
>> > from
>> > Enterprise to Developer. The server is not supporting production and
>> > has
>> > never supported production; it is strictly for development activities.
>> > Is
>> > there a way we can do that?
>> >
>> > Thanks,
>> >
>> > Joseph
>>|||There is no such a path is available because one of the edition is for
production\business purposes and the other one is for totally different
purpose which is development\test.
Here' s a list of available upgrade paths:
http://technet.microsoft.com/en-us/library/ms143393.aspx
--
Ekrem Ã?nsoy
"SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
news:D5495DB1-1592-4339-85EA-3536AA8A81BA@.microsoft.com...
> Thanks Andrew. I wanted to avoid uninstalling 2000 because I've never
> been
> able to uninstall it cleanly. Also wanted to see how the upgrade in-place
> works for 2005. I want to know if there's a way I can downgrade the
> Enterprise to Developer and then upgrade.
> Joseph
> "Andrew J. Kelly" wrote:
>> You can uninstall Enterprise and install Developer. It will not delete
>> any
>> user dbs but you should have proper backups of all dbs and scripts or a
>> plan
>> to recreate logins etc if needed.
>> --
>> Andrew J. Kelly SQL MVP
>> Solid Quality Mentors
>>
>> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
>> news:0E3E5B6A-27ED-46B2-AA2E-F4E31363E859@.microsoft.com...
>> > We want to install SQL Server 2005 Developer on a server that has SQL
>> > Server
>> > 2000 Enterprise edition and we are getting an error of you can't
>> > upgrade
>> > from
>> > Enterprise to Developer. The server is not supporting production and
>> > has
>> > never supported production; it is strictly for development activities.
>> > Is
>> > there a way we can do that?
>> >
>> > Thanks,
>> >
>> > Joseph
>>
2000 Enterprise edition and we are getting an error of you can't upgrade from
Enterprise to Developer. The server is not supporting production and has
never supported production; it is strictly for development activities. Is
there a way we can do that?
Thanks,
JosephYou can uninstall Enterprise and install Developer. It will not delete any
user dbs but you should have proper backups of all dbs and scripts or a plan
to recreate logins etc if needed.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
news:0E3E5B6A-27ED-46B2-AA2E-F4E31363E859@.microsoft.com...
> We want to install SQL Server 2005 Developer on a server that has SQL
> Server
> 2000 Enterprise edition and we are getting an error of you can't upgrade
> from
> Enterprise to Developer. The server is not supporting production and has
> never supported production; it is strictly for development activities. Is
> there a way we can do that?
> Thanks,
> Joseph|||Thanks Andrew. I wanted to avoid uninstalling 2000 because I've never been
able to uninstall it cleanly. Also wanted to see how the upgrade in-place
works for 2005. I want to know if there's a way I can downgrade the
Enterprise to Developer and then upgrade.
Joseph
"Andrew J. Kelly" wrote:
> You can uninstall Enterprise and install Developer. It will not delete any
> user dbs but you should have proper backups of all dbs and scripts or a plan
> to recreate logins etc if needed.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
> news:0E3E5B6A-27ED-46B2-AA2E-F4E31363E859@.microsoft.com...
> > We want to install SQL Server 2005 Developer on a server that has SQL
> > Server
> > 2000 Enterprise edition and we are getting an error of you can't upgrade
> > from
> > Enterprise to Developer. The server is not supporting production and has
> > never supported production; it is strictly for development activities. Is
> > there a way we can do that?
> >
> > Thanks,
> >
> > Joseph
>|||Not that I know of. I am pretty sure it will require you to uninstall EE.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
news:D5495DB1-1592-4339-85EA-3536AA8A81BA@.microsoft.com...
> Thanks Andrew. I wanted to avoid uninstalling 2000 because I've never
> been
> able to uninstall it cleanly. Also wanted to see how the upgrade in-place
> works for 2005. I want to know if there's a way I can downgrade the
> Enterprise to Developer and then upgrade.
> Joseph
> "Andrew J. Kelly" wrote:
>> You can uninstall Enterprise and install Developer. It will not delete
>> any
>> user dbs but you should have proper backups of all dbs and scripts or a
>> plan
>> to recreate logins etc if needed.
>> --
>> Andrew J. Kelly SQL MVP
>> Solid Quality Mentors
>>
>> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
>> news:0E3E5B6A-27ED-46B2-AA2E-F4E31363E859@.microsoft.com...
>> > We want to install SQL Server 2005 Developer on a server that has SQL
>> > Server
>> > 2000 Enterprise edition and we are getting an error of you can't
>> > upgrade
>> > from
>> > Enterprise to Developer. The server is not supporting production and
>> > has
>> > never supported production; it is strictly for development activities.
>> > Is
>> > there a way we can do that?
>> >
>> > Thanks,
>> >
>> > Joseph
>>|||There is no such a path is available because one of the edition is for
production\business purposes and the other one is for totally different
purpose which is development\test.
Here' s a list of available upgrade paths:
http://technet.microsoft.com/en-us/library/ms143393.aspx
--
Ekrem Ã?nsoy
"SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
news:D5495DB1-1592-4339-85EA-3536AA8A81BA@.microsoft.com...
> Thanks Andrew. I wanted to avoid uninstalling 2000 because I've never
> been
> able to uninstall it cleanly. Also wanted to see how the upgrade in-place
> works for 2005. I want to know if there's a way I can downgrade the
> Enterprise to Developer and then upgrade.
> Joseph
> "Andrew J. Kelly" wrote:
>> You can uninstall Enterprise and install Developer. It will not delete
>> any
>> user dbs but you should have proper backups of all dbs and scripts or a
>> plan
>> to recreate logins etc if needed.
>> --
>> Andrew J. Kelly SQL MVP
>> Solid Quality Mentors
>>
>> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
>> news:0E3E5B6A-27ED-46B2-AA2E-F4E31363E859@.microsoft.com...
>> > We want to install SQL Server 2005 Developer on a server that has SQL
>> > Server
>> > 2000 Enterprise edition and we are getting an error of you can't
>> > upgrade
>> > from
>> > Enterprise to Developer. The server is not supporting production and
>> > has
>> > never supported production; it is strictly for development activities.
>> > Is
>> > there a way we can do that?
>> >
>> > Thanks,
>> >
>> > Joseph
>>
Sunday, March 25, 2012
change enterprise to standard edition
I need to change my current SQL 2000 enterprise editon to SQL 2000 standard
edtion. May I know what is the best way to do it?
andrew,
You need to uninstall enterprise and install standard. There's no short
cut I'm afraid. You can upgrade from standard to enterprise though.
Steps:
1) Back up all your dbs
2) Detach all your databases
3) Uninstall enterprise
4) Install standard
5) Attach the databases
If the attach fails, you can restore them.
Read this before doing anything:
INF: Effects of Moving a Database from SQL 2000 Enterprise Edition to
SQL 2000 Standard Edition
http://support.microsoft.com/?id=268361
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
andrew wrote:
> I need to change my current SQL 2000 enterprise editon to SQL 2000 standard
> edtion. May I know what is the best way to do it?
sql
edtion. May I know what is the best way to do it?
andrew,
You need to uninstall enterprise and install standard. There's no short
cut I'm afraid. You can upgrade from standard to enterprise though.
Steps:
1) Back up all your dbs
2) Detach all your databases
3) Uninstall enterprise
4) Install standard
5) Attach the databases
If the attach fails, you can restore them.
Read this before doing anything:
INF: Effects of Moving a Database from SQL 2000 Enterprise Edition to
SQL 2000 Standard Edition
http://support.microsoft.com/?id=268361
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
andrew wrote:
> I need to change my current SQL 2000 enterprise editon to SQL 2000 standard
> edtion. May I know what is the best way to do it?
sql
change enterprise to standard edition
I need to change my current SQL 2000 enterprise editon to SQL 2000 standard
edtion. May I know what is the best way to do it?andrew,
You need to uninstall enterprise and install standard. There's no short
cut I'm afraid. You can upgrade from standard to enterprise though.
Steps:
1) Back up all your dbs
2) Detach all your databases
3) Uninstall enterprise
4) Install standard
5) Attach the databases
If the attach fails, you can restore them.
Read this before doing anything:
INF: Effects of Moving a Database from SQL 2000 Enterprise Edition to
SQL 2000 Standard Edition
http://support.microsoft.com/?id=268361
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
andrew wrote:
> I need to change my current SQL 2000 enterprise editon to SQL 2000 standard
> edtion. May I know what is the best way to do it?
edtion. May I know what is the best way to do it?andrew,
You need to uninstall enterprise and install standard. There's no short
cut I'm afraid. You can upgrade from standard to enterprise though.
Steps:
1) Back up all your dbs
2) Detach all your databases
3) Uninstall enterprise
4) Install standard
5) Attach the databases
If the attach fails, you can restore them.
Read this before doing anything:
INF: Effects of Moving a Database from SQL 2000 Enterprise Edition to
SQL 2000 Standard Edition
http://support.microsoft.com/?id=268361
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
andrew wrote:
> I need to change my current SQL 2000 enterprise editon to SQL 2000 standard
> edtion. May I know what is the best way to do it?
change enterprise to standard edition
I need to change my current SQL 2000 enterprise editon to SQL 2000 standard
edtion. May I know what is the best way to do it?andrew,
You need to uninstall enterprise and install standard. There's no short
cut I'm afraid. You can upgrade from standard to enterprise though.
Steps:
1) Back up all your dbs
2) Detach all your databases
3) Uninstall enterprise
4) Install standard
5) Attach the databases
If the attach fails, you can restore them.
Read this before doing anything:
INF: Effects of Moving a Database from SQL 2000 Enterprise Edition to
SQL 2000 Standard Edition
http://support.microsoft.com/?id=268361
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
andrew wrote:
> I need to change my current SQL 2000 enterprise editon to SQL 2000 standar
d
> edtion. May I know what is the best way to do it?
edtion. May I know what is the best way to do it?andrew,
You need to uninstall enterprise and install standard. There's no short
cut I'm afraid. You can upgrade from standard to enterprise though.
Steps:
1) Back up all your dbs
2) Detach all your databases
3) Uninstall enterprise
4) Install standard
5) Attach the databases
If the attach fails, you can restore them.
Read this before doing anything:
INF: Effects of Moving a Database from SQL 2000 Enterprise Edition to
SQL 2000 Standard Edition
http://support.microsoft.com/?id=268361
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
andrew wrote:
> I need to change my current SQL 2000 enterprise editon to SQL 2000 standar
d
> edtion. May I know what is the best way to do it?
Change Edition of existing isntance?
I have a named instance of SQL Server 2005 Developer Edition. I want to install VS Team System Foundation Server on the same box, but this needs a default instance of Standard or Enterprise edition. I installed the Standard version alongside the existing Developer instance but now I can't start SSIS and without it VSTS Foundation Server won't install.
I have tried to uninstall SSIS and reisntall it from both the Standard Edition and Developer edition media, but it makes no difference, the service still won't start.
Could the SSIS failure be due to having different editions on the same box? If so, is it possible to change the edition of the Developer instance to Standard (or to change them both to Enterprise edition) without having to uninstall and start all over again. The developer instance is used by several team members, so I don't want to have to uninstall it if I can help.
Any ideas anyone?
No. I should not be something like that as different SQL Server 2005 SKUs(Editions) can be installed side by side successfully provided that they have unique instance names. What kind of processor architecture of your machine? If you install 32-bit and 64-bit SQL Server 2005 on an x64 machines side by side, which is also supported, then it is possible that only one version of SSIS works at one time.|||Both isntances are 32-bit. Only differnece is that named instance is Developer Edition and default instance is Standard Edition|||
Having two different editions (Developer and Standard) on the same box should not cause SSIS to be unable to start. Do the event logs have any messages? When you installed the second instance, did you change any of the logon service accounts?
Thanks,
Sam Lester (MSFT)
Here is a lengthy thread on SSIS not starting. Can you read through it and see if it applies to your situation?
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=375216&SiteID=1
Thanks,
Sam
Change Edition of existing isntance?
I have a named instance of SQL Server 2005 Developer Edition. I want to install VS Team System Foundation Server on the same box, but this needs a default instance of Standard or Enterprise edition. I installed the Standard version alongside the existing Developer instance but now I can't start SSIS and without it VSTS Foundation Server won't install.
I have tried to uninstall SSIS and reisntall it from both the Standard Edition and Developer edition media, but it makes no difference, the service still won't start.
Could the SSIS failure be due to having different editions on the same box? If so, is it possible to change the edition of the Developer instance to Standard (or to change them both to Enterprise edition) without having to uninstall and start all over again. The developer instance is used by several team members, so I don't want to have to uninstall it if I can help.
Any ideas anyone?
No. I should not be something like that as different SQL Server 2005 SKUs(Editions) can be installed side by side successfully provided that they have unique instance names. What kind of processor architecture of your machine? If you install 32-bit and 64-bit SQL Server 2005 on an x64 machines side by side, which is also supported, then it is possible that only one version of SSIS works at one time.|||Both isntances are 32-bit. Only differnece is that named instance is Developer Edition and default instance is Standard Edition|||Having two different editions (Developer and Standard) on the same box should not cause SSIS to be unable to start. Do the event logs have any messages? When you installed the second instance, did you change any of the logon service accounts?
Thanks,
Sam Lester (MSFT)
Here is a lengthy thread on SSIS not starting. Can you read through it and see if it applies to your situation?
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=375216&SiteID=1
Thanks,
Sam
Tuesday, March 20, 2012
change DB owner
I have several Production Databases on my SQL Server 2000 Standard Edition Server (mixed mode authentication) that I'd like to change DBO Permissions on. When I look at the Properties of the DB(s) from EM, the Database owner is showing up as a Windows NT USer who is no longer even with the company!!
Can I use the sp_changedbowner 'sa' command to change the database owner to sa without disrupting Production? Might sound like a dumb question.. but ya never know!!!!! Also, I had someone on another forum tell me that 'sa' as db owner is a bad idea but I don't know why??? can anyone elaborate on that???I am also interested in these questions (and so have posted to just put it back to the top of the list in the hope someone can answer - is that bad etiquette?)|||Yes, you can always change the database owner to sa. At least as far as I know, this is a good idea in almost every case.
As far as the person that thought it was a bad idea, I'd love to hear their reasoning... While I can concoct a case where it was a bad idea, it would take some considerable doing, and would probably never happen in "the real world".
-PatP|||Thank's Pat.
jpotucek, even though the user that own's the database has left, does their Windows account still exist? Does it cause you any issues?|||The only reason I ever had a person other than sa as dbo, was when I had a person who kept forgetting to put dbo in front of objects she created.
Tim S|||I don't manage the NT accounts here, just the logins on the SQL Server. The accounts still exist and they may even be disabled, i don't know. I'm going to change the DB Owner on all to sa and drop the users from my sql servers - then I know i won't have any problems!!!!
THank you one and all
Can I use the sp_changedbowner 'sa' command to change the database owner to sa without disrupting Production? Might sound like a dumb question.. but ya never know!!!!! Also, I had someone on another forum tell me that 'sa' as db owner is a bad idea but I don't know why??? can anyone elaborate on that???I am also interested in these questions (and so have posted to just put it back to the top of the list in the hope someone can answer - is that bad etiquette?)|||Yes, you can always change the database owner to sa. At least as far as I know, this is a good idea in almost every case.
As far as the person that thought it was a bad idea, I'd love to hear their reasoning... While I can concoct a case where it was a bad idea, it would take some considerable doing, and would probably never happen in "the real world".
-PatP|||Thank's Pat.
jpotucek, even though the user that own's the database has left, does their Windows account still exist? Does it cause you any issues?|||The only reason I ever had a person other than sa as dbo, was when I had a person who kept forgetting to put dbo in front of objects she created.
Tim S|||I don't manage the NT accounts here, just the logins on the SQL Server. The accounts still exist and they may even be disabled, i don't know. I'm going to change the DB Owner on all to sa and drop the users from my sql servers - then I know i won't have any problems!!!!
THank you one and all
Wednesday, March 7, 2012
Challenge to all DBAs
I have a challenge for all DBAs. I am getting INCONSISTENT TIMINGS for Querry Results from a SQL Server 2000 Standard Edition on a HP Proliant 2 CPU Server with 4 GB RAM and SCSI DrivAFAe.
Our Database is 72 million records and have 8 columns. Most of them are indexed, which are used in the "Where…" clause. In addition to independent indexes, we also have a covering index for 3 most frequently searched fields.
My challenge is that out of the 7000 odd queries that hit the server with various search conditions in a Week, 5% of the queries return result in less than a minute.
The same query at a different Time or with a different Value, returns results inconsistently. For e.g. searching FirstName = "Anna"; LastName = "Williams" returns result in 0.01 sec. Searching for FirstName "Benjamin"; LastName = "Watson" returns in 5 minutes.
Any kind of help is welcome and will be highly appreciated.
- Santy
san.rely@.gmail.com
Note: Edited to fix white on white font.
Friday, February 24, 2012
CELCO - SQL For Smarties 2005 Ed.
Joe,
Kudos to you on a job well done. Will be adding your 2005 edition to my
personal SQL book library as well as a recommended SQL book for others.
JerryHurricane Celko...
I just purchased the "Joe Celko's SQL for Smarties: Advanced SQL
Programming."
Yosh
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:%23EZc5v5zFHA.2912@.TK2MSFTNGP10.phx.gbl...
> Joe,
> Kudos to you on a job well done. Will be adding your 2005 edition to my
> personal SQL book library as well as a recommended SQL book for others.
> Jerry
>|||I notice its still not been updated to the current ANSI 99 standard and is
16 years old now (ANSI 89).
Whilst it contains some good fundementals there are better books that taylor
to Microsoft SQL Server rather than a standard that isn't commonly used in
the wider community on a day to day basis.
Ken Henderson and Itzik Ben Gan have both done some really excellant
advanced t-SQL books that have immediate use to you as a SQL Server
developer/dba.
My 2 cents.
Tony Rogerson
SQL Server MVP
http://sqlserverfaq.com - free video tutorials
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:%23EZc5v5zFHA.2912@.TK2MSFTNGP10.phx.gbl...
> Joe,
> Kudos to you on a job well done. Will be adding your 2005 edition to my
> personal SQL book library as well as a recommended SQL book for others.
> Jerry
>|||On Wed, 12 Oct 2005 19:15:24 -0700, "Jerry Spivey"
<jspivey@.vestas-awt.com> wrote:
>Joe,
>Kudos to you on a job well done. Will be adding your 2005 edition to my
>personal SQL book library as well as a recommended SQL book for others.
>Jerry
Jerry,
A basic question or two.
If you don't have the book already in your library how can you be sure
it's a job well done?
What do you think its strengths are? How relevant, for example, is
(what seems to be) a generic SQL book to a T-SQL context?
I am not sniping simply asking for clarification to better understand
the basis for your assessment.
Thanks.
Andrew Watt
MVP - InfoPath|||howd you get SQL into a packet of smarties anyway...?
"Jerry Spivey" wrote:
> Joe,
> Kudos to you on a job well done. Will be adding your 2005 edition to my
> personal SQL book library as well as a recommended SQL book for others.
> Jerry
>
>|||Tony,
Yes...Ken's book is one of the best and I like Itzik's as well. Would put
Ken and Kalen's as two of the top SQL Server books available.
Jerry
"Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
news:ubORBL9zFHA.2076@.TK2MSFTNGP14.phx.gbl...
>I notice its still not been updated to the current ANSI 99 standard and is
>16 years old now (ANSI 89).
> Whilst it contains some good fundementals there are better books that
> taylor to Microsoft SQL Server rather than a standard that isn't commonly
> used in the wider community on a day to day basis.
> Ken Henderson and Itzik Ben Gan have both done some really excellant
> advanced t-SQL books that have immediate use to you as a SQL Server
> developer/dba.
> My 2 cents.
> --
> Tony Rogerson
> SQL Server MVP
> http://sqlserverfaq.com - free video tutorials
>
> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
> news:%23EZc5v5zFHA.2912@.TK2MSFTNGP10.phx.gbl...
>|||Hi Andrew,
I own about 40+ SQL/SQL Server books and I've taught SQL Server for 7 years.
I base my book recommendations on content, ease of readability and
relevancy. I do own Joe's 1999 edition. In fact I was just going through
it when I stopped by the book store and happend to notice his 2005 edition.
I was impressed with the additional content (coverage and examples). In
fact the book has increased in size by over 250 pages. While personally I
believe Ken and Kalen's books are the two best SQL Server books on the
market I feel Joe's book is one of the top SQL books on the market.
HTH
Jerry
"Andrew Watt [MVP - InfoPath]" <SVGDeveloper@.aol.com> wrote in message
news:7mask1toptlh9gsqqmbqr5vrg9vmpmaun0@.
4ax.com...
> On Wed, 12 Oct 2005 19:15:24 -0700, "Jerry Spivey"
> <jspivey@.vestas-awt.com> wrote:
>
> Jerry,
> A basic question or two.
> If you don't have the book already in your library how can you be sure
> it's a job well done?
> What do you think its strengths are? How relevant, for example, is
> (what seems to be) a generic SQL book to a T-SQL context?
> I am not sniping simply asking for clarification to better understand
> the basis for your assessment.
> Thanks.
> Andrew Watt
> MVP - InfoPath
Kudos to you on a job well done. Will be adding your 2005 edition to my
personal SQL book library as well as a recommended SQL book for others.
JerryHurricane Celko...
I just purchased the "Joe Celko's SQL for Smarties: Advanced SQL
Programming."
Yosh
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:%23EZc5v5zFHA.2912@.TK2MSFTNGP10.phx.gbl...
> Joe,
> Kudos to you on a job well done. Will be adding your 2005 edition to my
> personal SQL book library as well as a recommended SQL book for others.
> Jerry
>|||I notice its still not been updated to the current ANSI 99 standard and is
16 years old now (ANSI 89).
Whilst it contains some good fundementals there are better books that taylor
to Microsoft SQL Server rather than a standard that isn't commonly used in
the wider community on a day to day basis.
Ken Henderson and Itzik Ben Gan have both done some really excellant
advanced t-SQL books that have immediate use to you as a SQL Server
developer/dba.
My 2 cents.
Tony Rogerson
SQL Server MVP
http://sqlserverfaq.com - free video tutorials
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:%23EZc5v5zFHA.2912@.TK2MSFTNGP10.phx.gbl...
> Joe,
> Kudos to you on a job well done. Will be adding your 2005 edition to my
> personal SQL book library as well as a recommended SQL book for others.
> Jerry
>|||On Wed, 12 Oct 2005 19:15:24 -0700, "Jerry Spivey"
<jspivey@.vestas-awt.com> wrote:
>Joe,
>Kudos to you on a job well done. Will be adding your 2005 edition to my
>personal SQL book library as well as a recommended SQL book for others.
>Jerry
Jerry,
A basic question or two.
If you don't have the book already in your library how can you be sure
it's a job well done?
What do you think its strengths are? How relevant, for example, is
(what seems to be) a generic SQL book to a T-SQL context?
I am not sniping simply asking for clarification to better understand
the basis for your assessment.
Thanks.
Andrew Watt
MVP - InfoPath|||howd you get SQL into a packet of smarties anyway...?
"Jerry Spivey" wrote:
> Joe,
> Kudos to you on a job well done. Will be adding your 2005 edition to my
> personal SQL book library as well as a recommended SQL book for others.
> Jerry
>
>|||Tony,
Yes...Ken's book is one of the best and I like Itzik's as well. Would put
Ken and Kalen's as two of the top SQL Server books available.
Jerry
"Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
news:ubORBL9zFHA.2076@.TK2MSFTNGP14.phx.gbl...
>I notice its still not been updated to the current ANSI 99 standard and is
>16 years old now (ANSI 89).
> Whilst it contains some good fundementals there are better books that
> taylor to Microsoft SQL Server rather than a standard that isn't commonly
> used in the wider community on a day to day basis.
> Ken Henderson and Itzik Ben Gan have both done some really excellant
> advanced t-SQL books that have immediate use to you as a SQL Server
> developer/dba.
> My 2 cents.
> --
> Tony Rogerson
> SQL Server MVP
> http://sqlserverfaq.com - free video tutorials
>
> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
> news:%23EZc5v5zFHA.2912@.TK2MSFTNGP10.phx.gbl...
>|||Hi Andrew,
I own about 40+ SQL/SQL Server books and I've taught SQL Server for 7 years.
I base my book recommendations on content, ease of readability and
relevancy. I do own Joe's 1999 edition. In fact I was just going through
it when I stopped by the book store and happend to notice his 2005 edition.
I was impressed with the additional content (coverage and examples). In
fact the book has increased in size by over 250 pages. While personally I
believe Ken and Kalen's books are the two best SQL Server books on the
market I feel Joe's book is one of the top SQL books on the market.
HTH
Jerry
"Andrew Watt [MVP - InfoPath]" <SVGDeveloper@.aol.com> wrote in message
news:7mask1toptlh9gsqqmbqr5vrg9vmpmaun0@.
4ax.com...
> On Wed, 12 Oct 2005 19:15:24 -0700, "Jerry Spivey"
> <jspivey@.vestas-awt.com> wrote:
>
> Jerry,
> A basic question or two.
> If you don't have the book already in your library how can you be sure
> it's a job well done?
> What do you think its strengths are? How relevant, for example, is
> (what seems to be) a generic SQL book to a T-SQL context?
> I am not sniping simply asking for clarification to better understand
> the basis for your assessment.
> Thanks.
> Andrew Watt
> MVP - InfoPath
CE Compatibility with ADO.NET and Orcas
Does SQL Server Compact Edition fully support ADO.NET?
Will SQL Server Compact Edition fully support the ADO.NET Entity Framework?
Will SQL Server Compact Edition fully support LINQ?
1. I don't know what you would consider "fully support" but there's special SQL CE ADO.Net managed provider for both desktop and devices. It has pretty much all classes SQL Client has (with few nonessential exceptions) and even something extra (like SqlCeResultSet).
2. Don't know about desktop but there's no EF support on devices. EF on desktop is extensible, even if not supported out of the box support might be available later on.
3. Again, not sure what you mean by that. As name implies LINQ is integrated into programming languages, not into databases. If you’re asking if you’ll be able to query SQL CE database from C# or VB using, say, EF and LINQ then see #2.
Tuesday, February 14, 2012
Catalogue Report Manager is not installing
Hello!
I installed SQL Server 2005 Express Edition with Advanced Services with Service Pack 2 but catalogue Report Manager it was not installed. To me will not address under the reference http: // localhost/reports$SQLExpress since such catalogue is not present in IIS. In what there can be a problem?
Thank's
Hi,are you sure that Reporting Services is installed ? You will need to have IIS as a prerequisite before installing Reporting Services, otherwise it wwon′t be installed.
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de|||
yes, but I have't installed Report Manager 
.
Thank's for help!!
Subscribe to:
Posts (Atom)