Migraton from Enterprise to Standard

Hi
I wan to migrate an SQL Enterprise server system to SQL Standard system.
Can somebody guide me throgh the process?
Thanks
KNDHi,
Is it a SQL2000? If so, refer:
'INF: Effects of Moving a Database from SQL 2000 Enterprise Edition to SQL
2000 Standard Edition'
http://support.microsoft.com/default.aspx?id=268361
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"KND" <anonymous@.discussions.microsoft.com> wrote in message
news:52E54DFE-58E4-4D2B-93AB-49A9CA083F03@.microsoft.com...
> Hi
> I wan to migrate an SQL Enterprise server system to SQL Standard system.
> Can somebody guide me throgh the process?
> Thanks
> KND

Migraton from Enterprise to Standard

Hi
I wan to migrate an SQL Enterprise server system to SQL Standard system.
Can somebody guide me throgh the process?
Thanks
KND
Hi,
Is it a SQL2000? If so, refer:
'INF: Effects of Moving a Database from SQL 2000 Enterprise Edition to SQL
2000 Standard Edition'
http://support.microsoft.com/default.aspx?id=268361
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"KND" <anonymous@.discussions.microsoft.com> wrote in message
news:52E54DFE-58E4-4D2B-93AB-49A9CA083F03@.microsoft.com...
> Hi
> I wan to migrate an SQL Enterprise server system to SQL Standard system.
> Can somebody guide me throgh the process?
> Thanks
> KND

Migraton from Enterprise to Standard

H
I wan to migrate an SQL Enterprise server system to SQL Standard system
Can somebody guide me throgh the process
Thank
KNDHi,
Is it a SQL2000? If so, refer:
'INF: Effects of Moving a Database from SQL 2000 Enterprise Edition to SQL
2000 Standard Edition'
http://support.microsoft.com/default.aspx?id=268361
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"KND" <anonymous@.discussions.microsoft.com> wrote in message
news:52E54DFE-58E4-4D2B-93AB-49A9CA083F03@.microsoft.com...
> Hi
> I wan to migrate an SQL Enterprise server system to SQL Standard system.
> Can somebody guide me throgh the process?
> Thanks
> KND

Migration: SQL Server 7.0 - SQL Server 2000

I have to migrate my SQL Server 7 databases to SQL Server 2000.
What I was planning to do was to restore my full 7.0 backup to my new SQL Server 2000 system. This looks to good to be
true so......... Is there a problem with this plan? What are the "gotchas"? What should I look-out for? Is there
a better way of doing this migration.
I've only been a DBA for about a year so I can definitely use all the help I can get. Any ideas, help, suggestions are
greatly appreciated.
tx.
cathy
"Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in message
news:p35jl0ho08595bk909et8eikvamehb889a@.4ax.com...
> I have to migrate my SQL Server 7 databases to SQL Server 2000.
> What I was planning to do was to restore my full 7.0 backup to my new SQL
Server 2000 system. This looks to good to be
> true so......... Is there a problem with this plan? What are the
"gotchas"? What should I look-out for? Is there
> a better way of doing this migration.
That's an excellent way to perform your upgrade.

> I've only been a DBA for about a year so I can definitely use all the help
I can get. Any ideas, help, suggestions are
> greatly appreciated.
Planning is a key part of any DBA's job, so you are on target. If you have
not seen the following links, have a read ;)
How to Upgrade SQL Server 6.5 and 7.0 to SQL Server 2000
http://www.microsoft.com/technet/pro...y/sqlugrd.mspx
Upgrading an Existing Installation of SQL Server
http://msdn.microsoft.com/library/de...rview_2xtf.asp
Steve
|||... and some other links that might be useful:
Moving SQL Server Databases
http://www.support.microsoft.com/?id=224071
Moving Databases between Servers
http://www.support.microsoft.com/?id=314546
Using WITH MOVE in a Restore to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465
How To Transfer Logins and Passwords Between SQL Servers
http://www.support.microsoft.com/?id=246133
Mapping Logins & SIDs after a Restore
http://www.support.microsoft.com/?id=298897
Utility to map users to the correct login
http://www.dbmaint.com/SyncSqlLogins.asp
How to Resolve Permission Issues When a Database Is Moved Between SQL Servers
http://www.support.microsoft.com/?id=240872
User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=168001
Disaster Recovery Articles for SQL Server
http://www.support.microsoft.com/?id=307775
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Steve Thompson" <stevethompson@.nomail.please> wrote in message
news:%23zStb4XpEHA.324@.TK2MSFTNGP11.phx.gbl...
> "Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in message
> news:p35jl0ho08595bk909et8eikvamehb889a@.4ax.com...
> Server 2000 system. This looks to good to be
> "gotchas"? What should I look-out for? Is there
> That's an excellent way to perform your upgrade.
> I can get. Any ideas, help, suggestions are
> Planning is a key part of any DBA's job, so you are on target. If you have
> not seen the following links, have a read ;)
> How to Upgrade SQL Server 6.5 and 7.0 to SQL Server 2000
> http://www.microsoft.com/technet/pro...y/sqlugrd.mspx
> Upgrading an Existing Installation of SQL Server
> http://msdn.microsoft.com/library/de...rview_2xtf.asp
> Steve
>
|||Thanks Steve & Tibor. The links are definitely helpful. I always get a
case of the "warm fuzzies" when I have someone with lots of experience
validating my decisions & plans.
cathy
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uVdec5XpEHA.516@.TK2MSFTNGP09.phx.gbl...
> ... and some other links that might be useful:
>
> Moving SQL Server Databases
> http://www.support.microsoft.com/?id=224071
> Moving Databases between Servers
> http://www.support.microsoft.com/?id=314546
> Using WITH MOVE in a Restore to a New Location with Detach/Attach
> http://support.microsoft.com/?id=221465
> How To Transfer Logins and Passwords Between SQL Servers
> http://www.support.microsoft.com/?id=246133
> Mapping Logins & SIDs after a Restore
> http://www.support.microsoft.com/?id=298897
> Utility to map users to the correct login
> http://www.dbmaint.com/SyncSqlLogins.asp
> How to Resolve Permission Issues When a Database Is Moved Between SQL
Servers[vbcol=seagreen]
> http://www.support.microsoft.com/?id=240872
> User Logon and/or Permission Errors After Restoring Dump
> http://www.support.microsoft.com/?id=168001
> Disaster Recovery Articles for SQL Server
> http://www.support.microsoft.com/?id=307775
>
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Steve Thompson" <stevethompson@.nomail.please> wrote in message
> news:%23zStb4XpEHA.324@.TK2MSFTNGP11.phx.gbl...
message[vbcol=seagreen]
SQL[vbcol=seagreen]
help[vbcol=seagreen]
have[vbcol=seagreen]
http://www.microsoft.com/technet/pro...y/sqlugrd.mspx[vbcol=seagreen]
http://msdn.microsoft.com/library/de...rview_2xtf.asp
>

