Experience about resource consumption about migration SQL- server to MaxDB

Hi,
Has somebody experience about migration MS SQL server (running under MS Windows) to MaxDB (Linux). Right now DB size is 2TB and SAP system is used about 1000 SAP users. I need information how cpu- and memory- consumption will change. Otherwise which requirements have to make for target database especially SAPS and hardware design.
Mit freundlichen Grüssen
Andreas Sartor

Check
https://www.sdn.sap.com/irj/sdn/maxdb
--> "Ensuring a Successful Database Migration to SAP MaxDB"
I would book that service.
The people doing that have lots of experience in diagnosing possible problems before the migration and will give you a lot of useful tips.
Markus

Similar Messages

Quick Migrate: SQL Server database to Oracle

When I try Quick Migrate: SQL Server database to Oracle, I get the following error messages:
1. Locating source plugin...failed
2. Checking multi-schema privileges...Privilege 'CREATE ROLE" is not granted with admin option.
Error #1 I do not understand.
Error #2: I created the user as follows:
DROP USER GRAINTEST CASCADE
CREATE USER GRAINTEST
IDENTIFIED BY SQL
DEFAULT TABLESPACE SMARTSOFT_DATA
TEMPORARY TABLESPACE TEMP
QUOTA UNLIMITED ON SMARTSOFT_DATA
QUOTA UNLIMITED ON SMARTSOFT_INDEX
GRANT CONNECT,
RESOURCE,
CREATE ROLE,
CREATE VIEW,
CREATE SESSION,
ALTER ANY TRIGGER TO GRAINTEST
DROP ROLE R_GRAINTST
CREATE ROLE R_GRAINTST NOT IDENTIFIED
GRANT R_GRAINTST TO GRAINTEST
WITH ADMIN OPTION
Thanks
Murray

Murray,
Apologies for referring to the 1.5 documentation but the 2.1 documentation still has the same information about creating a user to hold the repository.
You initially reported 2 problems -
1. Locating source plugin...failed
2. Checking multi-schema privileges...Privilege 'CREATE ROLE" is not granted with admin option.
For the first error have you installed the necessary JDBC driver ? I have just installed SQL*Developer 2.1 on a new laptop and could successfully connect following the documentation steps -
Oracle® SQL Developer
User’s Guide
Release 2.1
2.5.2 Before Migrating From Microsoft SQL Server or Sybase Adaptive Server
To configure a Microsoft SQL Server or Sybase Adaptive Server database for
migration:
1. Ensure that the source database is accessible by the Microsoft SQL Server or
Sybase Adaptive Server user that is used by SQL Developer for the source
connection. This user must be able to see any objects to be captured in the
Microsoft SQL Server or Sybase Adaptive Server database; objects that the user
cannot see are not captured. For example, if the user can execute a stored
procedure but does not have sufficient privileges to see the source code, the stored
procedure cannot be captured.
2. Ensure that you can connect to the Microsoft SQL Server or Sybase Adaptive
Server database from the system where you have installed SQL Developer.
3. Ensure that you have downloaded the JTDS JDBC driver from
http://jtds.sourceforge.net/.
4. In SQL Developer, if you have not already installed the JTDS driver using Check
for Updates (on the Help menu), do the following:
a. Click Tools, then Preferences, then Database, then Third Party JDBC Drivers.
b. Click Add Entry.
c. Select the jar file for the JTDS driver you downloaded from
http://jtds.sourceforge.net/.
d. Click OK.
========
The second error is again documented in the 2.1 documentation -
5.99 Privilege Warning for Migration
This dialog box is displayed if you click Verify in the Quick Migrate box and the
database user for the connection does not have all privileges necessary for a
multischema migration. For multischema migrations, this user must granted the
RESOURCE role with the ADMIN option; and this user must also be granted the
CREATE ROLE, CREATE USER, and ALTER ANY TRIGGER privileges, all with the
ADMIN option.
If you are performing a single-schema migration, you can ignore this warning.
=====
Which errors are you now seeing and which user was used to hold the repository ?
If you are using GRAINTEST for the repository then create it using this syntax -
CREATE USER GRAINTEST IDENTIFIED BY password <=== change password as necessary
DEFAULT TABLESPACE users TEMPORARY TABLESPACE temp; <=== change tablespaces as necessary
GRANT CONNECT, RESOURCE, CREATE VIEW, CREATE PUBLIC SYNONYM TO
GRAINTEST WITH ADMIN OPTION;
GRANT ALTER ANY ROLE, ALTER ANY SEQUENCE, ALTER ANY TABLE, ALTER TABLESPACE,
ALTER ANY TRIGGER, COMMENT ANY TABLE, CREATE ANY SEQUENCE, CREATE ANY TABLE,
CREATE ANY TRIGGER, CREATE ROLE, CREATE TABLESPACE, CREATE USER, DROP ANY
SEQUENCE, DROP ANY TABLE, DROP ANY TRIGGER, DROP TABLESPACE, DROP USER, DROP ANY
ROLE, GRANT ANY ROLE, INSERT ANY TABLE, SELECT ANY TABLE, UPDATE ANY TABLE TO
GRAINTEST with admin option ;
then when making the migration make sure the Oracle connection is to this user.
Please update the thread with the errors you get after following these steps.
Regards,
Mike

