Monday 27 May 2013

SAP Business one Modules e-Learning





These e-Learning components have been developed to provide you with the basic product understanding of SAP Business One release 8.8.
It’s setup to give you a good understanding of the business processes within SAP Business One, not just task execution.  This e-Learning is covering the key area’s in the standard product training of SAP Business One release 8.8 and is only covering  ‘global’ standard functionality, localization specific functionality is not included.
If you have any questions or feedback on these sessions, feel free to use the SAP Business One training forum that you can access  here

Its an link where we can easy to know the modules of  sap business one!!!

Link
http://www.richardduffy.com/sap-business-one-version-elearning-modules

Its very useful for those who doesn't  have any idea about SAP Business one.



Sunday 26 May 2013

SSIS First simple Project

Microsoft SQL Server 2008 Integration Services (SSIS) is a platform for building high performance data integration solutions, including the extraction, transformation, and loading (ETL) of packages for data warehousing. SSIS is the new name assigned to the component formerly branded as Data Transformation Services (DTS).

SSIS (SQL Server Integration Services) is an upgrade of DTS (DataTransformation Services), which is a feature of the previous version ofSQL Server. SSIS packages can be created in BIDS (Business IntelligenceDevelopment Studio). These can be used to merge data from heterogeneousdata sources into SQL Server. They can also be used to populate datawarehouses, to clean and standardize data, and to automateadministrative tasks.















SQL Version Details


SQL Server Released Versions and details


Simple Database concepts

System Databases
  1. Master: composed of system tables that keep track of server installation as a whole and all other databases that are eventually created. Master DB has system catalogs that keep info about disk space, file allocations and usage, configuration settings, endpoints, logins, etc.
  2. Model: template database. Gets cloned when a new database is created. Any changes that one would like be applied by default to a new database should be made here
  3. Tempdb: re-created every time SQL Server instance is restarted. Holds intermediate results created internally by SQL Server during query processing and sorting, maintaining row versions, etc. Recreated from the model database. Sizing and configuration of tempdb is critical for SQL Server performance.
  4. Resource [hidden database]: stores executable system objects such as stored system procedures and functions. Allows for very fast and safe upgrades.
  5. MSDB: used by the SQL Server Agent service and other companion services. Used for backups, replication tasks, Service Broker, supports jobs, alerts, log shipping, policies, database mail and recovery of damaged pages.
Database Files
  1. Primary data files: every database must have at least one primary data file that keeps track of all the rest of the files in the database. Has the extension .mdf.
  2. Secondary data files: a database may have zero or more secondary data files. Has the extension .ndf.
  3. Log files: every database has at least one log file that contains information necessary to recover all transactions in a database. Has the extension .ldf.
Creating a Database
  1. New user database files must be at least 3 MB or larger including the transaction log
  2. The default size of the data file is the size of the primary data file of the model database (2 MB) and the default size of the log file is 0.5 MB
  3. If LOG ON is not specified but data files are specified during a create database, the size of the log file is 25% of the sum of the sizes of all the data files.