Migration: SQL Server 7.0 - SQL Server 2000

I have to migrate my SQL Server 7 databases to SQL Server 2000.
What I was planning to do was to restore my full 7.0 backup to my new SQL Server 2000 system. This looks to good to be
true so......... Is there a problem with this plan? What are the "gotchas"? What should I look-out for? Is there
a better way of doing this migration.
I've only been a DBA for about a year so I can definitely use all the help I can get. Any ideas, help, suggestions are
greatly appreciated.
tx.
cathy"Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in message
news:p35jl0ho08595bk909et8eikvamehb889a@.4ax.com...
> I have to migrate my SQL Server 7 databases to SQL Server 2000.
> What I was planning to do was to restore my full 7.0 backup to my new SQL
Server 2000 system. This looks to good to be
> true so......... Is there a problem with this plan? What are the
"gotchas"? What should I look-out for? Is there
> a better way of doing this migration.
That's an excellent way to perform your upgrade.
> I've only been a DBA for about a year so I can definitely use all the help
I can get. Any ideas, help, suggestions are
> greatly appreciated.
Planning is a key part of any DBA's job, so you are on target. If you have
not seen the following links, have a read ;)
How to Upgrade SQL Server 6.5 and 7.0 to SQL Server 2000
http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/sqlugrd.mspx
Upgrading an Existing Installation of SQL Server
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/instsql/in_overview_2xtf.asp
Steve|||... and some other links that might be useful:
Moving SQL Server Databases
http://www.support.microsoft.com/?id=224071
Moving Databases between Servers
http://www.support.microsoft.com/?id=314546
Using WITH MOVE in a Restore to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465
How To Transfer Logins and Passwords Between SQL Servers
http://www.support.microsoft.com/?id=246133
Mapping Logins & SIDs after a Restore
http://www.support.microsoft.com/?id=298897
Utility to map users to the correct login
http://www.dbmaint.com/SyncSqlLogins.asp
How to Resolve Permission Issues When a Database Is Moved Between SQL Servers
http://www.support.microsoft.com/?id=240872
User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=168001
Disaster Recovery Articles for SQL Server
http://www.support.microsoft.com/?id=307775
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Steve Thompson" <stevethompson@.nomail.please> wrote in message
news:%23zStb4XpEHA.324@.TK2MSFTNGP11.phx.gbl...
> "Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in message
> news:p35jl0ho08595bk909et8eikvamehb889a@.4ax.com...
>> I have to migrate my SQL Server 7 databases to SQL Server 2000.
>> What I was planning to do was to restore my full 7.0 backup to my new SQL
> Server 2000 system. This looks to good to be
>> true so......... Is there a problem with this plan? What are the
> "gotchas"? What should I look-out for? Is there
>> a better way of doing this migration.
> That's an excellent way to perform your upgrade.
>> I've only been a DBA for about a year so I can definitely use all the help
> I can get. Any ideas, help, suggestions are
>> greatly appreciated.
> Planning is a key part of any DBA's job, so you are on target. If you have
> not seen the following links, have a read ;)
> How to Upgrade SQL Server 6.5 and 7.0 to SQL Server 2000
> http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/sqlugrd.mspx
> Upgrading an Existing Installation of SQL Server
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/instsql/in_overview_2xtf.asp
> Steve
>|||Thanks Steve & Tibor. The links are definitely helpful. I always get a
case of the "warm fuzzies" when I have someone with lots of experience
validating my decisions & plans.
cathy
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uVdec5XpEHA.516@.TK2MSFTNGP09.phx.gbl...
> ... and some other links that might be useful:
>
> Moving SQL Server Databases
> http://www.support.microsoft.com/?id=224071
> Moving Databases between Servers
> http://www.support.microsoft.com/?id=314546
> Using WITH MOVE in a Restore to a New Location with Detach/Attach
> http://support.microsoft.com/?id=221465
> How To Transfer Logins and Passwords Between SQL Servers
> http://www.support.microsoft.com/?id=246133
> Mapping Logins & SIDs after a Restore
> http://www.support.microsoft.com/?id=298897
> Utility to map users to the correct login
> http://www.dbmaint.com/SyncSqlLogins.asp
> How to Resolve Permission Issues When a Database Is Moved Between SQL
Servers
> http://www.support.microsoft.com/?id=240872
> User Logon and/or Permission Errors After Restoring Dump
> http://www.support.microsoft.com/?id=168001
> Disaster Recovery Articles for SQL Server
> http://www.support.microsoft.com/?id=307775
>
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Steve Thompson" <stevethompson@.nomail.please> wrote in message
> news:%23zStb4XpEHA.324@.TK2MSFTNGP11.phx.gbl...
> > "Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in
message
> > news:p35jl0ho08595bk909et8eikvamehb889a@.4ax.com...
> >> I have to migrate my SQL Server 7 databases to SQL Server 2000.
> >> What I was planning to do was to restore my full 7.0 backup to my new
SQL
> > Server 2000 system. This looks to good to be
> >> true so......... Is there a problem with this plan? What are the
> > "gotchas"? What should I look-out for? Is there
> >> a better way of doing this migration.
> >
> > That's an excellent way to perform your upgrade.
> >
> >> I've only been a DBA for about a year so I can definitely use all the
help
> > I can get. Any ideas, help, suggestions are
> >> greatly appreciated.
> >
> > Planning is a key part of any DBA's job, so you are on target. If you
have
> > not seen the following links, have a read ;)
> >
> > How to Upgrade SQL Server 6.5 and 7.0 to SQL Server 2000
> >
http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/sqlugrd.mspx
> >
> > Upgrading an Existing Installation of SQL Server
> >
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/instsql/in_overview_2xtf.asp
> >
> > Steve
> >
> >
>