Migrating SQL Server DB to Oracle DB - probably EASY answer

I completed the tutorial on migrating SQL Server DB to Oracle. When I try on my own database, it all migrated well except anything containing a datetime. When I run the oracle_ctl.bat file and view any of the log files, I see Record 1: Rejected - Error on table DBO_RIVERSIDEDB_NCWCD_TEST.TS6HOUR_TAIN, column DATE_TIME.
ORA-01843: not a valid month. Do I need to change the first line of the file set NLS_DATE_FORMAT=Mon dd YYYY HH:mi:ssAM ? In the .dat file created from the unload_script.bat, the data starts out 1275<EOFD>2007-05-11 00:00:00.000<EOFD>74.900000000000006<EOFD><EOFD><EORD>1275<EOFD>. So my questions is about the date_format - is that the same for all SQL Server databases or do I need to enter something based on MY database? I am definitely a newbie so this is probably a super easy question. Thanks so much for any help!

Hello,
There are two different date format in SQL Server.
1] DateTime : 2010-08-03 12:48:15.170
2] SmallDateTime: 2010-08-03 12:48:00
Both the date will be inserted in Oracle Date column.
Is there any automated way to generate datamove script to tackle these differences? I've around 200 tables to be migrated and there may be many such cases.
The issue with Oracle SQL Developer setting i.e. Tools >Preferences> (Under) Migration> Data Move Option, there are two masks we can specify, one for Date Mask and other for Timestamp. How can I set both of these for converting data into Date, not in timestamp.
Below is my .CTL file, none of below fields are timestamp, but since incoming data in in timestamp format, it is applying timestamp mask and eventually failing to insert data into table
load data
infile '[PARTSORDER].dat'
"str '<EORD>'"
into table admin.PARTSORDER
fields terminated by '<EOFD>'
trailing nullcols
ORDERID ,
GenDate "TO_TIMESTAMP(:GenDate, 'YYYY-MM-DD.HH24.MI.SS.ff3')",
Status "DECODE(:Status, CHR(00), ' ', :Status)",
StatusBy ,
StatusDate "TO_TIMESTAMP(:StatusDate, 'YYYY-MM-DD.HH24.MI.SS.ff3')",
Approved ,
ApprovedBy ,
ApprovedDate "TO_TIMESTAMP(:ApprovedDate, 'YYYY-MM-DD.HH24.MI.SS.ff3')",
TrackingNumber "DECODE(:TrackingNumber, CHR(00), ' ', :TrackingNumber)",
SVOther "DECODE(:SVOther, CHR(00), ' ', :SVOther)",
ShippedVia "DECODE(:ShippedVia, CHR(00), ' ', :ShippedVia)",
ShippedBy "DECODE(:ShippedBy, CHR(00), ' ', :ShippedBy)",
ShippedDate "TO_TIMESTAMP(:ShippedDate, 'YYYY-MM-DD.HH24.MI.SS.ff3')",
CompletedBy "DECODE(:CompletedBy, CHR(00), ' ', :CompletedBy)",
CompletedDate "TO_TIMESTAMP(:CompletedDate, 'YYYY-MM-DD.HH24.MI.SS.ff3')",
ORDERType "DECODE(:ORDERType, CHR(00), ' ', :ORDERType)",
RMAID ,
RMANumber "DECODE(:RMANumber, CHR(00), ' ', :RMANumber)",
BackOrdered ,
XORDERID ,
PARTSORDERSENT "DECODE(:PARTSORDERSENT, CHR(00), ' ', :PARTSORDERSENT)",
SHIPMENTID "DECODE(:SHIPMENTID, CHR(00), ' ', :SHIPMENTID)"
Any help in this regard will be highly appreciated!
Thanks
Vinod

