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
>
Showing posts with label planning. Show all posts
Showing posts with label planning. Show all posts
Monday, March 12, 2012
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
> >
> >
>
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
> >
> >
>
Friday, March 9, 2012
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/)
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 of Sql Server 7
Hi All,
Greetings,
We have
sql server 7
Sqlserver ServicePack SP3
Sort Order = 32
BuildNumber 7.00.961
on Windows NT,Now we are planning to upgrade operating system from win NT machine to windows 2000.
Please let me know what and all precausion do i need to take what and what all backup should be done apart from user database.
How do i take care of the users,logins,roles, DTS Job and Replication.
Please help me in this and also any links if u have on this topic
Waiting for reply
TIA
AdilWill you also be upgrading to SQL 2000 ?
When I moved to a new machine, we shut down SQL Server on both boxes, copied the database files to the new server and then started SQL Server. Because you are moving master you get all the login id's, etc. Just make sure you are running the same version of SQL server, otherwise it can get complicated.|||yes we are running the same version of SQL server.
pls suggest how do i go about it.
Thanks for ur reply
TIA
Adil
Greetings,
We have
sql server 7
Sqlserver ServicePack SP3
Sort Order = 32
BuildNumber 7.00.961
on Windows NT,Now we are planning to upgrade operating system from win NT machine to windows 2000.
Please let me know what and all precausion do i need to take what and what all backup should be done apart from user database.
How do i take care of the users,logins,roles, DTS Job and Replication.
Please help me in this and also any links if u have on this topic
Waiting for reply
TIA
AdilWill you also be upgrading to SQL 2000 ?
When I moved to a new machine, we shut down SQL Server on both boxes, copied the database files to the new server and then started SQL Server. Because you are moving master you get all the login id's, etc. Just make sure you are running the same version of SQL server, otherwise it can get complicated.|||yes we are running the same version of SQL server.
pls suggest how do i go about it.
Thanks for ur reply
TIA
Adil
Wednesday, March 7, 2012
migration from sybase to sql
Our company planning to migrate database server(Unix)
sybase 11.9.2 . This database are avaliable in tape(DAT).
I want to down load & convert to seq 7 or seq 2000
directly from tap to disk.
If I am using dump statment it is showing error msg.
Any one can solve this Issue.
Thanking U
r.varadharajanThe "SQL Server 2000 for the Sybase Customer Resource Kit" might help you -
check http://www.microsoft.com/sql/evaluation/compare/sybaseresourcekit.asp.
--
Dejan Sarka, SQL Server MVP
FAQ from Neil & others at: http://www.sqlserverfaq.com
Please reply only to the newsgroups.
PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Varadharajan" <rvrajanmdu@.hotmail.com> wrote in message
news:07f901c33f9d$6e8e49e0$a301280a@.phx.gbl...
> Our company planning to migrate database server(Unix)
> sybase 11.9.2 . This database are avaliable in tape(DAT).
> I want to down load & convert to seq 7 or seq 2000
> directly from tap to disk.
> If I am using dump statment it is showing error msg.
> Any one can solve this Issue.
> Thanking U
> r.varadharajan
>
sybase 11.9.2 . This database are avaliable in tape(DAT).
I want to down load & convert to seq 7 or seq 2000
directly from tap to disk.
If I am using dump statment it is showing error msg.
Any one can solve this Issue.
Thanking U
r.varadharajanThe "SQL Server 2000 for the Sybase Customer Resource Kit" might help you -
check http://www.microsoft.com/sql/evaluation/compare/sybaseresourcekit.asp.
--
Dejan Sarka, SQL Server MVP
FAQ from Neil & others at: http://www.sqlserverfaq.com
Please reply only to the newsgroups.
PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Varadharajan" <rvrajanmdu@.hotmail.com> wrote in message
news:07f901c33f9d$6e8e49e0$a301280a@.phx.gbl...
> Our company planning to migrate database server(Unix)
> sybase 11.9.2 . This database are avaliable in tape(DAT).
> I want to down load & convert to seq 7 or seq 2000
> directly from tap to disk.
> If I am using dump statment it is showing error msg.
> Any one can solve this Issue.
> Thanking U
> r.varadharajan
>
Migration from SQL Server 2000 to 2005
I have a fairly large web application that was built with SQL Server 2000 and .NET 1.1. We're planning on moving to .NET 2.0 eventually, but there's a lot of work to be done before that happens. In the short term, we're looking to purchase a new database server and would like to upgrade to SQL Server 2005 at the same time. Is it as simple as recreating our databases on this new system and changing the connection string, or are there other gotchas? As far as what we're doing with SQL Server 2000, it's really nothing more than tables, views, and stored procedures. Thanks in advance for any advice.
Before the migration, consider the following issues.
1. What is the Edition of SQL Server 2000?
2. What is the Edtiion of SQL Server 2005 you want to upgrade to?
3. What is the processor architecture? If it is IA64, then you must upgrade to 64-bit. If it is x64, then SQL Server 2000 has only 32-bit builds. At the same time, SQL Server 2005 has 64-bit builds. You cannot upgrade 32-bit SQL Server 2000 to 64-bit SQL Server 2005 directly.
4. What is the operating system running SQL Server 2000? If SQL Server 2005 editions requires a different operating system, is it acceptable to upgrad the operating system? For example, SQL Server 2005 Enterprise edition requires server operating systems such as Windows 2000 Advanced Server 2004, Windows Server 2003 Enterprise Edition SP1, and the coming Longhorn server.
5. Any special business and applicaiton logic?
Please also download the latest BOL from MSDN website for detailed information.
Once you decide to migrate, try side by side upgrade instead of in-site upgrade. SQL Server 2000 can be upgraded to SQL Server 2005 directly (if editions and processor architecture builds match). At the same time, SQL Server 2000 and SQL Server 2005 can be installed side by side successfully on the same machine if the resources allow. If resources allow, please follow the following recommendation.
1. Install SQL Server 2005 side by side with SQL Server 2000, i.e., not direct upgrade.
2. While SQL Server 2000 is still running, i.e., your application is still running, duplicate/copy data from SQL Server 2000 to SQL Server 2005.
3. Tune SQL Server 2005 and test SQL Server 2005.
4. When you think SQL Server 2005 is tested well and works well, switch to SQL Server 2005.
5. You may uninstall SQL Server 2000. This is optional.
Anyway, please back up your database before performing any major operations like this.
|||Well, luckily we'll be buying a new machine to eventually replace our existing database server. So we don't need to worry about actually "upgrading" anything currently in production. We'll just be migrating the actual databases to the new system.Our new system will be x64 running Windows Server 2003 and SQL Server 2005.
|||
Another great source of information in the Upgrade Portal
http://www.microsoft.com/sql/solutions/upgrade/default.mspx
This has pointer to lots of documents on Upgrading and it also points you to the Upgrade Advisor. If you run this tool against you SQL 2000 DB, SQL Batch Files and a SQL Trace file it can help determine if there is any potential incompatibilities.
Thanks
Michelle
Migration from SQL Server 2000 to 2005
I have a fairly large web application that was built with SQL Server 2000 and .NET 1.1. We're planning on moving to .NET 2.0 eventually, but there's a lot of work to be done before that happens. In the short term, we're looking to purchase a new database server and would like to upgrade to SQL Server 2005 at the same time. Is it as simple as recreating our databases on this new system and changing the connection string, or are there other gotchas? As far as what we're doing with SQL Server 2000, it's really nothing more than tables, views, and stored procedures. Thanks in advance for any advice.
Before the migration, consider the following issues.
1. What is the Edition of SQL Server 2000?
2. What is the Edtiion of SQL Server 2005 you want to upgrade to?
3. What is the processor architecture? If it is IA64, then you must upgrade to 64-bit. If it is x64, then SQL Server 2000 has only 32-bit builds. At the same time, SQL Server 2005 has 64-bit builds. You cannot upgrade 32-bit SQL Server 2000 to 64-bit SQL Server 2005 directly.
4. What is the operating system running SQL Server 2000? If SQL Server 2005 editions requires a different operating system, is it acceptable to upgrad the operating system? For example, SQL Server 2005 Enterprise edition requires server operating systems such as Windows 2000 Advanced Server 2004, Windows Server 2003 Enterprise Edition SP1, and the coming Longhorn server.
5. Any special business and applicaiton logic?
Please also download the latest BOL from MSDN website for detailed information.
Once you decide to migrate, try side by side upgrade instead of in-site upgrade. SQL Server 2000 can be upgraded to SQL Server 2005 directly (if editions and processor architecture builds match). At the same time, SQL Server 2000 and SQL Server 2005 can be installed side by side successfully on the same machine if the resources allow. If resources allow, please follow the following recommendation.
1. Install SQL Server 2005 side by side with SQL Server 2000, i.e., not direct upgrade.
2. While SQL Server 2000 is still running, i.e., your application is still running, duplicate/copy data from SQL Server 2000 to SQL Server 2005.
3. Tune SQL Server 2005 and test SQL Server 2005.
4. When you think SQL Server 2005 is tested well and works well, switch to SQL Server 2005.
5. You may uninstall SQL Server 2000. This is optional.
Anyway, please back up your database before performing any major operations like this.
|||Well, luckily we'll be buying a new machine to eventually replace our existing database server. So we don't need to worry about actually "upgrading" anything currently in production. We'll just be migrating the actual databases to the new system.Our new system will be x64 running Windows Server 2003 and SQL Server 2005.
|||
Another great source of information in the Upgrade Portal
http://www.microsoft.com/sql/solutions/upgrade/default.mspx
This has pointer to lots of documents on Upgrading and it also points you to the Upgrade Advisor. If you run this tool against you SQL 2000 DB, SQL Batch Files and a SQL Trace file it can help determine if there is any potential incompatibilities.
Thanks
Michelle
Monday, February 20, 2012
Migrating to SQL Server 2005 on same machine
I'm planning a migration from SQL Server 2000 to SQL Server 2005. To do thi
s
migration I have the contraint that I can't buy new machines. So I'm trying
to determine what options I have. First let me set the stage a little. For
a given SQL Server production machine I may have from 10-50
databases/application running. So I'm looking at the following options. Ar
e
there others? What are the risks of each of these. If you were me which wa
y
would you go, consider the constraint above.
Option 1: Upgrade In Place - This option would upgrade all database to from
SQL Server 2000 to SQL server 2005 at the same time by SQL Server machine.
Option 2: Run a named instance of SQL Server 2005 - This option would
install a named instance of SQL Server 2005 on the same machine that is
running the default instance of SQL Server 2000. Databases would be migrate
d
one at a time, or a handful at a time, until all database have been migrated
.
Once all databases have been migrated, SQL Server 2000 would be shutdown.
What are your opinions of how successful would each of these options be?
What are this risks of each option? Does running two instanances of
different versions of SQL Server cause any issue?If you have only one machine , I would recommend install SQL as a named
instance, and when you migrate all of the databases and test them
thouroughly you can stop SQL Server 2000.
Regards
Amish Shah
s
migration I have the contraint that I can't buy new machines. So I'm trying
to determine what options I have. First let me set the stage a little. For
a given SQL Server production machine I may have from 10-50
databases/application running. So I'm looking at the following options. Ar
e
there others? What are the risks of each of these. If you were me which wa
y
would you go, consider the constraint above.
Option 1: Upgrade In Place - This option would upgrade all database to from
SQL Server 2000 to SQL server 2005 at the same time by SQL Server machine.
Option 2: Run a named instance of SQL Server 2005 - This option would
install a named instance of SQL Server 2005 on the same machine that is
running the default instance of SQL Server 2000. Databases would be migrate
d
one at a time, or a handful at a time, until all database have been migrated
.
Once all databases have been migrated, SQL Server 2000 would be shutdown.
What are your opinions of how successful would each of these options be?
What are this risks of each option? Does running two instanances of
different versions of SQL Server cause any issue?If you have only one machine , I would recommend install SQL as a named
instance, and when you migrate all of the databases and test them
thouroughly you can stop SQL Server 2000.
Regards
Amish Shah
Migrating to SQL Server 2005 on same machine
I'm planning a migration from SQL Server 2000 to SQL Server 2005. To do this
migration I have the contraint that I can't buy new machines. So I'm trying
to determine what options I have. First let me set the stage a little. For
a given SQL Server production machine I may have from 10-50
databases/application running. So I'm looking at the following options. Are
there others? What are the risks of each of these. If you were me which way
would you go, consider the constraint above.
Option 1: Upgrade In Place - This option would upgrade all database to from
SQL Server 2000 to SQL server 2005 at the same time by SQL Server machine.
Option 2: Run a named instance of SQL Server 2005 - This option would
install a named instance of SQL Server 2005 on the same machine that is
running the default instance of SQL Server 2000. Databases would be migrated
one at a time, or a handful at a time, until all database have been migrated.
Once all databases have been migrated, SQL Server 2000 would be shutdown.
What are your opinions of how successful would each of these options be?
What are this risks of each option? Does running two instanances of
different versions of SQL Server cause any issue?If you have only one machine , I would recommend install SQL as a named
instance, and when you migrate all of the databases and test them
thouroughly you can stop SQL Server 2000.
Regards
Amish Shah
migration I have the contraint that I can't buy new machines. So I'm trying
to determine what options I have. First let me set the stage a little. For
a given SQL Server production machine I may have from 10-50
databases/application running. So I'm looking at the following options. Are
there others? What are the risks of each of these. If you were me which way
would you go, consider the constraint above.
Option 1: Upgrade In Place - This option would upgrade all database to from
SQL Server 2000 to SQL server 2005 at the same time by SQL Server machine.
Option 2: Run a named instance of SQL Server 2005 - This option would
install a named instance of SQL Server 2005 on the same machine that is
running the default instance of SQL Server 2000. Databases would be migrated
one at a time, or a handful at a time, until all database have been migrated.
Once all databases have been migrated, SQL Server 2000 would be shutdown.
What are your opinions of how successful would each of these options be?
What are this risks of each option? Does running two instanances of
different versions of SQL Server cause any issue?If you have only one machine , I would recommend install SQL as a named
instance, and when you migrate all of the databases and test them
thouroughly you can stop SQL Server 2000.
Regards
Amish Shah
Migrating to Report Services
Or rather, migrating to local reports using the Microsoft Report
Services.
We are in the process of planning the next generation of our software,
and among other things we are contemplating which reporting platform
we will use.
Until now we have been using Crystal Report, but it seems to be
getting more and more heavy to work with, plus it is a rather hefty
investment, well it can be.
First a little history:
- Our software will be running on anything from a stand-alone PC with
no connection to the surrounding world, to large-scale "enterprise"
networks with several dozens of clients. As a result our reporting
platform must be able to handle this.
Originally Crystal Report handled this very nicely, in that regard
that we simply installed the runtime libraries on each PC with our
software and a bunch of report files locally. This is model our
customers are used to.
Now I have decided to check out Reporting Services, but I have a bit
of a difficult time wrapping my mind around the concept. Some things
seem very nice and elegant, but others seem somewhat less so. For one
thing, the reports seem a little too simple and no where nearly as
powerful as Crystal Reports.
Now, our database is usually called the same regardless of the
customer, and of course, the layout of the database is always the same
(some customers may have a few custom tables, etc). But internally we
may have any number of databases that is named differently (customer
backups, test databases etc). So I need a way of being able to set the
database "on-the-fly".
What (I think) I need:
- A way of designing local reports and setting the data source at
runtime.
- I do not want to use the web server exclusively.
- Initially I want local reports, but the central reporting server can
be an option.
- I want to be able to mix tabular/matrix and chart reports.
- I want to be able to show group headers and footers, as well as page
headers and footers.
- I want to have full access to all tables in the database, and not
being restricted once I select on table, or entity.
Basically, I want to use the Reporting Service, but I don't want to
loose the freedom in data selection that Crystal Report gives me.According to your description, you need to use both SQL Server Reporting
Services and local report tool, which is bundled with VS2005/8 (VS2003 is
bundled with CrystalReport.NET as local report tool, while VS2005/8 come
with both CrystalReport.NET and MS report tool).
More comments inline.
"ThomasD" <tho.due@.gmail.com> wrote in message
news:4de6bed8-f6bc-4188-afd5-93ac01d49398@.8g2000hse.googlegroups.com...
> Or rather, migrating to local reports using the Microsoft Report
> Services.
> We are in the process of planning the next generation of our software,
> and among other things we are contemplating which reporting platform
> we will use.
> Until now we have been using Crystal Report, but it seems to be
> getting more and more heavy to work with, plus it is a rather hefty
> investment, well it can be.
> First a little history:
> - Our software will be running on anything from a stand-alone PC with
> no connection to the surrounding world, to large-scale "enterprise"
> networks with several dozens of clients. As a result our reporting
> platform must be able to handle this.
> Originally Crystal Report handled this very nicely, in that regard
> that we simply installed the runtime libraries on each PC with our
> software and a bunch of report files locally. This is model our
> customers are used to.
> Now I have decided to check out Reporting Services, but I have a bit
> of a difficult time wrapping my mind around the concept. Some things
> seem very nice and elegant, but others seem somewhat less so. For one
> thing, the reports seem a little too simple and no where nearly as
> powerful as Crystal Reports.
> Now, our database is usually called the same regardless of the
> customer, and of course, the layout of the database is always the same
> (some customers may have a few custom tables, etc). But internally we
> may have any number of databases that is named differently (customer
> backups, test databases etc). So I need a way of being able to set the
> database "on-the-fly".
> What (I think) I need:
> - A way of designing local reports and setting the data source at
> runtime.
If you have VS2005/8, you can do local report with either CrystalReport.NET
or MS report tool. By "Local". If you use SQL Server RS, I'd use MS report
tool in VS for local report, because the report viewer control can render
both local report and report from SQL Server RS. So, you app can seemlessly
dispaly report either from local report or from SQL Server RS without user
knowing the difference.
> - I do not want to use the web server exclusively.
> - Initially I want local reports, but the central reporting server can
> be an option.
> - I want to be able to mix tabular/matrix and chart reports.
> - I want to be able to show group headers and footers, as well as page
> headers and footers.
MS local report is a bit not as fancy as RS report can be.
> - I want to have full access to all tables in the database, and not
> being restricted once I select on table, or entity.
That has little to do with reporting, local or server.
> Basically, I want to use the Reporting Service, but I don't want to
> loose the freedom in data selection that Crystal Report gives me.
Do not know what "Data selection freedom" means here.
With local report, you can connect to whatever data source. If needed, you
can use code do trasform anything into a DataSet/Table of your desired
schema and use it as the report source, I'd think it is complete freedom.
With SQL Server RS, if the report data is difficult to access by reqular
queries, or the data source is not conventinal database, you can write your
own Data Processing Extensions sitting between the reporting processor and
data source. Of course, this requires lots of coding.|||> According to your description, you need to use both SQL Server Reporting
> Services and local report tool, which is bundled with VS2005/8 (VS2003 is
> bundled with CrystalReport.NET as local report tool, while VS2005/8 come
> with both CrystalReport.NET and MS report tool).
We use VS2008. I would like keep the option of using the report server
open, but my primary concern is local reports.
> More comments inline.
Cool. :)
> > - A way of designing local reports and setting the data source at
> > runtime.
> If you have VS2005/8, you can do local report with either CrystalReport.NET
> or MS report tool. By "Local". If you use SQL Server RS, I'd use MS report
> tool in VS for local report, because the report viewer control can render
> both local report and report from SQL Server RS. So, you app can seemlessly
> dispaly report either from local report or from SQL Server RS without user
> knowing the difference.
I finally managed to actually get the report designer working (it is
not easy to handle, when you are used to using Crystal Reports). It
looks very promising, however as it turns out, I have to supply the
data source "manually" when using the report locally. That is fine,
not a problem. However, I would like to use the SQL embedded in the
report, but that seems to be somewhat difficult to get at. So far I
have managed to get it by using XPath, but I can't help thinking that
there must be an easier way.
> MS local report is a bit not as fancy as RS report can be.
True, but I AM making progress in understanding the limitations and
differences.
> > - I want to have full access to all tables in the database, and not
> > being restricted once I select on table, or entity.
> That has little to do with reporting, local or server.
Well, after I "discovered" the report designer in Sql Server Business
Intelligence Development Studio (what a mouthful), I see that. Now I
just need to get a handle on the embedded SQL.
> > Basically, I want to use the Reporting Service, but I don't want to
> > loose the freedom in data selection that Crystal Report gives me.
> Do not know what "Data selection freedom" means here.
SQL. I don't want to be relying on some obscure model. Direct SQL
input is my preferred method of pulling data. Crystal Reports can do
both, and after discover the report designer in BI studio it looks
very promising.
> With local report, you can connect to whatever data source. If needed, you
> can use code do trasform anything into a DataSet/Table of your desired
> schema and use it as the report source, I'd think it is complete freedom.
> With SQL Server RS, if the report data is difficult to access by reqular
> queries, or the data source is not conventinal database, you can write your
> own Data Processing Extensions sitting between the reporting processor and
> data source. Of course, this requires lots of coding.
Coding doesn't scare me, I wouldn't be a software developer otherwise
*grin*
Regards,
Thomas
Services.
We are in the process of planning the next generation of our software,
and among other things we are contemplating which reporting platform
we will use.
Until now we have been using Crystal Report, but it seems to be
getting more and more heavy to work with, plus it is a rather hefty
investment, well it can be.
First a little history:
- Our software will be running on anything from a stand-alone PC with
no connection to the surrounding world, to large-scale "enterprise"
networks with several dozens of clients. As a result our reporting
platform must be able to handle this.
Originally Crystal Report handled this very nicely, in that regard
that we simply installed the runtime libraries on each PC with our
software and a bunch of report files locally. This is model our
customers are used to.
Now I have decided to check out Reporting Services, but I have a bit
of a difficult time wrapping my mind around the concept. Some things
seem very nice and elegant, but others seem somewhat less so. For one
thing, the reports seem a little too simple and no where nearly as
powerful as Crystal Reports.
Now, our database is usually called the same regardless of the
customer, and of course, the layout of the database is always the same
(some customers may have a few custom tables, etc). But internally we
may have any number of databases that is named differently (customer
backups, test databases etc). So I need a way of being able to set the
database "on-the-fly".
What (I think) I need:
- A way of designing local reports and setting the data source at
runtime.
- I do not want to use the web server exclusively.
- Initially I want local reports, but the central reporting server can
be an option.
- I want to be able to mix tabular/matrix and chart reports.
- I want to be able to show group headers and footers, as well as page
headers and footers.
- I want to have full access to all tables in the database, and not
being restricted once I select on table, or entity.
Basically, I want to use the Reporting Service, but I don't want to
loose the freedom in data selection that Crystal Report gives me.According to your description, you need to use both SQL Server Reporting
Services and local report tool, which is bundled with VS2005/8 (VS2003 is
bundled with CrystalReport.NET as local report tool, while VS2005/8 come
with both CrystalReport.NET and MS report tool).
More comments inline.
"ThomasD" <tho.due@.gmail.com> wrote in message
news:4de6bed8-f6bc-4188-afd5-93ac01d49398@.8g2000hse.googlegroups.com...
> Or rather, migrating to local reports using the Microsoft Report
> Services.
> We are in the process of planning the next generation of our software,
> and among other things we are contemplating which reporting platform
> we will use.
> Until now we have been using Crystal Report, but it seems to be
> getting more and more heavy to work with, plus it is a rather hefty
> investment, well it can be.
> First a little history:
> - Our software will be running on anything from a stand-alone PC with
> no connection to the surrounding world, to large-scale "enterprise"
> networks with several dozens of clients. As a result our reporting
> platform must be able to handle this.
> Originally Crystal Report handled this very nicely, in that regard
> that we simply installed the runtime libraries on each PC with our
> software and a bunch of report files locally. This is model our
> customers are used to.
> Now I have decided to check out Reporting Services, but I have a bit
> of a difficult time wrapping my mind around the concept. Some things
> seem very nice and elegant, but others seem somewhat less so. For one
> thing, the reports seem a little too simple and no where nearly as
> powerful as Crystal Reports.
> Now, our database is usually called the same regardless of the
> customer, and of course, the layout of the database is always the same
> (some customers may have a few custom tables, etc). But internally we
> may have any number of databases that is named differently (customer
> backups, test databases etc). So I need a way of being able to set the
> database "on-the-fly".
> What (I think) I need:
> - A way of designing local reports and setting the data source at
> runtime.
If you have VS2005/8, you can do local report with either CrystalReport.NET
or MS report tool. By "Local". If you use SQL Server RS, I'd use MS report
tool in VS for local report, because the report viewer control can render
both local report and report from SQL Server RS. So, you app can seemlessly
dispaly report either from local report or from SQL Server RS without user
knowing the difference.
> - I do not want to use the web server exclusively.
> - Initially I want local reports, but the central reporting server can
> be an option.
> - I want to be able to mix tabular/matrix and chart reports.
> - I want to be able to show group headers and footers, as well as page
> headers and footers.
MS local report is a bit not as fancy as RS report can be.
> - I want to have full access to all tables in the database, and not
> being restricted once I select on table, or entity.
That has little to do with reporting, local or server.
> Basically, I want to use the Reporting Service, but I don't want to
> loose the freedom in data selection that Crystal Report gives me.
Do not know what "Data selection freedom" means here.
With local report, you can connect to whatever data source. If needed, you
can use code do trasform anything into a DataSet/Table of your desired
schema and use it as the report source, I'd think it is complete freedom.
With SQL Server RS, if the report data is difficult to access by reqular
queries, or the data source is not conventinal database, you can write your
own Data Processing Extensions sitting between the reporting processor and
data source. Of course, this requires lots of coding.|||> According to your description, you need to use both SQL Server Reporting
> Services and local report tool, which is bundled with VS2005/8 (VS2003 is
> bundled with CrystalReport.NET as local report tool, while VS2005/8 come
> with both CrystalReport.NET and MS report tool).
We use VS2008. I would like keep the option of using the report server
open, but my primary concern is local reports.
> More comments inline.
Cool. :)
> > - A way of designing local reports and setting the data source at
> > runtime.
> If you have VS2005/8, you can do local report with either CrystalReport.NET
> or MS report tool. By "Local". If you use SQL Server RS, I'd use MS report
> tool in VS for local report, because the report viewer control can render
> both local report and report from SQL Server RS. So, you app can seemlessly
> dispaly report either from local report or from SQL Server RS without user
> knowing the difference.
I finally managed to actually get the report designer working (it is
not easy to handle, when you are used to using Crystal Reports). It
looks very promising, however as it turns out, I have to supply the
data source "manually" when using the report locally. That is fine,
not a problem. However, I would like to use the SQL embedded in the
report, but that seems to be somewhat difficult to get at. So far I
have managed to get it by using XPath, but I can't help thinking that
there must be an easier way.
> MS local report is a bit not as fancy as RS report can be.
True, but I AM making progress in understanding the limitations and
differences.
> > - I want to have full access to all tables in the database, and not
> > being restricted once I select on table, or entity.
> That has little to do with reporting, local or server.
Well, after I "discovered" the report designer in Sql Server Business
Intelligence Development Studio (what a mouthful), I see that. Now I
just need to get a handle on the embedded SQL.
> > Basically, I want to use the Reporting Service, but I don't want to
> > loose the freedom in data selection that Crystal Report gives me.
> Do not know what "Data selection freedom" means here.
SQL. I don't want to be relying on some obscure model. Direct SQL
input is my preferred method of pulling data. Crystal Reports can do
both, and after discover the report designer in BI studio it looks
very promising.
> With local report, you can connect to whatever data source. If needed, you
> can use code do trasform anything into a DataSet/Table of your desired
> schema and use it as the report source, I'd think it is complete freedom.
> With SQL Server RS, if the report data is difficult to access by reqular
> queries, or the data source is not conventinal database, you can write your
> own Data Processing Extensions sitting between the reporting processor and
> data source. Of course, this requires lots of coding.
Coding doesn't scare me, I wouldn't be a software developer otherwise
*grin*
Regards,
Thomas
Subscribe to:
Posts (Atom)