• Introducing Dark Mode! Switch by clicking on the lightbulb icon next to Search or by clicking on Default style at the bottom left of the page!

Sql Serveur

JohnBlaze

Member
Well well

For those who working with OW Xe and Sql server 7
What am i suppose to do with Sql 7 and One world
i mean JDE will create, manage and whatever itself
the only thing i have to do is learn backup files
or what ????
i dont have to create tables, views or query ????

If somebody is working with it can you tell me what (in some details)
you do with sql ...

Thx
 

ronnet

Active Member
It is supposed that you will not to do anything in SQL, but
I can tell that you will find it very useful usin SQL very often.

You are not going to need to create OneWorld tables, or indexes in SQL Server,
OneWorld does it for you when you generate a table
but if you are going to desing a SQL script that gathers some data from
couple of OneWorld tables, maybe will be useful to create it directly in SQL.

Mostly I use SQL for Queries among tables.

Let say you need to pass all the data of the accounting ledger from production,
the fastest way to do it will be using SQL.

insert into JDE_CRP.crpdta.f0911 select * from JDE_PRODUCTION.proddta.f0911

Hope this gives you an idea why you will need SQL.

Ronnet Patino
OneWorld Developer
Noritex - Panama

Ronnet Patino
OneWorld Developer
Noritex - Panama
 

Ray Justus

Reputable Poster
Ronnet,

You had better be careful if you use this SQL approach. It is unlikely that your account IDs are the same in both environments. All related tables must be copied, i.e., F0901, F0902, F0911 and many more. JDE has instructions on the steps required to update the Prototype (CRP) environment with Production (PROD) data.

Ray W. Justus
Kitchell Corporation
1707 East Highland Avenue, Suite 100
Phoenix, AZ 85016-4679
(602) 631-6157
mailto: rjustus@kitchell.com

It is supposed that you will not to do anything in SQL, but
I can tell that you will find it very useful usin SQL very often.

You are not going to need to create OneWorld tables, or indexes in SQL Server,
OneWorld does it for you when you generate a table
but if you are going to desing a SQL script that gathers some data from
couple of OneWorld tables, maybe will be useful to create it directly in SQL.

Mostly I use SQL for Queries among tables.

Let say you need to pass all the data of the accounting ledger from production,
the fastest way to do it will be using SQL.

insert into JDE_CRP.crpdta.f0911 select * from JDE_PRODUCTION.proddta.f0911

Hope this gives you an idea why you will need SQL.

Ronnet Patino
OneWorld Developer
Noritex - Panama

Ronnet Patino
OneWorld Developer
Noritex - Panama
--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=OW&Number=8612
 

Larry_Jones

Legendary Poster
John,

are you in a Sales situation at the moment with JDE?

It sounds like someone is telling you and/or your management that you don't need a DBA. That may be true if your configuration is 10 users - Financials only. For larger implementations you will find that Databases still need to be maintained, S/W patches need to be analyzed and applied, and DBAs / programmers are still called on to do 'magic' to undo user screwups. When the fecal matter hits the fan the guy who sold you the software "that runs itself" will no longer be around :)

Larry Jones
ljones@wagstaff.com
OneWorld B733.1, SP 11.3
HPUX 11, Oracle SE 8.1.6
SandBox: OneWorld XE SP13
 

Ray Justus

Reputable Poster
Who is John? Are you referring to me?

Ray W. Justus
Kitchell Corporation
1707 East Highland Avenue, Suite 100
Phoenix, AZ 85016-4679
(602) 631-6157
mailto: rjustus@kitchell.com

John,

are you in a Sales situation at the moment with JDE?

It sounds like someone is telling you and/or your management that you don't need a DBA. That may be
 

jdcmwilson

Well Known Member
I couldn't have said it better myself.

James
CNC Consultant





All views are expressly my own and in no way reflect those of my employer.
 
I can support Larry's post 150%. The Payroll system is notorious for
building work files and then hiccupping. Once the hiccup occurs, someone
that understands the files and how to manipulate them MUST clear the files
in order for Payroll to run. This is only one example of many that supports
the need for someone with some DBA experience.
 
I can support Larry's post 150%. The Payroll system is notorious for
building work files and then hiccupping. Once the hiccup occurs, someone
that understands the files and how to manipulate them MUST clear the files
in order for Payroll to run. This is only one example of many that supports
the need for someone with some DBA experience.
 
Top