Migrate SQL Server 7.0 to Oracle 8i - Any known issues??

Hi,
I am in the process of migrating SQL Server database to Oracle 8i for testing purpose. When I do migrate SQL Server database to Oracle 8i, am I doing any harm to the exiting SQL Server database? Would the users be able to use SQL Server database as usual?? Are there any known issues in this regard?
Please reply.
Thanks.
Ramesh

The Migration Workbench copys the information it requires from the source database and stores it in the Migration Workbench Repository, which is separate from the Source database. So, to answer your question, yes, the users can continue to use the SQL Server database. The data move may cause some system performance degradation. It may also be an idea to replicate the SQL Server database, in case any complication should arise.
Hope this helps
Dan

Migrating SQL Server 7.0 to Oracle 8i in Different Operating Systems

I am migrating SQL Server 7.0 Databases on NT to Oracle 8i on Sun 2.6. Is there is any other way other then Migration Workbench.
If Mig Workbench is OK. What are the steps to do Migration.
null

Hi,
You can perform this action with the Oracle Migration Workbench. Just install the Workbench on the same machine as your SQL Server database.
You can then configure the workbench to point to the oracle database on your Sun machine.
You can use the Oracle database on your Sun machine for both your destination database (the database to which you migrate your SQL Server schema and data) and workbench repository.
In order to do this you will need to configure a tnsnames.ora entry. The tool that will do this configuration for you should be started up at the end of the workbench installation. It is a fairly straightfoward process.
You then need to create a user in your oracle database that will store the workbench repository.
Once you have comleted these steps you will be able to migrate SQL Server on NT to Oracle on Sun.
It is exactly the same process as migrating to Oracle on NT except you are pointing the Workbench to Oracle on a Sun box.
Regards
John

Migrating SQL Server database to Oracle 8i - any known issues

Hi,
I am in the process of migrating SQL Server database to Oracle 8i for testing purpose.
When I do migrate SQL Server database to Oracle 8i, am I doing any harm to the exiting
SQL Server database? Would the users be able to use SQL Server database as usual?? Are
there any known issues in this regard?
Please reply.
Thanks.
Ramesh

Hi,
I am in the process of migrating SQL Server database to Oracle 8i for testing purpose.
When I do migrate SQL Server database to Oracle 8i, am I doing any harm to the exiting
SQL Server database? Would the users be able to use SQL Server database as usual?? Are
there any known issues in this regard?
Please reply.
Thanks.
Ramesh Hi Ramesh!
The Migration Workbench does not make any modifications to the SQL Server database. It only reads information from it. Your users should be able to use the SQL Server database as usual.
Please note however that if you migrate the data over to Oracle using the Migration Workbench and your users continue to enter/update data in the exiting SQL Server database then you may need to move all that data over again in order to have the most up to date data in the Oracle database.
thanks
- Garry

Migrating SQL Server 7 to O8i

Please refer to TAR # 2005705.995 for more details.
I am unable to migrate SQL Server 7.0 database into oracle 8i . While in the
capturing stage I get the following errors shown in the attachment . It hangs
while tyring to make indices. I tried aborting the operation but it wouldn't
let me do it . it says cannot abort the application.
After waiting for ages, I therfore use TASK MANAGER in NT I kill me OMWB
application.
I get plenty of EXECEPTION ERRORS failed to map tables and then it gets stuck while trying to create indices.
Please refer to TAR # 2005705.995 for more details.