Migration Wizard Error

When I attempt to migrate any AS2000 database to AS2005, I get an error during the "Validating Databases" step, during the Cube validation, as follows:

Unable to cast COM object of type 'System.__ComObject' to interface type 'Interop.Dso.IPartition90Ex'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{F82195C2-53A0-41B5-B7D8-7D087BAE32CF}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).

Needless to say, this prevents me from performing the migration. I have even created a super-simple cube with one dimension, and I still get the same error. I have tried this using 3 different source servers. Any suggestions on where to look? I'm running SSMS and Analysis Manager on a workstation, not the server itself.

Gary

This could be related to the order you installed your components. Try uninstalling and re-installing SQL Server 2005 components on your workstation.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||Thank you. I uninstalled and re-installed SQL Server 2005 on the workstation and that solved the problem.

Migration VFP to MS SQL Server 2000

Dear Friends,
I am about to migrate a Visual FoX Pro 7.0 & 5.0 databases to MS SQL
Server 2000. I would like to
share the experience with you, if you have undergone such a task. Is
there any utility for achieving
this.
Any white paper or link for guidance on the same.
I wannted to migrate the whole database to MS SQL Server 2000. I wanted
to migrate the table
structures and procedures to MS SQL Server 2000.
Please shed some light please.
Regards
Kumar
--
Posted via http://dbforums.comFoxPro 7 includes an Upsizing Wizard that will move your schema and data
into SQLServer. I believe this wizard was also in 5.
However, I suggest you take the opportunity to redesign your database in SQL
rather than just rely on the Wizard. Your database will probably need design
changes to take best advantage of the SQL platform. When you have designed
your SQL schema you can use SQLServer DTS to help transform the data from
FoxPro to SQL.
Your code will certainly need re-writing. The syntax and behaviour of SQL
statements in FoxPro (SELECT, INSERT, UPDATE, DELETE) are quite different to
Transact-SQL. I don?t know of any tools to help with this process.
--
David Portas
--
Please reply only to the newsgroup
--|||In news:3561073.1068013648@.dbforums.com,
sgnerd <member23530@.dbforums.com> posted:
> Dear Friends,
> I am about to migrate a Visual FoX Pro 7.0 & 5.0 databases to MS SQL
Server 2000. I would like to share the experience with you, if you have
undergone such a task. Is there any utility for achieving this. Any white
paper or link for guidance on the same.
> I wannted to migrate the whole database to MS SQL Server 2000. I wanted to
migrate the table structures and procedures to MS SQL Server 2000.
Hi Kumar,
If you have Visual FoxPro available there's an Upsizing Wizard that will do
what you want. For more information try
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/fox7help/html/dgUpsizing_Visual_FoxPro_Databases.asp .
--
Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy.winegarden@.mvps.org, www.cindywinegarden.com

Migration to SQL Server 2k5

Hi all,

I have script written in SQL Server 2000.

