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.
Showing posts with label sybase. Show all posts
Showing posts with label sybase. Show all posts
Friday, March 9, 2012
Wednesday, March 7, 2012
Migration from Sybase to SQL 2000 problems
Hello,
I'm having a problem migrating a particular stored Procedure wich runs
nested and interdependent Fetching from temporary tables.
There is a main cursor and from that, a var is retrieved for use as a
parameter for other cursors. The most important is that the Cursor's queryes
all run successfully independently and with the parameters filled in.
//main cursor
declare CritSelAgr cursor for
select CodCritSelec, TodosSectInst, TodosPrzContr, TodosPais,
TodosMoeda, Coeficiente
from P_TRMCCSE0
where MRCUIC = @.PCodRub and
MRCUKN = @.PVersRub
order by CodCritSelec
for read only
select @.ErroSql = @.@.error
if @.ErroSql <> 0
begin
exec PCRMZZZZ0itratamsg @.ErroSql
return @.ErroSql
end
//dependent cursor *uses CodCritSelec from the main cursor
declare CritInstrFin cursor for
select CodInstrFin, CIF.CodTpConta, DescTpConta
from P_TRMCCIF0 CIF,
VRMCTCO00 TCO
where MRCUIC = @.PCodRub and
MRCUKN = @.PVersRub and
CodCritSelec = @.CodCritSelec and
CIF.CodTpConta = TCO.CodTpConta
order by CodInstrFin, TCO.CodTpConta
for read only
select @.ErroSql = @.@.error
if @.ErroSql <> 0
begin
exec PCRMZZZZ0itratamsg @.ErroSql
return @.ErroSql
end
In the stored procedure they do not work, only the main query, wich has all
parameters set works well.
//this is an extract of the code from the stored procedure
open CritSelAgr
select @.ErroSql = @.@.error
if @.ErroSql <> 0
begin
exec PCRMZZZZ0itratamsg @.ErroSql
return @.ErroSql
end
select @.SqlStat = 0
while( @.SqlStat = 0 )
begin
fetch CritSelAgr into @.CodCritSelec, @.TodosSectInst, @.TodosPrzContr,
@.TodosPais,
@.TodosMoeda, @.Coeficiente
select @.ErroSql = @.@.error, @.SqlStat = @.@.fetch_status
if @.ErroSql <> 0
begin
exec PCRMZZZZ0itratamsg @.ErroSql
return @.ErroSql
end
if @.SqlStat <> 0
break
select @.InstrFin = NULL, @.SectInst = NULL, @.PrzContr = NULL, @.Pais =
NULL, @.Moeda = NULL
open CritInstrFin
select @.ErroSql = @.@.error
if @.ErroSql <> 0
begin
exec PCRMZZZZ0itratamsg @.ErroSql
return @.ErroSql
end
select @.SqlStatCrit = 0
while( @.SqlStatCrit = 0 )
begin
fetch CritInstrFin into @.CodInstrFin, @.CodTpConta, @.DescTpConta
select @.ErroSql = @.@.error, @.SqlStatCrit = @.@.fetch_status
//*****@.@.fetch_status is ALWAYS -1 here and in the other cursors as well
Is there a way to pass explicitly the parameters to a cursor or it's enough
to have the vars defined in the scope? (I think that's the problem)
Thaks in advanceSince you are changing platforms, wouldn't now be a good time to get rid of
any legacy cursor code? I expect this could be done much more quickly and
efficiently with set-based code.
If you need more help, please post a fuller description of the problem as
explained in the following article:
http://www.aspfaq.com/etiquette.asp?id=5006
David Portas
SQL Server MVP
--|||Thanks for the reply,
Do you mean
Set @.var = value?
"David Portas" wrote:
> Since you are changing platforms, wouldn't now be a good time to get rid o
f
> any legacy cursor code? I expect this could be done much more quickly and
> efficiently with set-based code.
> If you need more help, please post a fuller description of the problem as
> explained in the following article:
> http://www.aspfaq.com/etiquette.asp?id=5006
> --
> David Portas
> SQL Server MVP
> --
>|||No. Set-based code means declarative SQL code that operates on entire sets o
f
rows. On the other hand, cursor code only processes one row at a time. SQL
Server is optimized for set-based code, not for cursors.
Without more information it's hard to guess how to do it in your case but
you should aim to write code using regular SELECT, UPDATE, INSERT and DELETE
statements *without* cursors. Cursors are rarely a good idea and most of the
time you don't need them.
David Portas
SQL Server MVP
--|||do you mean set based logic like in joins?
as for ex: in http://techrepublic.com.com/5100-6228_11-5532304.html
"David Portas" wrote:
> No. Set-based code means declarative SQL code that operates on entire sets
of
> rows. On the other hand, cursor code only processes one row at a time. SQL
> Server is optimized for set-based code, not for cursors.
> Without more information it's hard to guess how to do it in your case but
> you should aim to write code using regular SELECT, UPDATE, INSERT and DELE
TE
> statements *without* cursors. Cursors are rarely a good idea and most of t
he
> time you don't need them.
> --
> David Portas
> SQL Server MVP
> --|||Joins are set based operations, yes.
David Portas
SQL Server MVP
--
I'm having a problem migrating a particular stored Procedure wich runs
nested and interdependent Fetching from temporary tables.
There is a main cursor and from that, a var is retrieved for use as a
parameter for other cursors. The most important is that the Cursor's queryes
all run successfully independently and with the parameters filled in.
//main cursor
declare CritSelAgr cursor for
select CodCritSelec, TodosSectInst, TodosPrzContr, TodosPais,
TodosMoeda, Coeficiente
from P_TRMCCSE0
where MRCUIC = @.PCodRub and
MRCUKN = @.PVersRub
order by CodCritSelec
for read only
select @.ErroSql = @.@.error
if @.ErroSql <> 0
begin
exec PCRMZZZZ0itratamsg @.ErroSql
return @.ErroSql
end
//dependent cursor *uses CodCritSelec from the main cursor
declare CritInstrFin cursor for
select CodInstrFin, CIF.CodTpConta, DescTpConta
from P_TRMCCIF0 CIF,
VRMCTCO00 TCO
where MRCUIC = @.PCodRub and
MRCUKN = @.PVersRub and
CodCritSelec = @.CodCritSelec and
CIF.CodTpConta = TCO.CodTpConta
order by CodInstrFin, TCO.CodTpConta
for read only
select @.ErroSql = @.@.error
if @.ErroSql <> 0
begin
exec PCRMZZZZ0itratamsg @.ErroSql
return @.ErroSql
end
In the stored procedure they do not work, only the main query, wich has all
parameters set works well.
//this is an extract of the code from the stored procedure
open CritSelAgr
select @.ErroSql = @.@.error
if @.ErroSql <> 0
begin
exec PCRMZZZZ0itratamsg @.ErroSql
return @.ErroSql
end
select @.SqlStat = 0
while( @.SqlStat = 0 )
begin
fetch CritSelAgr into @.CodCritSelec, @.TodosSectInst, @.TodosPrzContr,
@.TodosPais,
@.TodosMoeda, @.Coeficiente
select @.ErroSql = @.@.error, @.SqlStat = @.@.fetch_status
if @.ErroSql <> 0
begin
exec PCRMZZZZ0itratamsg @.ErroSql
return @.ErroSql
end
if @.SqlStat <> 0
break
select @.InstrFin = NULL, @.SectInst = NULL, @.PrzContr = NULL, @.Pais =
NULL, @.Moeda = NULL
open CritInstrFin
select @.ErroSql = @.@.error
if @.ErroSql <> 0
begin
exec PCRMZZZZ0itratamsg @.ErroSql
return @.ErroSql
end
select @.SqlStatCrit = 0
while( @.SqlStatCrit = 0 )
begin
fetch CritInstrFin into @.CodInstrFin, @.CodTpConta, @.DescTpConta
select @.ErroSql = @.@.error, @.SqlStatCrit = @.@.fetch_status
//*****@.@.fetch_status is ALWAYS -1 here and in the other cursors as well
Is there a way to pass explicitly the parameters to a cursor or it's enough
to have the vars defined in the scope? (I think that's the problem)
Thaks in advanceSince you are changing platforms, wouldn't now be a good time to get rid of
any legacy cursor code? I expect this could be done much more quickly and
efficiently with set-based code.
If you need more help, please post a fuller description of the problem as
explained in the following article:
http://www.aspfaq.com/etiquette.asp?id=5006
David Portas
SQL Server MVP
--|||Thanks for the reply,
Do you mean
Set @.var = value?
"David Portas" wrote:
> Since you are changing platforms, wouldn't now be a good time to get rid o
f
> any legacy cursor code? I expect this could be done much more quickly and
> efficiently with set-based code.
> If you need more help, please post a fuller description of the problem as
> explained in the following article:
> http://www.aspfaq.com/etiquette.asp?id=5006
> --
> David Portas
> SQL Server MVP
> --
>|||No. Set-based code means declarative SQL code that operates on entire sets o
f
rows. On the other hand, cursor code only processes one row at a time. SQL
Server is optimized for set-based code, not for cursors.
Without more information it's hard to guess how to do it in your case but
you should aim to write code using regular SELECT, UPDATE, INSERT and DELETE
statements *without* cursors. Cursors are rarely a good idea and most of the
time you don't need them.
David Portas
SQL Server MVP
--|||do you mean set based logic like in joins?
as for ex: in http://techrepublic.com.com/5100-6228_11-5532304.html
"David Portas" wrote:
> No. Set-based code means declarative SQL code that operates on entire sets
of
> rows. On the other hand, cursor code only processes one row at a time. SQL
> Server is optimized for set-based code, not for cursors.
> Without more information it's hard to guess how to do it in your case but
> you should aim to write code using regular SELECT, UPDATE, INSERT and DELE
TE
> statements *without* cursors. Cursors are rarely a good idea and most of t
he
> time you don't need them.
> --
> David Portas
> SQL Server MVP
> --|||Joins are set based operations, yes.
David Portas
SQL Server MVP
--
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 sybase 8.0 to mssql server 2005
Hi all,
Here i had a task to migrate sybase 8.0 database to mssqlserver 2005 .how can i migrate this using INTEGRATED SERVICES (SSIS) or any other options. .Please try to provide some basical info because i am new to sybase versions.
Maybe these article will help:http://www.microsoft.com/resources/documentation/sql/2000/all/reskit/en-us/part2/c0661.mspx
http://www.microsoft.com/technet/itsolutions/migration/unix/sybsqlsv/default.mspx
http://www.microsoft.com/downloads/details.aspx?familyid=E7541305-891F-494A-B58B-2EED819C4411&displaylang=en
http://www.microsoft.com/sql/prodinfo/compare/sybase.mspx
http://www.devarticles.com/c/a/SQL-Server/Migrating-from-Sybase-to-SQL-Server/|||Basically that artical explaining migration from sybase|unix to sqlserver 2000 But not mssql server 2005 ,i gone through that article before but i did not find any help from that please can you make it clear.
Monday, February 20, 2012
Migrating Sybase to SQL Server 2000
I'm currently involving in a project in migrating from
Sybase to SQL Server 2000. I've been able to
successfully (and conveniently) import my tables/data.
My question involves the Stored Procedures. Can these
stored procedures be import w/ a wizard (i.e. the way my
tables/data have been converted)? Or must I manually
create new SP's in SQL Server, making the necessary
changes (Rollback trigger, transaction isolation levels,
etc.) on the fly?
I think that you must to do the necessary changes.
The sybase code is not totally compatible with sql2k.
After this forget sybase, please.
<anonymous@.discussions.microsoft.com> escreveu na mensagem
news:16a0801c4481a$7b9a8410$a401280a@.phx.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?
|||Hi,
Have a look into the below article from MS:-
http://www.microsoft.com/resources/d...reskit/en-us/p
art2/c0661.mspx
Thanks
Hari
MCDBA
<anonymous@.discussions.microsoft.com> wrote in message
news:16a0801c4481a$7b9a8410$a401280a@.phx.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?
|||Yes, you must make the changes manually, but there should not be a whole lot
of changes...They are doc'd in the article mentioned previously.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<anonymous@.discussions.microsoft.com> wrote in message
news:16a0801c4481a$7b9a8410$a401280a@.phx.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?
Sybase to SQL Server 2000. I've been able to
successfully (and conveniently) import my tables/data.
My question involves the Stored Procedures. Can these
stored procedures be import w/ a wizard (i.e. the way my
tables/data have been converted)? Or must I manually
create new SP's in SQL Server, making the necessary
changes (Rollback trigger, transaction isolation levels,
etc.) on the fly?
I think that you must to do the necessary changes.
The sybase code is not totally compatible with sql2k.
After this forget sybase, please.
<anonymous@.discussions.microsoft.com> escreveu na mensagem
news:16a0801c4481a$7b9a8410$a401280a@.phx.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?
|||Hi,
Have a look into the below article from MS:-
http://www.microsoft.com/resources/d...reskit/en-us/p
art2/c0661.mspx
Thanks
Hari
MCDBA
<anonymous@.discussions.microsoft.com> wrote in message
news:16a0801c4481a$7b9a8410$a401280a@.phx.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?
|||Yes, you must make the changes manually, but there should not be a whole lot
of changes...They are doc'd in the article mentioned previously.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<anonymous@.discussions.microsoft.com> wrote in message
news:16a0801c4481a$7b9a8410$a401280a@.phx.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?
Migrating Sybase to SQL Server 2000
I'm currently involving in a project in migrating from
Sybase to SQL Server 2000. I've been able to
successfully (and conveniently) import my tables/data.
My question involves the Stored Procedures. Can these
stored procedures be import w/ a wizard (i.e. the way my
tables/data have been converted)? Or must I manually
create new SP's in SQL Server, making the necessary
changes (Rollback trigger, transaction isolation levels,
etc.) on the fly?I think that you must to do the necessary changes.
The sybase code is not totally compatible with sql2k.
After this forget sybase, please.
<anonymous@.discussions.microsoft.com> escreveu na mensagem
news:16a0801c4481a$7b9a8410$a401280a@.phx.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?|||Hi,
Have a look into the below article from MS:-
http://www.microsoft.com/resources/documentation/sql/2000/all/reskit/en-us/p
art2/c0661.mspx
Thanks
Hari
MCDBA
<anonymous@.discussions.microsoft.com> wrote in message
news:16a0801c4481a$7b9a8410$a401280a@.phx.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?|||Yes, you must make the changes manually, but there should not be a whole lot
of changes...They are doc'd in the article mentioned previously.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<anonymous@.discussions.microsoft.com> wrote in message
news:16a0801c4481a$7b9a8410$a401280a@.phx.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?
Sybase to SQL Server 2000. I've been able to
successfully (and conveniently) import my tables/data.
My question involves the Stored Procedures. Can these
stored procedures be import w/ a wizard (i.e. the way my
tables/data have been converted)? Or must I manually
create new SP's in SQL Server, making the necessary
changes (Rollback trigger, transaction isolation levels,
etc.) on the fly?I think that you must to do the necessary changes.
The sybase code is not totally compatible with sql2k.
After this forget sybase, please.
<anonymous@.discussions.microsoft.com> escreveu na mensagem
news:16a0801c4481a$7b9a8410$a401280a@.phx.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?|||Hi,
Have a look into the below article from MS:-
http://www.microsoft.com/resources/documentation/sql/2000/all/reskit/en-us/p
art2/c0661.mspx
Thanks
Hari
MCDBA
<anonymous@.discussions.microsoft.com> wrote in message
news:16a0801c4481a$7b9a8410$a401280a@.phx.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?|||Yes, you must make the changes manually, but there should not be a whole lot
of changes...They are doc'd in the article mentioned previously.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<anonymous@.discussions.microsoft.com> wrote in message
news:16a0801c4481a$7b9a8410$a401280a@.phx.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?
Migrating Sybase to SQL Server 2000
I'm currently involving in a project in migrating from
Sybase to SQL Server 2000. I've been able to
successfully (and conveniently) import my tables/data.
My question involves the Stored Procedures. Can these
stored procedures be import w/ a wizard (i.e. the way my
tables/data have been converted)? Or must I manually
create new SP's in SQL Server, making the necessary
changes (Rollback trigger, transaction isolation levels,
etc.) on the fly?I think that you must to do the necessary changes.
The sybase code is not totally compatible with sql2k.
After this forget sybase, please.
<anonymous@.discussions.microsoft.com> escreveu na mensagem
news:16a0801c4481a$7b9a8410$a401280a@.phx
.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?|||Hi,
Have a look into the below article from MS:-
http://www.microsoft.com/resources/.../reskit/en-us/p
art2/c0661.mspx
Thanks
Hari
MCDBA
<anonymous@.discussions.microsoft.com> wrote in message
news:16a0801c4481a$7b9a8410$a401280a@.phx
.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?|||Yes, you must make the changes manually, but there should not be a whole lot
of changes...They are doc'd in the article mentioned previously.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<anonymous@.discussions.microsoft.com> wrote in message
news:16a0801c4481a$7b9a8410$a401280a@.phx
.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?
Sybase to SQL Server 2000. I've been able to
successfully (and conveniently) import my tables/data.
My question involves the Stored Procedures. Can these
stored procedures be import w/ a wizard (i.e. the way my
tables/data have been converted)? Or must I manually
create new SP's in SQL Server, making the necessary
changes (Rollback trigger, transaction isolation levels,
etc.) on the fly?I think that you must to do the necessary changes.
The sybase code is not totally compatible with sql2k.
After this forget sybase, please.
<anonymous@.discussions.microsoft.com> escreveu na mensagem
news:16a0801c4481a$7b9a8410$a401280a@.phx
.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?|||Hi,
Have a look into the below article from MS:-
http://www.microsoft.com/resources/.../reskit/en-us/p
art2/c0661.mspx
Thanks
Hari
MCDBA
<anonymous@.discussions.microsoft.com> wrote in message
news:16a0801c4481a$7b9a8410$a401280a@.phx
.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?|||Yes, you must make the changes manually, but there should not be a whole lot
of changes...They are doc'd in the article mentioned previously.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<anonymous@.discussions.microsoft.com> wrote in message
news:16a0801c4481a$7b9a8410$a401280a@.phx
.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?
Subscribe to:
Posts (Atom)