Hi,
You can perform this action with the Oracle Migration Workbench. Just install the Workbench on the same machine as your SQL Server database.
You can then configure the workbench to point to the oracle database on your Sun machine.
You can use the Oracle database on your Sun machine for both your destination database (the database to which you migrate your SQL Server schema and data) and workbench repository.
In order to do this you will need to configure a tnsnames.ora entry. The tool that will do this configuration for you should be started up at the end of the workbench installation. It is a fairly straightfoward process.
You then need to create a user in your oracle database that will store the workbench repository.
Once you have comleted these steps you will be able to migrate SQL Server on NT to Oracle on Sun.
It is exactly the same process as migrating to Oracle on NT except you are pointing the Workbench to Oracle on a Sun box.
Regards
John

Where did the tutorial to migrate SQL Server go?

Hi,
There was a great tutorial on how to do this on:
http://st-curriculum.oracle.com/obe/db/hol08/sqldev_migration/mssqlserver/migrate_microsoft_sqlserver_otn.htm
Where did it go? I cannot get to this link anymore.
Thanks,
Scott

Welcome to the forum!
Whenever you post provide your 4 digit Oracle version.
>
There was a great tutorial on how to do this on:
>
On how to do what? Migrate sql server to what? To Oracle? To mysql?
Here is a link with info on using sql develoer to migrate from sql server to Oracle
http://www.oracle.com/technetwork/database/migration/sqlserver-095136.html
Here is a link with a doc on how to migrate sql server to mysql
http://www.oracle.com/us/corporate/press/1715479
You need to explain specifically what you are trying to do and what tools you are trying to do it with.

Migration sql server 2000 to oracle 9i

Hi
I migrate sql server 2000 to oracle 9i
when i capture Microsoft Sql Server it gives an error
oracle.dbtools.metadata.persistence.PersistenceException: ORA-04098: trigger 'MIGRATIONS.MD_PROJECTS_TRG' is invalid and failed re-validation
I try it again and it starts but it doesn't stop until clicking cancel or close
what is the wrong?
Thanks

Hi,
You are hitting a know issue using a repository created in 9.2.
To show this is the case do the following -
SQL> alter trigger MD_PROJECTS_TRG compile ;
Warning: Trigger altered with compilation errors.
SQL> show errors
Errors for TRIGGER MD_PROJECTS_TRG:
LINE/COL ERROR
3/9 PL/SQL: Statement ignored
3/20 PLS-00905: object MIGREP.MD_META is invalid
Compiling md_meta -
SQL> alter package md_meta compile ;
Warning: Package altered with compilation errors.
SQL> show errors
Errors for PACKAGE MD_META:
LINE/COL ERROR
0/0 PLS-00908: The stored format of MD_META is not supported by this
release
21/4 PLS-00114: identifier 'PUTBAIFZKA3IHSJ5AC4ZXWYAWG41KN' too long
21/4 PLS-00707: unsupported construct or internal error [2702]
SQL>
==
If you get this then the only alternative is to create the SQL*Developer repository in a 10.2 database.
Regards,
Mike

Migrating SQL server 2000 to Oracle9i/10g

hi
i want to migrate SQL server 2000 database to Oracle9i database,
and i have downloaded the file OMWB.Zip from OTN.
but i did not find the Sql sever2000 plug-in.
plz send the link where i can get sqlserver plug-in. (SqlServer2k.jar file)
or anyone plz mail me this SqlServer2k.jar file,my mail id is:
[email protected]
its very urgent. plz help me out.
Dwaipayan Das

Hi Dwaipayan,
SQL Server migrations are not supported by the (old)OMWB anymore.
This functionality has been moved into the SQL Developer Migration Workbench.
SQL Server migrations are a built in feature of SQL Developer, which you can download for free here.
http://www.oracle.com/technology/products/database/sql_developer/index.html
Before downloading you can take a look at this viewlet demonstrating the migration of SQL Server Northwind database.
http://www.oracle.com/technology/tech/migration/workbench/viewlets/sqlserver.html
All the new migration features are based around SQL Developer.
Heres are new page
http://www.oracle.com/technology/tech/migration//workbench/index_sqldev_omwb.html
Regards,
Dermot.

