How many types replication in SQL Server

As Salamo Alaikum Wa Rahmatullah

There are three types of Replication in SQL Server 2012/2014.

1.Snapshot Replication
2. Transaction Replication
3. Merge Replication

--
Ma Asalaam
Passion 4 Oracle

Fixed Asset - Basic

As Salamo Aalaikum wa Rahmatullah

In simple terms, an asset is a resource having future economic benefit owned by an entity. Future benefit could mean in terms of contributing to the profit for profit oriented organizations and providing services for non-profit oriented organizations.

Assets are formally controlled and managed within larger organizations via the use of asset tracking tools. These monitor the purchasing, upgrading, servicing, licensing, disposal etc., of both physical and non-physical assets.

Assets may be classified in many ways. 

1. Current assets (Current deposits, Inventory)
2. Long-term investments (Investments in securities)
3. Fixed assets (land,buildings, machinery, furniture, tools)
4. Intangible assets (patents, copyrights, franchises, goodwill, trademarks)


Fixed assets are those that are expected to keep on providing benefit for more than one year. Some common examples are: scientific equipment, office equipment, photo copiers, land and buildings, vehicles, Machinery, Property held for Investment purpose.

--
Ma Asalaam
Passion 4 Oracle

Oracle Inventory - Basic

As salamo alaikum wa rahmatullah

Oracle Applications uses multiple types of organizations to build the business

execution structure. At the top of the structure is the accounting set of books

SOB), defined in the General Ledger. Next, different types of organizations are

used to further define the organization structure and relationships. All organizations are defined and updated with the Define Organization form.

Set of Books: A General Ledger SOB, linked to the inventory organization,

controls the financial accounting of inventory transactions. A SOB is made up

of a chart of accounts, a financial calendar, and a currency. 
The general ledger secures transactions (journal entries, balances) by SOB.

Legal Entity. A legal entity organization defines the tax and fiscal reporting

level. The legal entity represents the legal company.

Operating Unit: An operating unit organization defines the Purchasing, Order

Entry, Accounts Payable and Accounts Receivable level of operation. An operating unit may span multiple manufacturing facilities, distribution points and sales offices, or it may be limited to a single site.

Inventory Organization: Two flavors of inventory organizations are found in

Oracle Applications. They are defined the same, and both are assigned a set

of books, a legal entity organization, an operating unit organization, and a

location. An item master organization is used for item number maintenance and

validation. This master organization serves as a data repository storing items

and item attributes, master level categories and category sets, master level

cross references, and numerous data defaults. On-hand balances, inventory

movements, and other on-going inventory activities are not performed in an item master organization. Generally, the master organization is used as the

validation organization for Purchasing and Order Entry. It is recommended

that a single item master organization be defined, even in multiple organization,

multiple sets of books environments.

In addition to the item master organization there are one or more non-master

inventory organizations. Like the item master inventory organization, the

non-master organizations are assigned a set of books, a legal entity organization and an operating unit organization. The non-master inventory organization points to a master organization and looks to the master organization for master level item attributes, master level categories, and other master level controlled data.

Note that each organization has its own set of books/legal entity/operating unit

relationship, so inventory organizations with differing SOB’s or operating units

may share the same master organization.

These non-master inventory organizations are the execution level organizations.

They hold on-hand balances and transaction history. Here is where inventory

users execute their daily activities, such as receiving and issuing material,

performing cycle counts, and viewing material availability and transaction

history. A single organization therefore generally represents a single

manufacturing site or distribution center.

Locations: A location code is an address. Each inventory organization must

be assigned at least one location code.

Subinventories: A subinventory is used as a holding point for on-hand

inventory and generally represents a stockroom, stocking area or cage used

for storing material. Subinventories are defined within inventory

organizations. An inventory organization may have any number of

sub inventories, and an asset account is assigned to each sub inventory.

Since the subinventory entity is logical, as there is not an address or

physical location description associated with it, clients may define

sub inventories for any physical or logical grouping of inventory

Stock Locators: Stock locators are an optional entity that may be used to

represent physical locations within a subinventory. You may choose to use

stock locators for selected subinventories or selected items within selected

subinventories. If locators are used, subinventory and locator track on-hand

balances. Therefore, if locators are defined to represent a shelf within a

stockroom, on-hand balances on the system would show the item and quantity

down to the physical location within the facility.

Oracle Inventory uses a key flexfield for stock locators. This presents a few

limitations for its use. Only one locator flexfield definition is allowed per

install. Therefore, if the stockroom (subinventory) wants to track material

by row, bin and shelf, it will likely define a three-segment flexfield with

segments for row, bin, and shelf. If locators are desired for another

sub inventory, even in another organization, the structure will again be 3

segments for row, bin and shelf. In addition to this limitation, locators