When i tried to migrate to SQL Server 2005, it is working fine in the SQL Server 2005 installed in Windows 2003 Server. System tables(syscolumns, sysobjects etc)are created in "Database->Tables->SystemTable".

But when i tried to run in SQL Server 2005 installed in Windows XP, I'm facing the following problems.

1."The object 'CK_SavedSear_LastL_4B422AD5' is dependent on column'LastLoadedTime'

"ALTER TABLE DROP COLUMN LastLoadedTime failed because one or more objects access this column"

2.Moreover none of the tables had been created in "Database->Tables->SystemTable".

In both XP and 2003 Server, While installing, i have choosen same options.

Please anybody could help me to resolve this issue.

Thanks and Regards,

Nilavu

You should try a different forum: http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=93&SiteID=1

-Jamie

Migration to SQL Server 2k5

Hi all,

I have script written in SQL Server 2000.

When i tried to migrate to SQL Server 2005, it is working fine in the SQL Server 2005 installed in Windows 2003 Server. System tables(syscolumns, sysobjects etc)are created in "Database->Tables->SystemTable".

But when i tried to run in SQL Server 2005 installed in Windows XP, I'm facing the following problems.

1."The object 'CK_SavedSear_LastL_4B422AD5' is dependent on column'LastLoadedTime'

"ALTER TABLE DROP COLUMN LastLoadedTime failed because one or more objects access this column"

2.Moreover none of the tables had been created in "Database->Tables->SystemTable".

In both XP and 2003 Server, While installing, i have choosen same options.

Please anybody could help me to resolve this issue.

Thanks and Regards,

Nilavu

Can you give detailed steps on what exactly you're doing, it's unclear to me what you mean by "migrate". Are you running setup/upgrade, which is failing?|||

Hi,

First i have to thank you for the valuable efforts.

Problem is not with upgrade/Setup of SQL Server 2005, With scripts. Whether the scripts written in SQL Server 2000 will run in SQL Server 2005 without doing any modification .

Here is the scenario.

Actually i have scripts that are written for SQL Server 2000.

Now my clients are using SQL Server 2005.

So i have to test whether my scripts could run in SQL Server 2005 without any modification.

When i tried to run the scripts in SQL Server 2005 installed in Windows XP OS, it is giving error.

At the same time there are no tables created in "Database->Tables->SystemTable".

But Same script is executed properly in SQL Server 2005 installed in Windows 2003 Server.

In this case tables like "sysobjects" etc are created in "Database->Tables->SystemTable".

Still you are not able to understand, Please send me mail.

Please suggest me whether i have to do any changes in script level or in settings of SQL Server 2005.

Moreover Being installed SQL Server 2005, Why tables like "Sysobjects" have been created in 2003 Server OS while not in XP.

Kindly clarify my doubts.

Thanks and Regards,

Nilavu

|||I don't think this has anything to do with sql server on a given OS. If you look at the error message closely, it says the alter table drop column failed because a check constraint exists. You have to drop the check constraint first before you can drop the column.|||

Hi,

Yes Greg, you are right, i'm getting the same error message.

But the problem is, the same scripts works fine in ,

1.Windows XP, SQL Server 2000

2.Windows 2003 Server, SQL Server 2005

But i'm getting error in Windows XP, SQL Server 2005.

Thats what i could not find the solution.

I would like to mention one more different behaviour in SQL Server 2005,

In Windows 2003 Server, SQL Server 2005, "Tables->SystemTables" system tables like "sysobjects" are created.

But in Windows XP, SQL Server 2005, There are no such tables in "Tables->SystemTables".

Could you explain me why it is behaving in two different ways?

Thanks and Regards,

Nilavu.

|||

Look at the error message closely, it says a check constraint exists. You cannot drop a column if a check constraint exists on that column. Please check to see if this check constraint exists in both databases, as well as whether your script is explicitly dropping this constraint. If your script is explicitly dropping this constriant, maybe the script is failing beforehand. If your script is not dropping this constraint, then your databases are not exactly in sync, which is why it is failing on one db and not the other.

|||

Hi,

Thanks Greg.

Before dropping the column, code which is trying to find check constraint fails.

The "info" column in the "sysobjects" table contains only zero values for all objects in case of SQL Server 2005.

But in case of SQL Server 2000, there are certain values have entered.

Could you tell me, Where are the "info" column's values are mapped? Which table and column i have to refer instead of "sysobjects->info".

Here is my code,

IF ((SELECT COUNT(sysobjectsconstraint.id) FROM syscolumns

INNER JOIN sysobjects AS sysobjectstable ON syscolumns.id = sysobjectstable.id

INNER JOIN sysobjects AS sysobjectsconstraint ON syscolumns.id = sysobjectsconstraint.parent_obj

AND sysobjectsconstraint.info = syscolumns.colid AND sysobjectsconstraint.xtype = 'C'

WHERE syscolumns.name = 'RemoveFromSyncTime'

AND sysobjectstable.xtype = 'U' AND sysobjectstable.category & 2 <> 2

AND sysobjectstable.NAME = 'SavedSearchLoadScheduleItem') = 1)

BEGIN