My Experiences re: Migrating SQL Server Database to Oracle

I am using SQL Developer EA4 for thsi conversion, best attempt yet.
I had numerous problems with this conversion.
1. The wizard asked me to specify the new Oracle database; instead it just ignored this information and created an Oracle database similarly named as the SQL Server database. I also noticed a file name "Migration.out" was produced; it contained errors such as:
Error starting at line 3 in command:
CREATE USER Emulation IDENTIFIED BY Emulation DEFAULT TABLESPACE USERS TEMPORARY TABLESPACE TEMP
Error at Command Line:3 Column:36
Error report:
SQL Error: ORA-01031: insufficient privileges
01031. 00000 - "insufficient privileges" and
Error starting at line 4 in command:
GRANT CREATE SESSION, RESOURCE, CREATE VIEW, CREATE MATERIALIZED VIEW, CREATE SYNONYM,CREATE PUBLIC SYNONYM TO Emulation
Error report:
SQL Error: ORA-01031: insufficient privileges
01031. 00000 - "insufficient privileges" and
Error starting at line 7 in command:
CREATE USER dbo_COREv13 IDENTIFIED BY dbo_COREv13 DEFAULT TABLESPACE USERS TEMPORARY TABLESPACE TEMP
Error at Command Line:7 Column:38
Error report:
SQL Error: ORA-01031: insufficient privileges
01031. 00000 - "insufficient privileges" and
Error starting at line 8 in command:
GRANT CREATE SESSION, RESOURCE, CREATE VIEW, CREATE MATERIALIZED VIEW, CREATE SYNONYM TO dbo_COREv13
Error report:
SQL Error: ORA-01031: insufficient privileges
01031. 00000 - "insufficient privileges".
I followed all of the steps listed in the "Help" section re: Migrations but still ended up with these errors.
2. My schema consists of 1000+ tables; approximately 10 tables were NOT created. When I copied the SQL from Migration.sql making NO changes and pasted it into the new Oracle database it created without issues.
3. While the conversion is taking place, different objects (constraints, indexes, foreign keys, etc) are shown to be copied; their appears to be ordering of these items. Shouln't a dependancy tree be established, and object converted based on this?
4. Several tables, in my case about 250 tables did NOT get any data copied across. No reasons given.
5. A log of all activities should be produced for review and completeness.
6. I tried to use the "Migrate select tables" option but met with no success. Apparently, it makes an assumption that both the "source" and "target" databases wil be of the same type (ie both SQL Server or both Oracle); this does not make any sense to me since the point of the exercise is to migrate data from one database vendor to another. Obviously, different database vendors use differing datatypes for similar data (ie dates).
7. I noticed in the "Migration" sql that the "Connect" statements are not correct; they were missing the "instance name" portion.
8. Also, when I looked in the "MIGRATION" sql, I could not find any entries for the last step of the conversion - the movement of data from SQL Server to Oracle. Is this intentional or an oversight.
I dont want to appear negative on this Migration; I have used SQL Developer since it inception; in my opinion this is the best attempt to date.
Murray Sobol