must be unique within an organization; you cannot use the same locator in

different sub inventories within an organization, but you can use the same locator in sub inventories in a different organization.

--
Ma Asalaam
Passion 4 Oracle

Create Database manually in SQL SERVER

As salamo alaikum wa rahmatullah


Create database Food
ON
(
 Name=FoodData1,
 Filename='C:\ManualDB\SQLSERVER12.0\DATA\FoodData1.mdf',
 Size=10MB,
 MaxSize=unlimited,
 filegrowth=1GB
)
Log ON
(
 Name=FoodLog1,
 Filename='C:\ManualDB\SQLSERVER12.0\DATA\FoodData1_log.ldf',
 Size=10MB,
 MaxSize=unlimited,
 filegrowth=1024MB
)

--

Ma Asalaam

Passion 4 Oracle

Creating Data Block using Package and Procedure in Oracle 10g

As salamo alaikum wa rahmatullah

create table tbl_mst_student (roll number(3),
name varchar2(50),course varchar2(50))

create or replace package mypack
is
type student_rec is record (stud_id tbl_mst_student.roll%type,sname tbl_mst_student.name%type,scourse tbl_mst_student.course%type);
type stub is table of student_rec index by binary_integer;
procedure stuqry(data IN OUT stub);
procedure stuins(data IN stub);
end mypack;


create or replace package body mypack
is
procedure stuqry(data IN OUT stub)
is 
i number;
cursor cstudent is select * from tbl_mst_student;
begin
open cstudent;
i:=1;
loop
fetch cstudent into data(i).stud_id,data(i).sname,data(i).scourse;
exit when cstudent%notfound;
end loop;
close cstudent;
end stuqry;

procedure stuins(data IN stub)
is
i number;
ct number;
begin
ct:=data.count;
for i in 1..ct loop 
insert into tbl_mst_student values(data(i).stud_id,data(i).sname,data(i).scourse);
commit;
end loop;
end stuins;
end mypack;
/



select * from tbl_mst_student

Ma Asalaam
---------------
Passion 4 Oracle

TYPE EXAMPLE IN ORACLE 11G

As salamo alaikum wa rahmatullah


CREATE OR REPLACE TYPE PersonObj AS OBJECT (
  first_name  VARCHAR2(50),
  last_name   VARCHAR2(50),
  date_of_birth  DATE,
  MEMBER FUNCTION getAge RETURN NUMBER
)

create or replace type body PersonObj AS
Member Function getAge Return Number AS
Begin
    Return Trunc(Months_Between(Sysdate,date_of_birth)/12);
    End getAge;
End;

create table people
(
id number(2), person PersonObj);



INSERT INTO people
VALUES (1, PersonObj('John','Doe',
        TO_DATE('01/01/1999','DD/MM/YYYY')))
        
COMMIT

DECLARE
  v_person  PersonObj;
BEGIN
  v_person := PersonObj('Jane','Doe',
              TO_DATE('01/01/1999','DD/MM/YYYY'));
  INSERT INTO people VALUES (2, v_person);
  COMMIT;
END;


SELECT p.id,
       p.person.first_name,
       p.person.getAge() age
FROM   people p;

----------------

output 

------------

--

Ma asalaam

Passion 4 Oracle

EXAMPLE OF AUTO INCREMENT COLUMN IN ORACLE

AS SALAMO ALAIKUM WA RAHMATULLAH



CREATE TABLE TBL_ITEM
(
ITM_ID NUMBER(5),
ITM_CODE VARCHAR2(30) UNIQUE NOT NULL,
ITM_DESC VARCHAR2(250),
ITM_PRICE NUMBER(10,3),
ITM_QTY NUMBER(3),
ITM_CRT_DT DATE,
ITM_UPD_DT DATE,
ITM_IS_DEL CHAR(1),
PRIMARY KEY(ITM_ID),
CHECK (ITM_IS_DEL IN ('Y','N'))
)


CREATE SEQUENCE SEQ_TBL_ITM_ID START WITH 1 INCREMENT BY 1


CREATE OR REPLACE TRIGGER TRG_ITM_ID
BEFORE INSERT ON TBL_ITEM
FOR EACH ROW
BEGIN
    SELECT SEQ_TBL_ITM_ID.NEXTVAL INTO :NEW.ITM_ID FROM DUAL;
END;
/

INSERT INTO TBL_ITEM (ITM_CODE,ITM_DESC,ITM_PRICE,ITM_QTY,ITM_CRT_DT,ITM_UPD_DT,ITM_IS_DEL)
VALUES('LS-GC17103','GRIFFIN FLAT AUX CABLE CONNECT + PLAY',5.000,10,SYSDATE,SYSDATE,'N')

SELECT * FROM TBL_ITEM


--
MA ASALAAM
PASSION 4 ORACLE