SET @.sqlcommand = (

SELECT 'ALTER TABLE ' +

QUOTENAME(USER_NAME(sysobjectstable.uid)) + '.' +

QUOTENAME(sysobjectstable.name) +

' DROP CONSTRAINT ' +

QUOTENAME(sysobjectsconstraint.name)

FROM syscolumns

INNER JOIN sysobjects AS sysobjectstable ON syscolumns.id = sysobjectstable.id

INNER JOIN sysobjects AS sysobjectsconstraint ON syscolumns.id = sysobjectsconstraint.parent_obj

AND sysobjectsconstraint.info = syscolumns.colid AND sysobjectsconstraint.xtype = 'C'

WHERE syscolumns.name = 'RemoveFromSyncTime'

AND sysobjectstable.xtype = 'U' AND sysobjectstable.category & 2 <> 2

AND sysobjectstable.NAME = 'SavedSearchLoadScheduleItem'

)

The "If" condition fails in case of SQLServer 2005, whereas in case of SQLServer 2000, i'm getting value of 1.

Thanks and Regards,

Nilavu.

|||Moving to TSQL forum, someone more familiar with metadata and system tables can offer a better answer.|||The issue is that you are using columns reserved for internal use in your query. So any assumptions made as to what values it can contain will be wrong in SQL Server 2005. It might even break in SQL Server 2000 with a future service pack for example. You can determine CHECK constraints on a table by using INFORMATION_SCHEMA.CHECK_CONSTRAINTS view along with INFORMATION_SCHEMA.CONSTRAINT_COLUMN_USAGE view. Or just the INFORMATION_SCHEMA.CONSTRAINT_COLUMN_USAGE view with OBJECTPROPERTYEX metadata function to filter check constraints. This will work the same in SQL Server 2000/2005. Or you could use sp_helpconstraint system SP for example. It is best to use the documented objects so that your code works consistently and you don't rely on undocumented interfaces that can be modified anytime by us.|||

Hi,

Thank you for your timely help Umachandar.

Its working fine now.

Regards,

Nilavu.

Migration to new servers

I have to migrate reports to two new servers. I tried simply moving the
databases over, but RS freaked. rsactivate and the other utilities are
problematic, to say the least (I freaked).
It seems like the easiest thing would be to install SQL RS on the new
servers, copy over all of the project files/reports, and then from within VS,
reset the project properties to the new server and redeploy.
Does this make sense? Is there an easier, or more reliable way?
--
Thanks,
CGWYou are correct. easiest is to install RS on new servers and then to the new
RS URL, you can just post your reports directly from Visual studio, or
however you deploy your reports today. This is the cleanest way to deploy as
well.
"CGW" wrote:
> I have to migrate reports to two new servers. I tried simply moving the
> databases over, but RS freaked. rsactivate and the other utilities are
> problematic, to say the least (I freaked).
> It seems like the easiest thing would be to install SQL RS on the new
> servers, copy over all of the project files/reports, and then from within VS,
> reset the project properties to the new server and redeploy.
> Does this make sense? Is there an easier, or more reliable way?
> --
> Thanks,
> CGW|||Thank you!
CGW
"Ram" wrote:
> You are correct. easiest is to install RS on new servers and then to the new
> RS URL, you can just post your reports directly from Visual studio, or
> however you deploy your reports today. This is the cleanest way to deploy as
> well.
> "CGW" wrote:
> > I have to migrate reports to two new servers. I tried simply moving the
> > databases over, but RS freaked. rsactivate and the other utilities are
> > problematic, to say the least (I freaked).
> >
> > It seems like the easiest thing would be to install SQL RS on the new
> > servers, copy over all of the project files/reports, and then from within VS,
> > reset the project properties to the new server and redeploy.
> >
> > Does this make sense? Is there an easier, or more reliable way?
> > --
> > Thanks,
> >
> > CGW

Migration to new cluster enviroment

My production system is on stand alone Server and it is a publisher on the
replication system. I need to Migrate to a new hardware with fail over
cluster and upgrade to SQL 2005 .
I need to do that with out impacting replication. What is my options? Can I
do that Or not
If this was to stand alone new hardware I will have no issue.
Thanks for your help
You can't do it without any impact to replication, but you should be able to
with minimal impact.
Build out your new system and test thoroughly. Once you are confident that
the new system performs adequately, then drop your publication on the
production database and copy it (several options here for you) to the new
system.
You will have to redirect your clients to the new host name and reestablish
replication publication.
This should be doable during a reasonable off hours maintenance window.
Sincerely,
Anthony Thomas

<msnews.microsoft.com> wrote in message
news:ek7ECL6THHA.1552@.TK2MSFTNGP05.phx.gbl...
> My production system is on stand alone Server and it is a publisher on the
> replication system. I need to Migrate to a new hardware with fail over
> cluster and upgrade to SQL 2005 .
> I need to do that with out impacting replication. What is my options? Can
I
> do that Or not
> If this was to stand alone new hardware I will have no issue.
> Thanks for your help
>

Migration to ms-sql