Hi Murray,
Thanks for this feedback.
There is a lot of questions here, I think some of it boils down to misunderstandings, which we should clarify in the doc.
Hopefully Ill get a video of a migration online soon as well.
But here is a brief break down.
*1.*
"The wizard asked me to specify the new Oracle database; instead it just ignored this information and created an Oracle database similarly named as the SQL Server database."
So this relates to Step 7 of the Migration Wizard. Where you can select the target connection.
SQL Developer doesn't ignore the Target Connection you selected, It just uses it to connect to the target database , not the target schema.
SQL Developer generates a new target schema for the migrated objects. It standard approach is not to generate objects directly into an existing Schema.
The Target Connection is used to create all the migrated objects (including new Oracle Schemas) in your target oracle database. So you should choose an Oracle Target Connection which has enough privileges to create new Schemas and Objects.
But as you have found, it doesn't generate the migrate objects , like tables, ... , directly into your chosen Target Connection.
From the errors you encountered it doesn't sound like the Target Connection (and the underling Oracle Schema) doesn't have the privileges to create other Schemas.
If you use something like a connection to the SYSTEM schema on your target database, it should run OK.
It wont create any objects in SYSTEM, rather it will use SYSTEM privileges to create a new schema (ex: dbo_Northwind) and populate it.
You don't have to use SYSTEM, but you do need a schema with enough privileges to create other schemas.
That is the straight forward way. But if you really need to generate into an existing schema the following steps can be taken.
a)rename the schema under the Converted Database Objects
b)Right click "Converted Databases Objects" and choose generate. it will kick off the Migration Wizard in the correct place
*2.*
My schema consists of 1000+ tables; approximately 10 tables were NOT created. When I copied the SQL from Migration.sql making NO changes and pasted it into the new Oracle database it created without issues.
When you say Migration.sql , is the entire generation file , which can be found in your <outputspecified>/generated/<projectname.modelname>.sql ?
When your say "pasted it into the new Oracle database" , are you running it in SQL Developers SQL Worksheet using the Target Connection.
Basically your migration is all out of shape once the target Schemas are not created. So the above issues (insufficient privileges) has to be resolved first.
Please post back if it is still an issue.
*3.*
While the conversion is taking place, different objects (constraints, indexes, foreign keys, etc) are shown to be copied; their appears to be ordering of these items. Shouln't a dependancy tree be established, and object converted based on this?
Objects are converted in a particular order and their dependencies are persisted so that they can be generated in the correct order.
Are you seeing an issue?
*4.*
Several tables, in my case about 250 tables did NOT get any data copied across. No reasons given.
I'm surprised any tables were populated with data due to the target schema not being created.
The online data move is pretty simple and it does not report or recover very well from issues.
If you are having difficulties once item 1. is resolved, please post an example of the source table and I will give it a go.
For better control of the data move with much more powerful tweaking, error handling, reporting and performance try the offline data move.
SQL Developer can created a suite of scripts which use SQL Servers BCP tool to dump out the data to dat files, and Oracle SQL*Loader tool to insert the data in the dat file into Oracle.
*5.*
A log of all activities should be produced for review and completeness.
The output/generated/<projectname.modelname>.out provides the output of running the generation script.
The migration reports http://dermotoneill.blogspot.com/2010/11/migration-reports-30.html outline what happens during the migration.
Apart from online data move issues, is there any other data missing?
*6.*
I tried to use the "Migrate select tables" option but met with no success. Apparently, it makes an assumption that both the "source" and "target" databases wil be of the same type (ie both SQL Server or both Oracle); this does not make any sense to me since the point of the exercise is to migrate data from one database vendor to another. Obviously, different database vendors use differing datatypes for similar data (ie dates).
Do you mean "Copy To Oracle" ? This option is intended to migrate tables from non Oracle databases like SQL Server to Oracle.
Can you give more details on what issue you are seeing.
*7.*
I noticed in the "Migration" sql that the "Connect" statements are not correct; they were missing the "instance name" portion.
The generation script is meant to be run using SQL Developers SQL Worksheet. I think you only get this "instance name" issue if running from SQL*Plus.
Can you confirm
8. Also, when I looked in the "MIGRATION" sql, I could not find any entries for the last step of the conversion - the movement of data from SQL Server to Oracle. Is this intentional or an oversight.
The online data move is performed separately from creating the objects. It is not script based, it uses JDBC to pump the data from the source database to the target database.
In summary , I would
a) Create a connection to your Target database using your SYSTEM schema
b) Right click on your "Converted Database Objects" and choose "Generate Target"
c) Choose your new "System" connection as the Target Connection
d) Follow the Migration Wizard to the end.
You will end up with a new target Schema and the migrated objects in it.
Check the .out file to see the errors
and the migration reports http://dermotoneill.blogspot.com/2010/11/migration-reports-30.html
Regards,
Dermot
SQL Developer Team.

Question about MS SQL Server 2012 License on a server (renting/buying)

Hi,
I am currently paying about $300 per month to the hosting company for the MS SQL 2012 Standard Edition (for 4 cores) on my server, my question is, can I just buy MS SQL 2012 STD outright ( for example here http://www.microsoftstore.com/store/msusa/en_US/pdp/SQL-Server-Standard-Edition-2012/productID.281182400
) for around $3k and stop paying hosting company $300 monthly ?
If I am able to just buy it outright, is it possible to switch the licensing code to the new one that I bought without reinstalling or loosing database?
Thank you.