Expanding or Shrinking a Database
  1. Automatic File Expansion:
  1. The file property FILEGROWTH determines how automatic expansion happens
  2. File property MAXSIZE sets the upper limit on the size
  • Manual File Expansion: use the ALTER DATABASE command with the MODIFY FILE option to change the SIZE property to increase the database file size
  • Fast File Initialization: adds space to the data file without filling the newly added space with zeros. New disk content is overwritten as new data is written to the files. Security is managed through Windows security setting SE_MANAGE_VOLUME_NAME
  • Automatic Shrinkage:
    1. Same as doing DBCC SHRINKDATABASE (dbname, 25). Leave 25 % free space in the database after the shrink
    2. Thread performs autoshrink as often as 30 minutes, very resource intensive
  • Manual Shrinkage: use DBCC SHRINKDATABASE if you want to shrink.
  • I highly recommend not to shrink the database.

  • Filegroups
    1. Can group data files for a database into filegroups for allocation and administration purposes.
    2. Improves performance by controlling the placement of data and indexes into specific filegroups on specific drives or volumes.
    3. Filegroup containing the primary data file is called the primary filegroup, there is only one primary filegroup.
    4. Default filegroup: there is at least one filegroup with the property of DEFAULT, can be changed by DBA.
    5. Use cases when -not- to use filegroups:
    1. DBA might decide to spread out the I/O for a database: easiest way is to create a database file on a RAID device.
    2. DBA might want multiple files, perhaps to create a database that uses more space than is available on a single drive: can be accomplished by doing CREATE DATABASE with a list of files on separate drives
  • Use cases when you want to use filegroups:
    1. DBA might want to have different tables assigned to different drives or to use the table and index partitioning feature in SQL Server.
  • Benefits:
    1. Allows backup of parts of the database.
    2. Table is created on a single filegroup, allows for backup of critical tables by backing up selected filegroups.
    3. Same for restoration. Database can be online as soon as primary filegroup is restored, but only objects on the restored filegroups will be available.

    Difference between SQL SERVER 2000,2005 and 2008

    SQL SERVER 2000:
     

    1.Query Analyser and Enterprise manager are separate.
    2.No XML datatype is used.
    3.We can create maximum of 65,535 databases.
    4.Cant compress the tables and indexes.

    5.Datetime datatype is used for both date and time.
    6.No varchar(max) or varbinary(max) is available.
    7.No table datatype is included.
    8.No SSIS is included.
    9.CMS (Cenntral Management Server) is not available.
    10.PBM (Policy Based Management) is not available.
    11.High Availability Clustering or Log Shipping require Enterprise Edition. Expensive hardware.


    SQL SERVER 2005:

    1.Both are combined as SSMS(Sql Server management Studio).
    2.XML datatype is introduced.
    3.We can create 2(pow(20))-1 databases.
    4.Exception Handling
    5.Varchar(Max) data type
    6.DDL Triggers
    7.DataBase Mirroring
    8.RowNumber function for paging
    9.Table fragmentation
    10.Full Text Search
    11.Bulk Copy Update
    12.Cant encrypt the entire database.
    13.Can Compress tables and indexes.(Introduced in 2005 SP2)
    14.Datetime is used for both date and time.
    15.Varchar(max) and varbinary(max) is used.
    16.No table datatype is included.
    17.SSIS is started using.
    18.CMS is not available.
    19.PBM is not available.

    20. High Availability Clustering, Database Mirroring or Log Shipping available in Standard Edition. Database Mirroring can use cheap hardware. 

    SQL SERVER 2008:
     



     
    1.Both are combined as SSMS(Sql Server management Studio).
    2.XML datatype is used.
    3.We can create 2(pow(20))-1 databases.
    4.Exception Handling
    5.Varchar(Max) data type
    6.DDL Triggers
    7.DataBase Mirroring
    8.RowNumber function for paging
    9.Table fragmentation
    10.Full Text Search
    11.Bulk Copy Update
    12.TDE (Transparent Data Encryption) to encrypt the entire database introduced in 2008.
    13.Can compress tables and indexes.
    14.Date and time are separately used for date and time datatype,spatial and timestamps with internal timezone is used.
    15.Varchar(max) and varbinary(max) is used.
    16.Table datatype introduced.
    17.SSIS avails in this version.
    18.Central Management Server(CMS) is Introduced.
    19.Policy based management(PBM) server is Introduced.

    20. Auditing - monitoring of data access.
    21. Resource Governor. Restrict users or groups from consuming high levels or resources. 
    22. Activity monitorconsolidates this information by detailing running and recently executed processes, graphically.
    23. Backup compression

    Sql DBA concepts

    CORE DBA CONCEPTS of SQL SERVER 

    The History of SQL Server and Relational Databases
    Relational database history and SQL Server and ANSI Standards
    Relation between Application and Database

    Overview of Windows Concepts
    Role of Windows Operating System in SQL Server Administration
    Windows Operating System Basics
    Overview of Built-in accounts, Service accounts
    Overview of Users and Groups
    Overview of Services

    Overview of Network Concepts
    Role of Network in SQL Server Administration
    Basics of Network Concepts, Network drives
    Introduction to Work Group, Domain
    Introduction to Active Directory Services (ADS)
    Introduction to Domain Controller (DC)
    Introduction to Domain Naming Server (DNS)
    Introduction to Dynamic Host Configuration Protocol (DHCP)

    SQL Server Editions
    Different Editions of SQL Server and their features
    Tools, Utilities and Components of SQL Server
    Choosing Appropriate SQL Server Edition
    Licensing issues with SQL Server

    Installing and Configuring SQL Server
    Pre-installation steps and Installation SQL Server
    Configuring the run-time SQL Server system
    Patching SQL Server - Service Packs, Hot fixes
    Finding Right Service Pack or Hot Fix to be installed
    Problems and precautions involved in SQL Server Patching
    Upgradation from SQL server 2000/2005 to 2008 and Migration



    SQL Server Databases
    System Databases Master, MSDB, Model, Temp and Resource
    Creating User Databases

    SQL Server Data Storage Management
    SQL Server File Management Architecture
    Creating Database Files
    Creating SQL Server Log Files
    Using SQL Server File groups
    Moving Files or File Groups

    SQL Server Security Management
    Windows Security Management for the server
    Windows Authentication Model
    SQL Server Rights and Role Management
    SQL Server Authentication and Mixed Mode Authentication
    Logins
    Mapping roles and databases to logins

    SQL Server Backup & Recovery
    Overview of SQL Server Backup and Recovery
    Full Backups, Incremental Backups and Log Backups
    Overview of Backupset, Backupmediaset, Backupmediafamily
    Recovery Models in SQL Server
    Restoring a SQL Server Database
    Difference between Restore and Recovery
    Performing Recovery
    Backup and Restore through third party tools like Redgate

    Overview of Testing, Development, Staging and Production Server Environments
    Designing Production server from Test Server and Vice versa
    Naming Convention for servers(Compliant to Industry Standards)

    SQL Architecture and Memory
    Physical Database Architecture
    Relational (Logical) Database Architecture
    Memory Management

    Physical Database Engine Architecture
    Pages and Extents
    Physical Database Files and Filegroups
    Space Allocation and Reuse
    Table and Index Architecture

    Relational Database Engine Architecture
    Query Process Architecture
    Memory Architecture
    Managing Memory for Large Databases
    Thread and Task Architecture
    Understanding Non-Uniform Memory Access (NUMA)
    Buffer Management
    Distributed Query Architecture

    Management
    Policy Management
    Configuring Database Mail
    SQL Server Logs
    Distribution Transaction Coordinator
    Data Collection and Resource Governor (In 2008 only)

    SQL Server Agent
    Jobs and Job Activity Monitor
    Alerts
    Operators
    Proxies
    Error Logs

    SQL Server Job Scheduling
    Common Database Scheduled Jobs
    Setting SQL Server and server alerts thresholds
    Creating Customized Error Conditions
    Scheduling multi-step job streams
    Troubleshooting of failed Jobs

    Maintenance Plans
    Overview of Maintenance Plan
    Tasks in Maintenance Plans
    Creation of Maintenance Plan
    Monitoring Maintenance Plan
    Troubleshooting of failed Jobs created by Maintenance Plan

    DBCC Commands
    Introduction to Database Console Commands
    Maintenance DBCC Commands
    Informational DBCC Commands
    Validation DBCC Commands
    Miscellaneous DBCC Commands

    Metadata
    Understanding Metadata and its importance
    System Tables and Dynamic Management Views(DMV), System Stored Procedures
    Querying System Tables, DMV’s and Stored Procedures to obtain Metadata
    Role of Master and MSDB in maintaining Metadata

    SQL Server Configuration Manager (SSCM)
    Managing Services with SQL Server
    Starting and Stopping Instance from SSCM
    Starting and Stopping SQL Agent from SSCM
    Configuring Protocols, Ports and Aliases in SSCM
    Introduction to SSIS and DTS
    Using DTS to export and Import SQL Server Table data


    HIGH AVAILABILITY
    Overview of Disaster Recovery and High Availability solutions
    Disaster types
    Recovery solutions
    Standby database overview
    High Availability

    SQL Server Database Replication
    Replication Components and Replication Terminology 
    Replication Topologies – Central Publisher, Central Publisher with Remote Distributor, Central 
    Subscriber, Central Distributor, Publishing Subscriber
    Types of Replication – Snapshot Replication, Merge Replication and Transactional Replication,
    Peer-Peer Replication
    Configuring Replication – Merge Replication , Transactional Replication, Snapshot Replication

    Log Shipping
    Log Shipping Overview
    Log Shipping Deployment and Administration
    Configuring Log Shipping using Management Studio and T-SQL
    Monitoring Log Shipping

    Database Mirroring
    Important:
    Introduction
    Database Mirroring Overview
    Database Mirroring Dynamics
    Database Mirroring Availability Scenarios
    Implementing Database Mirroring
    Database Mirroring and High Availability Technologies
    Conclusion

    SQL Server Clustering
    Overview of Clustering
    Hardware and Software Requirement for Clustering.
    Installing and Configuring VMWARE for building virtual environment
    Installing Windows 2008 clustered environment
    Installing SQL Server Active Passive (Cluster) on Windows 2008 clustered environment
    Adding a node to existing SQL Server cluster
    How to patch SQL Server Clustered Environment by applying SP1 on SQL Server 2008 cluster instance.
    What is SQL Server Active Active Clustering
    Installing SQL Server Active Active Clustering
    Installing Analysis Services (SSAS) on a clustered environment
    Installing / Configuring Integration Services (SSIS) on a clustered environment
    Remove a node from a running clustered instance
    Un-installing SQL Server Cluster

    PERFORMANCE TUNING


    SQL Architecture and Memory
    Physical Database Architecture
    Relational (Logical) Database Architecture
    Memory Management

    Table and Index Structure
    Partitioning Tables
    Partitioning Index
    Clustered Index
    Table Scan and Index Scan
    Index Seek vs. Index Scan

    Locking and Concurrency
    Locking Mechanism
    Types of Locks
    Isolation Levels in SQL Server
    Live Lock, Dead Lock and Blocking detection and resolution
    Killing processes at OS level

    Query Optimization and Programming Efficiency
    T-SQL Tuning
    Query execution Plan
    Estimated Execution Plan

    SQL Server performance counters
    Understanding different Performance Counters
    Processor:% Processor Time
    PhysicalDisk:Avg.Disk Queue Length
    PhysicalDisk: Disk Read Bytes/sec and Physical Disk: Disk Write Bytes/sec

    Server Performance and Activity Monitoring
    Perform monitoring tasks with Windows tools
    Create SQL Server database alerts with Windows tools
    Perform monitoring tasks with SQL Server Management Studio
    Perform monitoring tasks with SQL Trace by using Transact-SQL stored procedures
    Create and modify traces by using SQL Server Profiler
    Start, pause, and stop traces by using SQL Server Profiler
    Open traces and configure how traces are displayed by using SQL Server Profiler
    Replay Traces by using SQL Server Profiler
    Create, modify, and use trace templates by using SQL Server Profiler
    Use SQL Server Profiler traces to collect and monitor server performance



    Database Engine Tuning Advisor
    Create Workloads
    Tune a Database
    View Tuning Output
    Implement Tuning Recommendations
    Create XML Input Files
    Perform Exploratory Analysis
    Review, Evaluate, and Clone Tuning Sessions

    Performance Tools and Monitoring
    SP_TRACE_SETFILTER (T-SQL) for tracking engine process events
    System Monitor for tracking resource usage
    Activity Monitor in SSMS to display Processes running on an instance, Blocked Processes,Locks,User activity
    System Stored Procedures
    DBCC(T-SQL)
    Built-in-Functions(T-SQL)
    Trace Flags(T-SQL)
    SQL Server Profiler
    Resource Governor
    Data Collection

    SQL Server performance tips
    Proactive Actions that Ensure Optimized SQL Server Performance
    Establishing a Smart SQL Server Monitoring Plan

    Saturday 25 May 2013

    To Take a Backup of all Stored Procedures in Sql Server Database

    Back up the All Stored procedures in the Database with one click.

    1. Right Click the  Database--->Task--->Generate Scripts



    2. when you click the Generate Script the pop window will display and you have to select the


    •   Select Specific Database objects
    •    On that Select the Stored Procedures

       











    3. You have to select the save to file mode


    • Single file per object
    • Directory name where to save the Stored procedure path.




    4.
          The process completed by Clicking the next button.



    I hope you will save some time by doing this method.