Hi,
Does any one aware of any tool for sybase to ms-sql migration, which will migrate store procedures/triggers from sybase to ms-sql server 2000.
Thanks
Vaishalinever done it, some googling came out with many results
sqlporter (http://www.realsoftstudio.com/overview.php) sounds impressive though. :cool:|||Hi Vaishali,

I came across the Migration tool that which doing fine in database migration. Which u needs fulfill the requirement. Yes. Plz. visit the www.swissql.com.

Regards
Saravanan.R|||Thanks Saravanan & Harshal!
Saravanan,
Does it migrate all the objects without any problem. I have visited this site. Is there a trial version available for this. I could not get any.

migration tips

is there any materials online

for migrating to 2005 rs.

is it necessary to migrate the reportserver db to 2005 also?

Hey joeydj, nice to see you here. You might want to take the MOC 7031. You can also check out http://www.microsoft.com/technet/prodtechnol/sql/2005/technologies/rptsvcs.mspx for other resources which might be of use to you|||thanks for the link

Migration Task

Hi guys.

I have a hard task to solve. I need to migrate 3 databases from an old SQL 6.0 (yes, it still exists!) to a new SQL 2000. These 3 dbs contain only tables and stores procedures. The sizes are:

DB_INews : 6.0GB
DB_Balanco : 600MB
DB_Invest : 100MB

I think I will have problems with DB_INEWS, because it contains tables with 2 million lines.

What is the best option to do this migration?

Cheers,

FabianoIF the databases are in SQL 6.0 version the only way is to upgrade it to 6.5 version and then choose UPGRADE WIZARD from 6.5 to SQL 2000. There is no other go to migrate data directly.

Migration SQLSERVER DB from one server to another Server

Hello,
How to migrate SQLSERVER DB from one server to another Server?
We are planning from Compaq server to Dell and vice versa?
Thx.
-SeenaBackup all databases from one server and restore on the other.
I think BOL has info on how to do this for system databases - if not just do a search.

Also look at detach/attach.

Worth reading up about system databases first.|||Hello,
It is the same as the other member of dBforums explained to you. It is so simple, you need only to backup the database. If you are using MS SQL Server 2000, you'll have to choose the database:
- right click
- all tasks
- backup database
- choose the device to which you want to copy (tape/disk)

Then on the other PC, create these databases manually and:
-choose the newly created DB
-right click
-all tasks
-restore database
-choose the source

Otherwise, you can use the DTS service which is available in SQL Server 2000.

it is so simple to use.

Take cares & good luck!

Alzebdeh
Originally posted by sqlserverdb
Hello,
How to migrate SQLSERVER DB from one server to another Server?
We are planning from Compaq server to Dell and vice versa?
Thx.
-Seena|||The easiest, if you have both computer on-line, is to Detach the databases
and copy the MDF and LDF files into the new server, then attach those files
into new SQl.

"Alzebdeh" wrote in message
news:2441325.1043640789@.dbforums.com...
> Hello,
> It is the same as the other member of dBforums explained to you. It is
> so simple, you need only to backup the database. If you are using MS SQL
> Server 2000, you'll have to choose the database:
> - right click
> - all tasks
> - backup database
> - choose the device to which you want to copy (tape/disk)
> Then on the other PC, create these databases manually and:
> -choose the newly created DB
> -right click
> -all tasks
> -restore database
> -choose the source
> Otherwise, you can use the DTS service which is available in SQL
> Server 2000.
> it is so simple to use.
> Take cares & good luck!
> Alzebdeh
> Originally posted by sqlserverdb
> > Hello,
> > How to migrate SQLSERVER DB from one server to another Server?
> > We are planning from Compaq server to Dell and vice versa?
> > Thx.
> -Seena
> --
> Posted via http://dbforums.com (http://dbforums.com/)

Migration replication jobs

Hi all,
I will be migrating a production database to a new box. I will be using
detach and attach db method to migrate, but I forsee that my replication job
will break. Can anyone advise me on how to migrate the replication jobs over
to the new db? Here is the sencario:
DB-1 in Box A detach and move over to Box B to be reattached,
DB-1 in Box A has some publications and subscriptions, and the distribution
is in Box C.
Let say Box B will resume the ip of Box A but different hostname.
You will be unable to detach replicated databases. You have to script out
the publications, edit them for the new server, remove all job names, and
then drop the publications, unpublish the databases and detach them. Attach
them on the new server, run the publication script and do a non sync.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"YK" <YK@.discussions.microsoft.com> wrote in message
news:25A6D0F1-6C2C-4B95-84F5-C96B963335D0@.microsoft.com...
> Hi all,
> I will be migrating a production database to a new box. I will be using
> detach and attach db method to migrate, but I forsee that my replication
job
> will break. Can anyone advise me on how to migrate the replication jobs
over
> to the new db? Here is the sencario:
> DB-1 in Box A detach and move over to Box B to be reattached,
> DB-1 in Box A has some publications and subscriptions, and the
distribution
> is in Box C.
> Let say Box B will resume the ip of Box A but different hostname.
>

Migration Problem with NS SQL 2000 to NS SQL 2005

Hello,

I'm traying to migrate a Notification service solution from SQL Server 2000 to SQL Server 2005. The solution works fine on SQL Server 2000, but on 2005 I allways get the message: "The registry entries for the specified instance of Notification Services could not be found". This message shows up everytime when i want to see the Subscriptions of a given Subscriber in my Web-Interface (written in ASP and C#) or when I want to add a new Subscription. News of a existing Subscription are shown without a problem.

So far I know i did follow all the steps to migrate the Database, Application and NS-Instance.

First I upgrated the DB-Files in SQL 2000 to SQL 2005. (Only the DB-file for user and admin Login for the Web-Inteface) Then i attached the DB file on the SQL 2005 server. So far everything works fine and users can log in. Then I edited the ADF-File and chaged all the NOTIFY syntax to INSERT INTO and changed all the paths to the new server-environement. In the Management Studio of SQL 2005 I created a new NS-Instance with the adapted ADF-file and the service is running without problems. At the end I recompiled all the ASP and C# scripts in Visual Studio 2005 with the assemblies of .NET 2.0 and SQL Server 2005.

Does anybody knows why the entries of this existing and running instance in the registry can't be found? The name of the instance is right and is in the registry.

Can anybody help ?

From my replies to your newsgroup posting....

Have you checked with the depreciated features pages of BOL to make
sure your C# code isn't making use of the old way of doing things?
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/c4612650-eaa9-443a-a4ef-95d9feaf4976.htm
Can you post the code that's failing?

By the way, I have an article on Simple-Talk.com about upgrading
to SQLNS 2005 from 2000.

http://www.simple-talk.com/2006/04/10/building-effective-sql-server-notification-applications-part-i/
or

http://sqlns.blogspot.com/2006/04/upgrading-to-sqlns-2005-from-2000.html

|||I had the same problem and solved it by changing my reference in VS to point to newest version of microsoft.sqlserver.notification.dll (version 9.0.242.0) and recompile- hope this helps-

Migration of Teradata and DB2 Timestamp fields.

I am trying to migrate timestamp fields in Teradata and
DB2 to SQL server. The problem is that Teradata and DB2
store timestamps to an accuracy of 1 microsecond, while
SQL Server stores it to the nearest 3.33 milliseconds
(the datetime datatype). The original accuracy needs to
be preserved as the columns are part of the primary key.
Is there an equivalent datatype in SQL Server or a quick
workaround for this problem? Date / Time functions need
to be performed on these columns.
There is no datatype in SQL Server that has a precision of 1 millisecond. I
can suggest 3 different workarounds:
- Store the timestamp in a CHAR(23) column in format
yyyy-mm-ddThh:mi:ss.nnn. You CONVERT this to and from datetime with style
126. Note that the precision will go back to 3.33 milliseconds when you
convert to datetime. This uses 23 bytes of storage.
- Store the timestamp as a UNIX timestamp (milliseconds since 1970-1-1) in a
BIGINT column. This uses 8 bytes of storage.
- Store the timestamp in 2 columns, one is a SMALLDATETIME (precision 1
minute), the second one is a INT, to store the number of milliseconds. This
uses 8 bytes of storage. (You can also use a SMALLINT if you want to save 2
bytes, but then you have to handle negative milliseconds.
Whichever is the most convenient of course depends on the calculations you
are going to do with it.
Jacco Schalkwijk
SQL Server MVP
"Arumugam" <arumugam@.optusnet.com.au> wrote in message
news:de3401c43bd6$5e60f870$a501280a@.phx.gbl...
> I am trying to migrate timestamp fields in Teradata and
> DB2 to SQL server. The problem is that Teradata and DB2
> store timestamps to an accuracy of 1 microsecond, while
> SQL Server stores it to the nearest 3.33 milliseconds
> (the datetime datatype). The original accuracy needs to
> be preserved as the columns are part of the primary key.
> Is there an equivalent datatype in SQL Server or a quick
> workaround for this problem? Date / Time functions need
> to be performed on these columns.

Migration of Teradata and DB2 Timestamp fields.

I am trying to migrate timestamp fields in Teradata and
DB2 to SQL server. The problem is that Teradata and DB2
store timestamps to an accuracy of 1 microsecond, while
SQL Server stores it to the nearest 3.33 milliseconds
(the datetime datatype). The original accuracy needs to
be preserved as the columns are part of the primary key.
Is there an equivalent datatype in SQL Server or a quick
workaround for this problem? Date / Time functions need
to be performed on these columns.There is no datatype in SQL Server that has a precision of 1 millisecond. I
can suggest 3 different workarounds:
- Store the timestamp in a CHAR(23) column in format
yyyy-mm-ddThh:mi:ss.nnn. You CONVERT this to and from datetime with style
126. Note that the precision will go back to 3.33 milliseconds when you
convert to datetime. This uses 23 bytes of storage.
- Store the timestamp as a UNIX timestamp (milliseconds since 1970-1-1) in a
BIGINT column. This uses 8 bytes of storage.
- Store the timestamp in 2 columns, one is a SMALLDATETIME (precision 1
minute), the second one is a INT, to store the number of milliseconds. This
uses 8 bytes of storage. (You can also use a SMALLINT if you want to save 2
bytes, but then you have to handle negative milliseconds.
Whichever is the most convenient of course depends on the calculations you
are going to do with it.
Jacco Schalkwijk
SQL Server MVP
"Arumugam" <arumugam@.optusnet.com.au> wrote in message
news:de3401c43bd6$5e60f870$a501280a@.phx.gbl...
> I am trying to migrate timestamp fields in Teradata and
> DB2 to SQL server. The problem is that Teradata and DB2
> store timestamps to an accuracy of 1 microsecond, while
> SQL Server stores it to the nearest 3.33 milliseconds
> (the datetime datatype). The original accuracy needs to
> be preserved as the columns are part of the primary key.
> Is there an equivalent datatype in SQL Server or a quick
> workaround for this problem? Date / Time functions need
> to be performed on these columns.

Migration of SQLServer user databases to another SQLServer

Guys,
I would like to migrate a number of user databases from one SQLSERVER (name:
LECOMMS02 - Windows NT - 5.0(2195), SQLServer 8.00.534(SP2)) to another (na
me: LEPIV01 - Windows NT - 5.0(2195), SQLServer 8.00.780(SP3)).
Please can you outline the steps involved and any pitfalls I should watch fo
r? I am new to SQLServer and this is live data. This needs completing today
as well!!
TIA, KenKen,
Have a look at:
INF: Moving SQL Server databases to a new location with Detach/Attach
http://support.microsoft.com/defaul...kb;EN-US;224071
Mark Allison, SQL Server MVP
Ken Jones wrote:

> Guys,
> I would like to migrate a number of user databases from one SQLSERVER (nam
e: LECOMMS02 - Windows NT - 5.0(2195), SQLServer 8.00.534(SP2)) to another (
name: LEPIV01 - Windows NT - 5.0(2195), SQLServer 8.00.780(SP3)).
> Please can you outline the steps involved and any pitfalls I should watch
for? I am new to SQLServer and this is live data. This needs completing toda
y as well!!
> TIA, Ken
>
Mark Allison, SQL Server MVP
http://www.allisonmitchell.com|||Hi,
Since you need to upgrade only the user databases you can do one of the
folowing
1. Detach and Attach databases
2. Backup and Restore the databases
1. Detach and Attach
a. Use SP_DETACH_DB to detach the MDF and LDF files
b. Copy the files to Destination server
c. Use SP_ATTACH_DB to attach the databases
(Refer books online for information)
2. Backup and Restore
a. Backup the source databases using BACKUP DATABASE command
b. Copy the .BAK files to destination
c. Restore the database using RESTORE DATABASE command
After this steps you may need to move the logins from source server to
destination server.
Have a look into the below link for information.
http://www.databasejournal.com/feat...cle.php/2228611
Thanks
Hari
MCDBA
"Ken Jones" <anonymous@.discussions.microsoft.com> wrote in message
news:1442724A-12BF-4AF2-8A02-B558DCA60658@.microsoft.com...
> Guys,
> I would like to migrate a number of user databases from one SQLSERVER
(name: LECOMMS02 - Windows NT - 5.0(2195), SQLServer 8.00.534(SP2)) to
another (name: LEPIV01 - Windows NT - 5.0(2195), SQLServer 8.00.780(SP3)).
> Please can you outline the steps involved and any pitfalls I should watch
for? I am new to SQLServer and this is live data. This needs completing
today as well!!
> TIA, Ken
>|||Mark,
So I can detach (using sp_detach) from the source database, ftp to new serve
r and then attach (using sp_attach)'
Is that all there is to it? Will the sp_attach alert master as to the appear
ance of x number of new user databases as I am moving from one SQLServer (li
ve) to a completely different, functioning SQLServer(live)?
TIA, Ken.|||Thanks for your swift replies - WOW!!|||Hi Hari,
Some of my files are .DAT files. Will this affect the detach and attach proc
ess?
TIA, Ken|||DAT files could mean they are 6.5 database files. You can't move such across
to 7.0/2000. You need to have those databases available in a 6.5 install and
use the upgrade wizard from there.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Ken Jones" <anonymous@.discussions.microsoft.com> wrote in message
news:40772738-BE5B-4C98-86D9-DE1DB7959FFB@.microsoft.com...
> Hi Hari,
> Some of my files are .DAT files. Will this affect the detach and attach
process?
> TIA, Ken|||"I would like to migrate a number of user databases from one SQLSERVER (name
: LECOMMS02 - Windows NT - 5.0(2195), SQLServer 8.00.534(SP2)) to another (n
ame: LEPIV01 - Windows NT - 5.0(2195), SQLServer 8.00.780(SP3))."
Both are SQLServer8 servers. I am going to try the sp_detach_db and sp_attac
h_db by ftp'ing the LDF and MDF files. I'll see if this works.
Ken|||OK I just mentioned the 6.5 stuff because in 6.5 DAT were the default
extension for both database and backup files.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Ken Jones" <anonymous@.discussions.microsoft.com> wrote in message
news:63CF9224-D4BF-4550-AF7E-4B139C9C1E69@.microsoft.com...
> "I would like to migrate a number of user databases from one SQLSERVER
(name: LECOMMS02 - Windows NT - 5.0(2195), SQLServer 8.00.534(SP2)) to
another (name: LEPIV01 - Windows NT - 5.0(2195), SQLServer 8.00.780(SP3))."
> Both are SQLServer8 servers. I am going to try the sp_detach_db and
sp_attach_db by ftp'ing the LDF and MDF files. I'll see if this works.
> Ken