Articles:
Penny Pinching in the Cloud: When do Azure Websites make sense?
To Cloud or not to Cloud: Microsoft Azure vs Hosted SQL Server..
Azure: SQL Databases, API Management, Media Services, Websites, Role Based Access Control and More
Kalman Toth Database & OLAP Architect
SQL Server 2014 Database Design
New Book / Kindle: Beginner Database Design & SQL Programming Using Microsoft SQL Server 2014

What to read about MS SQL server ... ?

Hello,
I just need an advice from you folks. I'm QE with some scripting skills. Now I've got an assignment to work with MS SQL 2008. My task is nothing with administration ... and mostly I will have to run SQL query and provide users with the results. Anyway ...
since I'm completely new to databases and to MS SQL as well I'd like to have some basic knowledge how database is organized, what are schema, system tables and etc.
Could you please point me to good on-line resource that could provide that info? It should not be sophisticated ... just basic but enough to understand how it works,
Thanks in advance.
EV

Purchase SQL Server 2014 (or 2012) Developer Edition for around $50 (2008 may no longer be available). Install it. Also install AdventureWorks2012 sample database.
SQL Server Management Studio is part of the client tools installation. SSMS is your learning and later working environment.
SSMS Object Explorer provides you access to all of the database objects.
Practice T-SQL scripts:
http://www.sqlusa.com/bestpractices/
Kalman Toth Database & OLAP Architect
SQL Server 2014 Design & Programming
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

Question about updating SQL Server on failover cluster

Hi all,
I would like to better understand the update process of SQL Server (2008 r2) in a failover cluster environment.
In our cluster we have 4 instances of SQL running, where two of them I am able to at anytime stop the instance and update it.
The question is... Applying the latest update, will update forcibly all instances installed on that node, or do I have the ability to choose which instance I want to update?
This way, I could "test" the update process in those two SQL Instances, as described in http://support.microsoft.com/kb/958734 and after finishing I would update the remaining instances.
Please let me know.
Thanks in advance.
Nuno Silva

Hi Nuno,
It's a failover cluster issue, I moved it to SQL Server High Availability and Disaster Recovery. So that you can get better help.
Regards,
Charlie Liao
TechNet Community Support

What is the rule about installing SQL server 2000

I'm a bit confused if which of the two is the best that i can do:
1. install MS SQL 2000 to R/3 Apllication Box per box
or
2. install MS SQL 2000 in 1 box and link the r/3 Applications form it?
im using SAP 4.6.c. I dont know what should i do... is it REALLY required that the MSSQL 2000 be installed per box (DEV, PRD, DB, etc.)?

Hi Michael,
it is possible to have just one DB server with different DBs (DEV, QAS, PRD) on it. You have to decide if you install your DBs in one instance of SQL Server or if you install named instances - e.g. one instance for DEV, one instance for QAS and so on. If you have all DBs in one instance they all share the same ressources like processors, buffers etc. That means that your possibilities to tune such a system are limited. Also if you have to stop the instance (e.g. for Support Packages or patches) all SAP Systems are not available.
On a box with named instances you can distribute the server ressources among those instances. For example the DEV instance gets 512 MB of RAM and may use 2 processors. The PRD instance gets 2 GB of RAM and may use 6 processors. You can stop and patch each instance individually.
But if I understand your post correctly you work in an 32 Bit environment. In such a case I would never recommend putting PRD with DEV and QAS on one database server. For DEV and QAS a Cental System (SQL Server and SAP on the same server) is usually the right choice. For production you might want to install the Database Instance on a separate server and the Central Instance on a separate server. For scalability reasons you can then add as many Dialog Instances as necessary.
But always keep in mind, you only have ONE Database Instance per SAP system! You can install many Dialog Instances connected to that Database Instance. That means your database is the 'heart' of you SAP system and should be treated that way.
Regards,
Sven

Experience about resource consumption about migration SQL- server to MaxDB

Similar Messages

Maybe you are looking for