The client I'm working at right now is currently moving from their current
ERP contained on AS/400 to a MS SQL Server based ERP known as SYSPRO. In
doing so they are migrating 2 physical AS/400's with 4 business units (2 on
each 400) over to SYSPRO. They have moved one out of the four and a
preparing to move the the second. When migrating over to SYSPRO they only
moved the needed information to go live on the new system hence leaving years
of sales, orders, customer and product information.
So my question is there anything just blazingly important that I should know
when using DTS to pull all of this data over to SQL Server?
I know that the structure of the 400 DB2 isn't exactly the same as SQL
Server. From what I understand multiple Libraries make up a database in the
400. Each of those contain files and logicals. Files look to be the same as
a tables and logicals look to be the same as views.
Thx
You're pretty much on the ball with the file vs table and logical vs view
deal, for what you're trying to do, they're affectively equivalent. I ran
into some trouble with this in a past life, though. There was a lot of
trailing white space in the character fields I pulled out of the 400. It was
a different ERP, and it may have been human error causing it (I'm no DB2
guru), but I wound up having to RTRIM a lot of stuff on it's way over. Only
issue I ran into, though.
"Chris Stevenson" wrote:
> The client I'm working at right now is currently moving from their current
> ERP contained on AS/400 to a MS SQL Server based ERP known as SYSPRO. In
> doing so they are migrating 2 physical AS/400's with 4 business units (2 on
> each 400) over to SYSPRO. They have moved one out of the four and a
> preparing to move the the second. When migrating over to SYSPRO they only
> moved the needed information to go live on the new system hence leaving years
> of sales, orders, customer and product information.
> So my question is there anything just blazingly important that I should know
> when using DTS to pull all of this data over to SQL Server?
> I know that the structure of the 400 DB2 isn't exactly the same as SQL
> Server. From what I understand multiple Libraries make up a database in the
> 400. Each of those contain files and logicals. Files look to be the same as
> a tables and logicals look to be the same as views.
> Thx
Showing posts with label client. Show all posts
Showing posts with label client. Show all posts
Monday, March 26, 2012
Migrating AS/400 DB2 to SQL Server
The client I'm working at right now is currently moving from their current
ERP contained on AS/400 to a MS SQL Server based ERP known as SYSPRO. In
doing so they are migrating 2 physical AS/400's with 4 business units (2 on
each 400) over to SYSPRO. They have moved one out of the four and a
preparing to move the the second. When migrating over to SYSPRO they only
moved the needed information to go live on the new system hence leaving years
of sales, orders, customer and product information.
So my question is there anything just blazingly important that I should know
when using DTS to pull all of this data over to SQL Server?
I know that the structure of the 400 DB2 isn't exactly the same as SQL
Server. From what I understand multiple Libraries make up a database in the
400. Each of those contain files and logicals. Files look to be the same as
a tables and logicals look to be the same as views.
ThxYou're pretty much on the ball with the file vs table and logical vs view
deal, for what you're trying to do, they're affectively equivalent. I ran
into some trouble with this in a past life, though. There was a lot of
trailing white space in the character fields I pulled out of the 400. It was
a different ERP, and it may have been human error causing it (I'm no DB2
guru), but I wound up having to RTRIM a lot of stuff on it's way over. Only
issue I ran into, though.
"Chris Stevenson" wrote:
> The client I'm working at right now is currently moving from their current
> ERP contained on AS/400 to a MS SQL Server based ERP known as SYSPRO. In
> doing so they are migrating 2 physical AS/400's with 4 business units (2 on
> each 400) over to SYSPRO. They have moved one out of the four and a
> preparing to move the the second. When migrating over to SYSPRO they only
> moved the needed information to go live on the new system hence leaving years
> of sales, orders, customer and product information.
> So my question is there anything just blazingly important that I should know
> when using DTS to pull all of this data over to SQL Server?
> I know that the structure of the 400 DB2 isn't exactly the same as SQL
> Server. From what I understand multiple Libraries make up a database in the
> 400. Each of those contain files and logicals. Files look to be the same as
> a tables and logicals look to be the same as views.
> Thx
ERP contained on AS/400 to a MS SQL Server based ERP known as SYSPRO. In
doing so they are migrating 2 physical AS/400's with 4 business units (2 on
each 400) over to SYSPRO. They have moved one out of the four and a
preparing to move the the second. When migrating over to SYSPRO they only
moved the needed information to go live on the new system hence leaving years
of sales, orders, customer and product information.
So my question is there anything just blazingly important that I should know
when using DTS to pull all of this data over to SQL Server?
I know that the structure of the 400 DB2 isn't exactly the same as SQL
Server. From what I understand multiple Libraries make up a database in the
400. Each of those contain files and logicals. Files look to be the same as
a tables and logicals look to be the same as views.
ThxYou're pretty much on the ball with the file vs table and logical vs view
deal, for what you're trying to do, they're affectively equivalent. I ran
into some trouble with this in a past life, though. There was a lot of
trailing white space in the character fields I pulled out of the 400. It was
a different ERP, and it may have been human error causing it (I'm no DB2
guru), but I wound up having to RTRIM a lot of stuff on it's way over. Only
issue I ran into, though.
"Chris Stevenson" wrote:
> The client I'm working at right now is currently moving from their current
> ERP contained on AS/400 to a MS SQL Server based ERP known as SYSPRO. In
> doing so they are migrating 2 physical AS/400's with 4 business units (2 on
> each 400) over to SYSPRO. They have moved one out of the four and a
> preparing to move the the second. When migrating over to SYSPRO they only
> moved the needed information to go live on the new system hence leaving years
> of sales, orders, customer and product information.
> So my question is there anything just blazingly important that I should know
> when using DTS to pull all of this data over to SQL Server?
> I know that the structure of the 400 DB2 isn't exactly the same as SQL
> Server. From what I understand multiple Libraries make up a database in the
> 400. Each of those contain files and logicals. Files look to be the same as
> a tables and logicals look to be the same as views.
> Thx
Migrating AS/400 DB2 to SQL Server
The client I'm working at right now is currently moving from their current
ERP contained on AS/400 to a MS SQL Server based ERP known as SYSPRO. In
doing so they are migrating 2 physical AS/400's with 4 business units (2 on
each 400) over to SYSPRO. They have moved one out of the four and a
preparing to move the the second. When migrating over to SYSPRO they only
moved the needed information to go live on the new system hence leaving year
s
of sales, orders, customer and product information.
So my question is there anything just blazingly important that I should know
when using DTS to pull all of this data over to SQL Server?
I know that the structure of the 400 DB2 isn't exactly the same as SQL
Server. From what I understand multiple Libraries make up a database in the
400. Each of those contain files and logicals. Files look to be the same a
s
a tables and logicals look to be the same as views.
ThxYou're pretty much on the ball with the file vs table and logical vs view
deal, for what you're trying to do, they're affectively equivalent. I ran
into some trouble with this in a past life, though. There was a lot of
trailing white space in the character fields I pulled out of the 400. It wa
s
a different ERP, and it may have been human error causing it (I'm no DB2
guru), but I wound up having to RTRIM a lot of stuff on it's way over. Only
issue I ran into, though.
"Chris Stevenson" wrote:
> The client I'm working at right now is currently moving from their current
> ERP contained on AS/400 to a MS SQL Server based ERP known as SYSPRO. In
> doing so they are migrating 2 physical AS/400's with 4 business units (2 o
n
> each 400) over to SYSPRO. They have moved one out of the four and a
> preparing to move the the second. When migrating over to SYSPRO they only
> moved the needed information to go live on the new system hence leaving ye
ars
> of sales, orders, customer and product information.
> So my question is there anything just blazingly important that I should kn
ow
> when using DTS to pull all of this data over to SQL Server?
> I know that the structure of the 400 DB2 isn't exactly the same as SQL
> Server. From what I understand multiple Libraries make up a database in t
he
> 400. Each of those contain files and logicals. Files look to be the same
as
> a tables and logicals look to be the same as views.
> Thx
ERP contained on AS/400 to a MS SQL Server based ERP known as SYSPRO. In
doing so they are migrating 2 physical AS/400's with 4 business units (2 on
each 400) over to SYSPRO. They have moved one out of the four and a
preparing to move the the second. When migrating over to SYSPRO they only
moved the needed information to go live on the new system hence leaving year
s
of sales, orders, customer and product information.
So my question is there anything just blazingly important that I should know
when using DTS to pull all of this data over to SQL Server?
I know that the structure of the 400 DB2 isn't exactly the same as SQL
Server. From what I understand multiple Libraries make up a database in the
400. Each of those contain files and logicals. Files look to be the same a
s
a tables and logicals look to be the same as views.
ThxYou're pretty much on the ball with the file vs table and logical vs view
deal, for what you're trying to do, they're affectively equivalent. I ran
into some trouble with this in a past life, though. There was a lot of
trailing white space in the character fields I pulled out of the 400. It wa
s
a different ERP, and it may have been human error causing it (I'm no DB2
guru), but I wound up having to RTRIM a lot of stuff on it's way over. Only
issue I ran into, though.
"Chris Stevenson" wrote:
> The client I'm working at right now is currently moving from their current
> ERP contained on AS/400 to a MS SQL Server based ERP known as SYSPRO. In
> doing so they are migrating 2 physical AS/400's with 4 business units (2 o
n
> each 400) over to SYSPRO. They have moved one out of the four and a
> preparing to move the the second. When migrating over to SYSPRO they only
> moved the needed information to go live on the new system hence leaving ye
ars
> of sales, orders, customer and product information.
> So my question is there anything just blazingly important that I should kn
ow
> when using DTS to pull all of this data over to SQL Server?
> I know that the structure of the 400 DB2 isn't exactly the same as SQL
> Server. From what I understand multiple Libraries make up a database in t
he
> 400. Each of those contain files and logicals. Files look to be the same
as
> a tables and logicals look to be the same as views.
> Thx
Wednesday, March 7, 2012
Microsoft Word Delivery Extension & Use of web client
1. Is there a Microsoft Word or RTF delivery extension available for SQL
Reporting Services?
If not, is there any technique of producing the same with XML and XSLT?
2. To solve the security extension problem on a standard edition:
I am thinking of using web client on a filter page on the web server to
connect to the reporting server so that I don't bypass the web server when a
URL access request comes thru.
I mean, the URL for the report viewer won't be reporting server, instead it
will be an aspx (filter) page within the web server. The filter on the web
server will intercept and in turn impersonate a user on the report server and
render a report in the report viewer.
My question: I have not used web clients from web server before. Will it
affect the performance of web server? Is the above theory make sense at all?
I haven't implemented it.
Thanks,
Sri.The XML/XSLT idea is probably your best bet. Years ago I created a custom
RTF generator (to create nice-looking documents from a CASE tool). It's
easy once you do two things:
(1) Hunt down the RTF specification (from Microsoft I think), and learn the
basic syntax.
(2) Create a Word document that looks like what you want and save it to RTF
as a baseline/reference.
Then, you'll be armed and dangerous -- especially if you know how to do
XSLT.
--
Cheers,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"Sri" <Sri@.discussions.microsoft.com> wrote in message
news:8B848583-4F7E-490F-9E77-95CD40C30072@.microsoft.com...
> 1. Is there a Microsoft Word or RTF delivery extension available for SQL
> Reporting Services?
> If not, is there any technique of producing the same with XML and XSLT?
> 2. To solve the security extension problem on a standard edition:
> I am thinking of using web client on a filter page on the web server to
> connect to the reporting server so that I don't bypass the web server when
> a
> URL access request comes thru.
> I mean, the URL for the report viewer won't be reporting server, instead
> it
> will be an aspx (filter) page within the web server. The filter on the web
> server will intercept and in turn impersonate a user on the report server
> and
> render a report in the report viewer.
> My question: I have not used web clients from web server before. Will it
> affect the performance of web server? Is the above theory make sense at
> all?
> I haven't implemented it.
> Thanks,
> Sri.
>|||Thanks Jeff. I will investigate.
"Jeff A. Stucker" wrote:
> The XML/XSLT idea is probably your best bet. Years ago I created a custom
> RTF generator (to create nice-looking documents from a CASE tool). It's
> easy once you do two things:
> (1) Hunt down the RTF specification (from Microsoft I think), and learn the
> basic syntax.
> (2) Create a Word document that looks like what you want and save it to RTF
> as a baseline/reference.
> Then, you'll be armed and dangerous -- especially if you know how to do
> XSLT.
> --
> Cheers,
> '(' Jeff A. Stucker
> \
> Business Intelligence
> www.criadvantage.com
> ---
> "Sri" <Sri@.discussions.microsoft.com> wrote in message
> news:8B848583-4F7E-490F-9E77-95CD40C30072@.microsoft.com...
> > 1. Is there a Microsoft Word or RTF delivery extension available for SQL
> > Reporting Services?
> >
> > If not, is there any technique of producing the same with XML and XSLT?
> >
> > 2. To solve the security extension problem on a standard edition:
> >
> > I am thinking of using web client on a filter page on the web server to
> > connect to the reporting server so that I don't bypass the web server when
> > a
> > URL access request comes thru.
> > I mean, the URL for the report viewer won't be reporting server, instead
> > it
> > will be an aspx (filter) page within the web server. The filter on the web
> > server will intercept and in turn impersonate a user on the report server
> > and
> > render a report in the report viewer.
> >
> > My question: I have not used web clients from web server before. Will it
> > affect the performance of web server? Is the above theory make sense at
> > all?
> > I haven't implemented it.
> >
> > Thanks,
> > Sri.
> >
>
>|||Hi,
You can check http://officewriter.softartisans.com/officewriter-250.aspx
for the first question.
creating a 'filter' will not affect performance
--
Message posted via http://www.sqlmonster.com
Reporting Services?
If not, is there any technique of producing the same with XML and XSLT?
2. To solve the security extension problem on a standard edition:
I am thinking of using web client on a filter page on the web server to
connect to the reporting server so that I don't bypass the web server when a
URL access request comes thru.
I mean, the URL for the report viewer won't be reporting server, instead it
will be an aspx (filter) page within the web server. The filter on the web
server will intercept and in turn impersonate a user on the report server and
render a report in the report viewer.
My question: I have not used web clients from web server before. Will it
affect the performance of web server? Is the above theory make sense at all?
I haven't implemented it.
Thanks,
Sri.The XML/XSLT idea is probably your best bet. Years ago I created a custom
RTF generator (to create nice-looking documents from a CASE tool). It's
easy once you do two things:
(1) Hunt down the RTF specification (from Microsoft I think), and learn the
basic syntax.
(2) Create a Word document that looks like what you want and save it to RTF
as a baseline/reference.
Then, you'll be armed and dangerous -- especially if you know how to do
XSLT.
--
Cheers,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"Sri" <Sri@.discussions.microsoft.com> wrote in message
news:8B848583-4F7E-490F-9E77-95CD40C30072@.microsoft.com...
> 1. Is there a Microsoft Word or RTF delivery extension available for SQL
> Reporting Services?
> If not, is there any technique of producing the same with XML and XSLT?
> 2. To solve the security extension problem on a standard edition:
> I am thinking of using web client on a filter page on the web server to
> connect to the reporting server so that I don't bypass the web server when
> a
> URL access request comes thru.
> I mean, the URL for the report viewer won't be reporting server, instead
> it
> will be an aspx (filter) page within the web server. The filter on the web
> server will intercept and in turn impersonate a user on the report server
> and
> render a report in the report viewer.
> My question: I have not used web clients from web server before. Will it
> affect the performance of web server? Is the above theory make sense at
> all?
> I haven't implemented it.
> Thanks,
> Sri.
>|||Thanks Jeff. I will investigate.
"Jeff A. Stucker" wrote:
> The XML/XSLT idea is probably your best bet. Years ago I created a custom
> RTF generator (to create nice-looking documents from a CASE tool). It's
> easy once you do two things:
> (1) Hunt down the RTF specification (from Microsoft I think), and learn the
> basic syntax.
> (2) Create a Word document that looks like what you want and save it to RTF
> as a baseline/reference.
> Then, you'll be armed and dangerous -- especially if you know how to do
> XSLT.
> --
> Cheers,
> '(' Jeff A. Stucker
> \
> Business Intelligence
> www.criadvantage.com
> ---
> "Sri" <Sri@.discussions.microsoft.com> wrote in message
> news:8B848583-4F7E-490F-9E77-95CD40C30072@.microsoft.com...
> > 1. Is there a Microsoft Word or RTF delivery extension available for SQL
> > Reporting Services?
> >
> > If not, is there any technique of producing the same with XML and XSLT?
> >
> > 2. To solve the security extension problem on a standard edition:
> >
> > I am thinking of using web client on a filter page on the web server to
> > connect to the reporting server so that I don't bypass the web server when
> > a
> > URL access request comes thru.
> > I mean, the URL for the report viewer won't be reporting server, instead
> > it
> > will be an aspx (filter) page within the web server. The filter on the web
> > server will intercept and in turn impersonate a user on the report server
> > and
> > render a report in the report viewer.
> >
> > My question: I have not used web clients from web server before. Will it
> > affect the performance of web server? Is the above theory make sense at
> > all?
> > I haven't implemented it.
> >
> > Thanks,
> > Sri.
> >
>
>|||Hi,
You can check http://officewriter.softartisans.com/officewriter-250.aspx
for the first question.
creating a 'filter' will not affect performance
--
Message posted via http://www.sqlmonster.com
Friday, February 24, 2012
Microsoft SqlServer Desktop Engine Connection Problem
i installed the MSDE2000A on server and i tried to connect from client machine through vb Application using connection string. Server anad client are in LAN. but Some systems able to connect and some systems are unable to connect.
i am getting the error:
"SqlServer does not exist or access denied "
for non connected machines.
the server is listening from these machines. but not connecting to MSDE.
can anyone give me solution what may be the cause.Ensure the System DSN used and login must have required privileges to connect to SQL server.
What is the authentication mode used?
Try:
1. Make sure the SQL server is on
2. Ping the server machine
3. Try connecting to the IP address rather than the server name
Review information from this KBA (http://support.microsoft.com/default.aspx?scid=kb;en-us;328306) for potential causes and resolve it.|||i am using user authentication mode.
i have set DISABLENETWORKPROTOCOLS=0
i have done pinging through IP Address.
i am able ping database.
after doing all these test .. still getting same error...
is there any other possibilities....
Originally posted by Satya
Ensure the System DSN used and login must have required privileges to connect to SQL server.
What is the authentication mode used?
Try:
1. Make sure the SQL server is on
2. Ping the server machine
3. Try connecting to the IP address rather than the server name
Review information from this KBA (http://support.microsoft.com/default.aspx?scid=kb;en-us;328306) for potential causes and resolve it.|||Review points listed in the knowledgebase article.
i am using user authentication mode.
SQL Server does have only 2 modes - Windows only or mixed. Which on e is yours?
i have set DISABLENETWORKPROTOCOLS=0
Don't know about this protocol in SQL, it should be named-pipes, TCP/ip or Multi-protocol. From Start--> programs --> goto MSSQLServer program group and select Server network utility and check for enabled protocols.
i am able ping database.
How can you do that in SQL?|||mine is MIXEDMODE.
this is obtained by setting parameter SECURITYMODE=SQL
i am sorry to tell u that i ping to database.
not database... it is server.
i am able to ping to server where i installed MSDE.
Originally posted by Satya
Review points listed in the knowledgebase article.
SQL Server does have only 2 modes - Windows only or mixed. Which on e is yours?
Don't know about this protocol in SQL, it should be named-pipes, TCP/ip or Multi-protocol. From Start--> programs --> goto MSSQLServer program group and select Server network utility and check for enabled protocols.
How can you do that in SQL?|||I'm probably being silly, but could you have installed SQL as a named server and tried to access it as a default (unnamed) server?
-PatP|||Check for any h/w issues on server installed by referring to event viewer log.
i am getting the error:
"SqlServer does not exist or access denied "
for non connected machines.
the server is listening from these machines. but not connecting to MSDE.
can anyone give me solution what may be the cause.Ensure the System DSN used and login must have required privileges to connect to SQL server.
What is the authentication mode used?
Try:
1. Make sure the SQL server is on
2. Ping the server machine
3. Try connecting to the IP address rather than the server name
Review information from this KBA (http://support.microsoft.com/default.aspx?scid=kb;en-us;328306) for potential causes and resolve it.|||i am using user authentication mode.
i have set DISABLENETWORKPROTOCOLS=0
i have done pinging through IP Address.
i am able ping database.
after doing all these test .. still getting same error...
is there any other possibilities....
Originally posted by Satya
Ensure the System DSN used and login must have required privileges to connect to SQL server.
What is the authentication mode used?
Try:
1. Make sure the SQL server is on
2. Ping the server machine
3. Try connecting to the IP address rather than the server name
Review information from this KBA (http://support.microsoft.com/default.aspx?scid=kb;en-us;328306) for potential causes and resolve it.|||Review points listed in the knowledgebase article.
i am using user authentication mode.
SQL Server does have only 2 modes - Windows only or mixed. Which on e is yours?
i have set DISABLENETWORKPROTOCOLS=0
Don't know about this protocol in SQL, it should be named-pipes, TCP/ip or Multi-protocol. From Start--> programs --> goto MSSQLServer program group and select Server network utility and check for enabled protocols.
i am able ping database.
How can you do that in SQL?|||mine is MIXEDMODE.
this is obtained by setting parameter SECURITYMODE=SQL
i am sorry to tell u that i ping to database.
not database... it is server.
i am able to ping to server where i installed MSDE.
Originally posted by Satya
Review points listed in the knowledgebase article.
SQL Server does have only 2 modes - Windows only or mixed. Which on e is yours?
Don't know about this protocol in SQL, it should be named-pipes, TCP/ip or Multi-protocol. From Start--> programs --> goto MSSQLServer program group and select Server network utility and check for enabled protocols.
How can you do that in SQL?|||I'm probably being silly, but could you have installed SQL as a named server and tried to access it as a default (unnamed) server?
-PatP|||Check for any h/w issues on server installed by referring to event viewer log.
Microsoft SQL Server, Error: 10053
O get this error when trying to connect to my database. About 5 minutes ago it was working fine...seems to go in and out. We have native client installed in this server as well so not sure why I keep having connection issues. I tried both Windows Authentification and local sql account, both are very choppy, sometimes works sometimes doesn't.
TITLE: Connect to Server
Cannot connect to BG-SQL2005.
ADDITIONAL INFORMATION:
A connection was successfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error: 0 - An established connection was aborted by the software in your host machine.) (Microsoft SQL Server, Error: 10053)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=10053&LinkId=20476
BUTTONS:
OK
I am also getting this error when trying to ALTER one of my stored procs :
A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)
Mostlikely the server is closing the connections for some reason, possibly the client does not have permission to access some sqlserver resources, e.g. database, sp, xp. We might get more hint as to why if you could share out the sql server ERRORLOG.|||Here are my logs:http:
aprint screens of various errors I have received on my remote SQL Server 2005 (Enterprise version):
http:
issue resolved, reinstalled SQL Server 2005 completely
thanks for the inputs!
Subscribe to:
Posts (Atom)