Can' upgrade to non-GUID tabled partition.
Apparently I can't upgrade from Leopard to Snow Leopard because by OS disk partition doesn't use the "GUID Partition Table Scheme". However, I can't change the partition table scheme to GUID in Disk Utility, as per the install instructions, because "Volume Scheme" is grayed out on "current" and "Options" is grayed out as well.
Is there some other way to change the volume scheme, or failing that some way to upgrade my system without losing all of my current application installations and data?
Freewheeling wrote:
Thanks. What can I use to back up? I've been backing up to Time Machine, but can I restore everything from that? Shouldn't I make the drive bootable when I format it, and then restore from that... or should I just go ahead and restore from the system disk after reformatting? I kind of know the general principles but know enough to realize things may not behave exactly the way I expect.
If you trust TM, then you are backed up--assuming you have been doing full system backups. Otherwise, make a bootable clone of your internal volume on an external drive. You can use Disk Utility to do so. If you need instructions, then let me know.
The drive will be bootable after partitioning; use your Sno disk to partition (see below). And, since you are partitioning, you won't have to erase. I would not restore from the system disk. Doing so would require you to upgrade from Leo to move to Sno. After partitioning, I would prefer to install Sno cleanly and then migrate what I wanted from the clone or TM--preferably from the clone IMO. Note, however, that an upgrade install, with prior restoration from TM, is perfectly acceptable if your Leopard installation is in good condition. If it is not, then erasing and installing, with migration from a clone, will give you more options in avoiding problems with your Leopard install. For example, you could choose to migrate only your data and possibly your apps.
Similar Messages
-
Can Shuttles be based non-base table ViewObjects with transient attributes
Hello,
Users have to select records from a data collection and a Shuttle looks most appropriate/nice for this purpose. We can introduce technical intersection tables in order to generate the Shuttles with JHeadstart 10g R3 if necessary, but there is no “functional” need to update any data in the database and therefore it would be practical if the ‘right’ side from a Shuttle can be based non-base table ViewObjects with transient attributes only. So, our interested is to know which records have been selected, i.e. moved to the right side from the Shuttle.
Hope that my question is clear enough.
Greetings,
MichaelMichael,
This cannot be generated out-of-the-box.
It is easiest to add the shuttle post-generation to your page, and then create a custom template to generate your custom shuttle into the page. I suggest you take a look at an example of a generated shuttle in a page, and the JHeadstart IntersectionShuttleBean class. You will see that the value property of <af:selectManyShuttle> points to the selectedKeys method in the JHeadstart Shuttle bean. In your case, you can create your own managed bean and bind the value property to your own method which will provide you access to the selected rows. The value property of the selectItem within the af:selectManyShuttle determines the property that is used to identify the selected row (which is the row key in case of Jhs-generated shuttles).
Steven Davelaar,
JHeadstart Team. -
Where can I find a guide / How to about how to upgrade using SM?
Hi,
Where can I find a guide / How to about how to upgrade a NetWeaver server using SAP Solution Manager?
Thanks.>
Doron Shai wrote:
> Hi,
>
> Where can I find a guide / How to about how to upgrade a NetWeaver server using SAP Solution Manager?
>
> Thanks.
Dear Doron
Solution Manager system will never physically participate in the upgrade of a Netweaver Server. It will only help you to find the right files via the maintenance optimizer. Also if you want to develop / use a Project for your upgrade you could use the upgrade roadmap and then use Solution Manager as a Project Management tool for the upgrade.
Besides this there will be no guide available for "upgrading" a system, since the upgrade roadmap is generic and the maintenance optimizer feature is isolated from the roadmap. You will have to follow the upgrade guides available on
http://service.sap.com/instguides.
Hope that this answers your query.
Regards
Amit -
Tongue twister of a question, huh?
I am creating a APM-partitioned hard drive for use with a PowerPC iMac G5, so I can have a fresh OS install on one as a reference, and the other be my usable OS. Now, I also want to back both of these partitions up on a storage hard drive that I also want to contain partitions that are bootable on an Intel mac (GUID). My question is, can I clone my APM partitions as backup to designated partitions on my GUID backup/storage hard drive (which I plan on being able to boot other partions on an Intel Mac), and have the option of later cloning the same APM partitions back to an APM-paritioned hard drive and have them still be bootable on a Power PC? I know I won't be able to boot a Power PC from off of the GUID-paritioned drive, but I want to be able to restore my APM-partitioned drive incase things go sour with it.
Thanks so much for your time, guys!Block-level copier that copies not just the files but the filesystem structure as well. But files can be moved from GUID to APM partitioned devices without any effect on the file. The partition scheme affects whether an installed system will boot a particular type of hardware.
If you installed OS X on a GUID partitioned drive you would not be able to boot a PPC Mac.
And, you're most welcome.
Please note the items listed under Legend in the right sidebar of this page. -
How can we use the table partitions feature and.........
Hai friends when i tried to use the bitmap indexes and table partitions feature ,
I got a message like this
'table partiotion feature not enabled'
so please tell me how can i enable those features so that i will be able to use those features..........Partitioning and Bitmap Indexes are features of Oracle Enterprise addition. In fact, I think that Partitioning is an extra option that needs to purchased with Oracle Enterprise - it is not a default feature.
These features do not exist on Oracle Standard Edition (and likely Express Edition too). -
How do I put my iPhone stored items into my iCloud storage?i have bought an upgrade but none of my phones stored items have moved to iCloud.i can't download new update from apple. due to not enough and yet iCloud space is empty??please help I don't know what I doing all I know is my phone is iPhone 4 and I can't update it. My phone on contract with t-mobile . Thanks
You can't have content in iCloud without having it on your phone, you will need to look at deleting items from your device that you don't need. Movies and TV shows from iTunes are possibly a good start because they tend to be large and can be redownloaded at a later date.
-
How can I remove a non=working windows partition from my mac?
Alright so when I got my computer around 3 years ago my mom installed Windows on it. Sadly it didn't work and there was an uninstall so it uninstalled it, but now I have this 10 GB windows partition that's still there but I can't boot up on it and it's wasting 10 GB of my space. HOw can I get rid of it without risking of personal data (on my mac partition)
Hi Midnight Pharaoh;
Seeing as how I don't allow anything from Microsloth into my house I am not able to answer your question from personal experience but I believe that Boot Camp can in addition to creating a partition for Winders also delete said partition. If you need more details you might try reposting in the Boot Camp forum instead of the Snow Leopard forum.
Allan -
Long running table partitioning job
Dear HANA grus,
I've just finished table partitioning jobs for CDPOS(change document item) with 4 partitions by hash with 3 columns.
Total data volumn is around 340GB and the table size was 32GB !!!!!
(migration job was done without disabling CD, so currently deleting data on the table with RSCDOK99)
Before partitioning, the data volumn of the table was around 32GB.
After partitioning, the size has changed to 25GB.
It took around One and half hour with exclusive lock as mentioned in the HANA adminitration guide.
(It is QA DB, so less complaints)
I thought that I might not can do this in the production DB.
Does anyone hava any idea for accelerating this task?? (This is the fastest DBMS HANA!!!!)
Or Do you have any plan for online table partitioning functionality??(To HANA Development team)
Any comments would be appreciate.
Cheers,
- JasonJason,
looks like we're cross talking here...
What was your rationale to partition the table in the first place?
=> To reduce deleting time of CDPOS (As I mentioned it was almost 10% quantity of whole Data volume, So I would like to save deleting time of the table from any pros of partitioning table like partitioning pruning)
Ok, I see where you're coming from, but did you ever try out if your idea would actually work?
As deletion of data is heavily related with locating the records to be deleted, creating an index would have probably be the better choice.
Thinking about it... you want to get rid of 10% of your data and in order to speed the overall process up, you decide to move 100% of the data into sets of 25% of the data - equally holding their 25% share of the 10% records to be deleted.
The deletion then should run along these 4 sets of 25% of data.
It's surely me, but where is the speedup potential here?
How many unloads happened during the re-partitioning?
=> It was fully uploaded in the memory before partitioning the table by myself.(from HANA studio)
I was actually asking about unloads _during_ the re-partitioning process. Check M_CS_UNLOADS for the time frame in question.
How do the now longer running SQL statements look like?
=> As i mentioned selecting/deleting increased almost twice.
That's not what I asked.
Post the SQL statement text that was taking longer.
What are the three columns you picked for partitioning?
=> mandant, objectclas, tabname(QA has 2 clients and each of them have nearly same rows of the table)
Why those? Because these are the primary key?
I wouldn't be surprised if the SQL statements only refer to e.g. MANDT and TABNAME in the WHERE clause.
In that case the partition pruning cannot work and all partitions have to be searched.
How did you come up with 4 partitions? Why not 13, 72 or 213?
=> I thought each partitions' size would be 8GB(32GB/4) if they are divided into same size(just simple thought), and 8GB size is almost same size like other largest top20 tables in the HANA DB.
Alright, so basically that was arbitrary.
For the last comment of your reply, most people would do partition for their existing large tables to get any benefit of partitioning(just like me). I think your comment can be applied for the newly inserting data.
Well, not sure what "most people" would do.
HASH partitioning a large existing table certainly is not an activity that is just triggered off in a production system. Adding partitions to a range partitions table however happens all the time.
- Lars -
Table partitioning (intervel partitioning) on existing tables in oracle 11g
Hi i'm newbie to table partitioning. I'm using 11g. I have table of size 32 gb (which has 22 million records) and i want to apply interval partition on that table. I created a empty table with a partition having columns same as source table and take dump of the source table and import into the new partition table. can you please suggest how to import table dump into new table? also is there any other better idea to do the same.
Hi,
imp user/password file=exp.dmp ignore=y
The ignore=y causes the import to skip the table creation and continues to load all rows.
On the other hand, you can insert data into the partitioned table with a subquery from the non-partitioned table such as follows;
insert into patitioned_table
select * from original_table;
Hope it helps, -
Calculated non-base table field in a tabular form
I am struggling with creating a non-base table calculated field in a tabular form in ApEx 3.1
Can you point me in the right direction
I thought this would be fairly easy to do, but I cant work out how to do it
Requirements
1) Tabular Form based on a table with QTY and PRICE columns
2) TOTAL is a non-base table field, based on QTY * PRICE
3) If the Qty or Price changes, the TOTAL should be re-calculated
Example
QTY PRICE TOTAL
=== ===== =====
3 5 15
10 50 500
20 3 60
Environment
ApEx 3.1, Oracle 10 and Oracle 11 databases
I recommended to upgrade to a newer version of ApEx but the request was rejected so Im stuck with 3.1Thanks, but its not the solution that I am after
I am looking for a solution that will ...
1) not require the calculated value TOTAL to be stored in the table
and 2) re-calculate the TOTAL when I modify the dependent values (QTY and PRICE) before I save the changes to the database
I am still looking for a solution if anyone can help -
How can I find out which tables are having DDL locks?
I can see related information by querying DBA_DDL_LOCKS view, but it doesn't give me the information which tables are having DDL locks.
Is there a way I can find out which tables are having DDL locks?
Thanks!Here's a long script written back in 2001. Still works:
BREAK on sid on serial# on username
COL sid for 9999
COL serial# for 99999
COL username for a20
COL type for a20 trunc
COL lmode for a5 trunc
COL lrequest for a4 trunc
COL detail for a75 trunc
SELECT s.sid
, s.serial#
, s.username
, DECODE(
l.TYPE
-- Long locks
, 'TM', 'dml/data enq (TM)'
, 'TX', 'transac enq (TX) '
, 'UL', 'pls usr lock (UL)'
-- Short locks
, 'BL', 'buf hash tbl (BL)'
, 'CF', 'control file (CF)'
, 'CI', 'cross inst f (CI)'
, 'CU', 'cursor bind (CU) '
, 'DF', 'data file (CF) '
, 'DL', 'direct load (DL) '
, 'DM', 'mount/strtup (DM)'
, 'DR', 'reco lock (DR) '
, 'DX', 'distrib tran (DX)'
, 'FI', 'sga opn file (FI)'
, 'FS', 'file set (FS) '
, 'IN', 'instance num (IN)'
, 'IR', 'instce recvr (IR)'
, 'IS', 'get state (IS) '
, 'IV', 'libcache inv (IV)'
, 'JQ', 'job queue (JQ) '
, 'KK', 'log sw kick (KK) '
, 'LS', 'log switch (LS) '
, 'MM', 'mount def (MM) '
, 'MR', 'media recvry (MR)'
, 'PF', 'pwfile enq (PF) '
, 'PR', 'process strt (PR)'
, 'RW', 'row wait (RW) '
, 'RT', 'redo thread (RT) '
, 'SC', 'scn enq (SC) '
, 'SM', 'smon lock (SM) '
, 'SN', 'seqno instce (SN)'
, 'SQ', 'seqno enq (SQ) '
, 'ST', 'space transc (ST)'
, 'SV', 'seqno value (SV) '
, 'TA', 'generic enq (TA) '
, 'TD', 'dll enq (TD) '
, 'TE', 'extend seg (TE) '
, 'TS', 'temp segment (TS)'
, 'TT', 'temp table (TT) '
, 'UN', 'user name (UN) '
, 'WL', 'write redo (WL) '
, 'TYPE = ' || l.TYPE) AS type
, DECODE(l.lmode, 0, 'none', 1, 'null', 2, 'RS', 3, 'RX', 4, 'S', 5, 'SRX', 6, 'X', TO_CHAR(l.lmode)) A
S lmode
, DECODE(l.request, 0, 'none', 1, 'null', 2, 'RS', 3, 'RX', 4, 'S', 5, 'SRX', 6, 'X', TO_CHAR(l.request
)) AS lrequest
, DECODE(
l.TYPE
, 'JQ', 'Job #' || j.job || ' (' || j.what || ') owned by: ' || j.username
, 'MR', DECODE(s.user_type, 'BG', 'DICTIONARY OBJECT', LOWER(obj.owner) || '.' || LOWER(obj.name))
|| ' (' || LOWER(obj.TYPE) || ')'
, 'RT', 'thread #' || LOWER(l.id1)
, 'RW', 'file#' || LOWER(SUBSTR(l.id1, 1, 3)) || ', block#' || LOWER(SUBSTR(l.id1, 4, 5)) || ', ro
w#' || LOWER(l.id2)
, 'TD', 'object: ' || LOWER(obj.owner) || '.' || LOWER(obj.name) || ' (' || LOWER(obj.TYPE) || ')'
, 'TM', 'object: ' || LOWER(obj.owner) || '.' || LOWER(obj.name) || ' (' || LOWER(obj.TYPE) || ')'
, 'TS', DECODE(l.id2, 0, 'enqueue', 'new block allocation')
, 'TX', DECODE(
lo.object_name
, NULL, 'rbs #' || TRUNC(l.id1 / 65536) || ', slot #' || LOWER(l.id1)
, 'rbs #' || TRUNC(l.id1 / 65536) || ', slot #' || LOWER(l.id1) || ', object: ' || LOWE
R(lo.object_name))
, 'UL', 'lock name: ' || la.name || ', expiration date: ' || TO_CHAR(la.expiration, 'DD-MON-RR HH2
4:MI:SS')
, 'WL', 'redo log file#' || LOWER(l.id1)
, 'id1 = ' || l.id1 || ', id2 = ' || l.id2) AS detail
FROM sys.v_$lock l
, (SELECT a.sid
, a.serial#
, NVL(a.username, 'SYS (' || LOWER(b.name) || ')') AS username
, DECODE(a.username, NULL, 'BG', 'USER') AS user_type
FROM sys.v_$session a
, sys.v_$bgprocess b
WHERE a.paddr = b.paddr(+)) s
, (SELECT o.obj#
, u.name AS owner
, o.name
, DECODE(
o.type#
, 0, 'NEXT OBJECT'
, 1, 'INDEX'
, 2, 'TABLE'
, 3, 'CLUSTER'
, 4, 'VIEW'
, 5, 'SYNONYM'
, 6, 'SEQUENCE'
, 7, 'PROCEDURE'
, 8, 'FUNCTION'
, 9, 'PACKAGE'
, 11, 'PACKAGE BODY'
, 12, 'TRIGGER'
, 13, 'TYPE'
, 14, 'TYPE BODY'
, 19, 'TABLE PARTITION'
, 20, 'INDEX PARTITION'
, 22, 'LIBRARY'
, 23, 'DIRECTORY'
, 24, 'QUEUE'
, 28, 'JAVA SOURCE'
, 29, 'JAVA CLASS'
, 30, 'JAVA RESOURCE'
, 32, 'INDEXTYPE'
, 33, 'OPERATOR'
, 34, 'TABLE SUBPARTITION'
, 35, 'INDEX SUBPARTITION'
, 39, 'LOB PARTITION'
, 40, 'LOB SUBPARTITION'
, 43, 'DIMENSION'
, 44, 'CONTEXT'
, 47, 'RESOURCE PLAN'
, 48, 'CONSUMER GROUP'
, 51, 'SUBSCRIPTION'
, 52, 'LOCATION'
, 'UNDEFINED') AS type
FROM sys.obj$ o
, sys.user$ u
WHERE o.owner# = u.user#) obj
, (SELECT vlo.xidusn
, vlo.xidslot
, vlo.xidsqn
, vlo.process
, o.owner || '.' || o.object_name AS object_name
FROM sys.v_$locked_object vlo
, sys.dba_objects o
WHERE vlo.object_id = o.object_id) lo
, (SELECT job
, schema_user AS username
, what
FROM dba_jobs) j
, sys.dbms_lock_allocated la
WHERE l.sid = s.sid
AND l.id1 = obj.obj#(+)
AND l.id2 = j.job(+)
AND TRUNC(l.id1 / 65536) = lo.xidusn(+)
AND LOWER(l.id1) = lo.xidslot(+)
AND l.id2 = lo.xidsqn(+)
AND l.id1 = la.lockid(+)
AND l.TYPE != 'MR'
UNION ALL
/*** LATCH HOLDERS ***/
SELECT s.sid
, s.serial#
, s.username
, 'latch'
, 'X'
, 'none'
, h.name || ' addr=' || LOWER(RAWTOHEX(laddr)) AS object
FROM sys.v_$process p
, sys.v_$session s
, sys.v_$latchholder h
WHERE h.pid = p.pid
AND p.addr = s.paddr
UNION ALL
/*** LATCH WAITERS ***/
SELECT s.sid
, s.serial#
, s.username
, 'latch'
, 'none'
, 'X'
, name || ' latch=' || p.latchwait AS object
FROM sys.v_$session s
, sys.v_$process p
, sys.v_$latch l
WHERE latchwait IS NOT NULL
AND p.addr = s.paddr
AND p.latchwait = l.addr
ORDER BY sid
, serial#
, username
, 4
, 5
, 6
, 7; -
Fact and dimension table partition
My team is implementing new data-warehouse. I would like to know that when should we plan to do partition of fact and dimension table, before data comes in or after?
Hi,
It is recommended to partition Fact table (Where we will have huge data). Automate the partition so that each day it will create a new partition to hold latest data (Split the previous partition into 2). Best practice is to create partition on transaction
timestamps so load the incremental data into a empty table called (Table_IN) and then Switch that data into main table (Table). Make sure your tables (Table and Table_IN) should be on one file group.
Refer below content for detailed info
Designing and Administrating Partitions in SQL Server 2012
A popular method of better managing large and active tables and indexes is the use of partitioning. Partitioning is a feature for segregating I/O workload within
SQL Server database so that I/O can be better balanced against available I/O subsystems while providing better user response time, lower I/O latency, and faster backups and recovery. By partitioning tables and indexes across multiple filegroups, data retrieval
and management is much quicker because only subsets of the data are used, meanwhile ensuring that the integrity of the database as a whole remains intact.
Tip
Partitioning is typically used for administrative or certain I/O performance scenarios. However, partitioning can also speed up some queries by enabling
lock escalation to a single partition, rather than to an entire table. You must allow lock escalation to move up to the partition level by setting it with either the Lock Escalation option of Database Options page in SSMS or by using the LOCK_ESCALATION option
of the ALTER TABLE statement.
After a table or index is partitioned, data is stored horizontally across multiple filegroups, so groups of data are mapped to individual partitions. Typical
scenarios for partitioning include large tables that become very difficult to manage, tables that are suffering performance degradation because of excessive I/O or blocking locks, table-centric maintenance processes that exceed the available time for maintenance,
and moving historical data from the active portion of a table to a partition with less activity.
Partitioning tables and indexes warrants a bit of planning before putting them into production. The usual approach to partitioning a table or index follows these
steps:
1. Create
the filegroup(s) and file(s) used to hold the partitions defined by the partitioning scheme.
2. Create
a partition function to map the rows of the table or index to specific partitions based on the values in a specified column. A very common partitioning function is based on the creation date of the record.
3. Create
a partitioning scheme to map the partitions of the partitioned table to the specified filegroup(s) and, thereby, to specific locations on the Windows file system.
4. Create
the table or index (or ALTER an existing table or index) by specifying the partition scheme as the storage location for the partitioned object.
Although Transact-SQL commands are available to perform every step described earlier, the Create Partition Wizard makes the entire process quick and easy through
an intuitive point-and-click interface. The next section provides an overview of using the Create Partition Wizard in SQL Server 2012, and an example later in this section shows the Transact-SQL commands.
Leveraging the Create Partition Wizard to Create Table and Index Partitions
The Create Partition Wizard can be used to divide data in large tables across multiple filegroups to increase performance and can be invoked by right-clicking
any table or index, selecting Storage, and then selecting Create Partition. The first step is to identify which columns to partition by reviewing all the columns available in the Available Partitioning Columns section located on the Select a Partitioning Column
dialog box, as displayed in Figure 3.13. This screen also includes additional options such as the following:
Figure 3.13. Selecting a partitioning column.
The next screen is called Select a Partition Function. This page is used for specifying the partition function where the data will be partitioned. The options
include using an existing partition or creating a new partition. The subsequent page is called New Partition Scheme. Here a DBA will conduct a mapping of the rows selected of tables being partitioned to a desired filegroup. Either a new partition scheme should
be used or a new one needs to be created. The final screen is used for doing the actual mapping. On the Map Partitions page, specify the partitions to be used for each partition and then enter a range for the values of the partitions. The
ranges and settings on the grid include the following:
Note
By opening the Set Boundary Values dialog box, a DBA can set boundary values based on dates (for example, partition everything in a column after a specific
date). The data types are based on dates.
Designing table and index partitions is a DBA task that typically requires a joint effort with the database development team. The DBA must have a strong understanding
of the database, tables, and columns to make the correct choices for partitioning. For more information on partitioning, review Books Online.
Enhancements to Partitioning in SQL Server 2012
SQL Server 2012 now supports as many as 15,000 partitions. When using more than 1,000 partitions, Microsoft recommends that the instance of SQL Server have at
least 16Gb of available memory. This recommendation particularly applies to partitioned indexes, especially those that are not aligned with the base table or with the clustered index of the table. Other Data Manipulation Language statements (DML) and Data
Definition Language statements (DDL) may also run short of memory when processing on a large number of partitions.
Certain DBCC commands may take longer to execute when processing a large number of partitions. On the other hand, a few DBCC commands can be scoped to the partition
level and, if so, can be used to perform their function on a subset of data in the partitioned table.
Queries may also benefit from a new query engine enhancement called partition elimination. SQL Server uses partition enhancement automatically if it is available.
Here’s how it works. Assume a table has four partitions, with all the data for customers whose names begin with R, S, or T in the third partition. If a query’s WHERE clause
filters on customer name looking for ‘System%’, the query engine knows that it needs only to partition three to answer
the request. Thus, it might greatly reduce I/O for that query. On the other hand, some queries might take longer if there are more than 1,000 partitions and the query is not able to perform partition elimination.
Finally, SQL Server 2012 introduces some changes and improvements to the algorithms used to calculate partitioned index statistics. Primarily, SQL Server 2012
samples rows in a partitioned index when it is created or rebuilt, rather than scanning all available rows. This may sometimes result in somewhat different query behavior compared to the same queries running on SQL Server 2012.
Administrating Data Using Partition Switching
Partitioning is useful to access and manage a subset of data while losing none of the integrity of the entire data set. There is one limitation, though. When
a partition is created on an existing table, new data is added to a specific partition or to the default partition if none is specified. That means the default partition might grow unwieldy if it is left unmanaged. (This concept is similar to how a clustered
index needs to be rebuilt from time to time to reestablish its fill factor setting.)
Switching partitions is a fast operation because no physical movement of data takes place. Instead, only the metadata pointers to the physical data are altered.
You can alter partitions using SQL Server Management Studio or with the ALTER TABLE...SWITCH
Transact-SQL statement. Both options enable you to ensure partitions are
well maintained. For example, you can transfer subsets of data between partitions, move tables between partitions, or combine partitions together. Because the ALTER TABLE...SWITCH statement
does not actually move the data, a few prerequisites must be in place:
• Partitions must use the same column when switching between two partitions.
• The source and target table must exist prior to the switch and must be on the same filegroup, along with their corresponding indexes,
index partitions, and indexed view partitions.
• The target partition must exist prior to the switch, and it must be empty, whether adding a table to an existing partitioned table
or moving a partition from one table to another. The same holds true when moving a partitioned table to a nonpartitioned table structure.
• The source and target tables must have the same columns in identical order with the same names, data types, and data type attributes
(length, precision, scale, and nullability). Computed columns must have identical syntax, as well as primary key constraints. The tables must also have the same settings for ANSI_NULLS and QUOTED_IDENTIFIER properties.
Clustered and nonclustered indexes must be identical. ROWGUID properties
and XML schemas must match. Finally, settings for in-row data storage must also be the same.
• The source and target tables must have matching nullability on the partitioning column. Although both NULL and NOT
NULL are supported, NOT
NULL is strongly recommended.
Likewise, the ALTER TABLE...SWITCH statement
will not work under certain circumstances:
• Full-text indexes, XML indexes, and old-fashioned SQL Server rules are not allowed (though CHECK constraints
are allowed).
• Tables in a merge replication scheme are not allowed. Tables in a transactional replication scheme are allowed with special caveats.
Triggers are allowed on tables but must not fire during the switch.
• Indexes on the source and target table must reside on the same partition as the tables themselves.
• Indexed views make partition switching difficult and have a lot of extra rules about how and when they can be switched. Refer to
the SQL Server Books Online if you want to perform partition switching on tables containing indexed views.
• Referential integrity can impact the use of partition switching. First, foreign keys on other tables cannot reference the source
table. If the source table holds the primary key, it cannot have a primary or foreign key relationship with the target table. If the target table holds the foreign key, it cannot have a primary or foreign key relationship with the source table.
In summary, simple tables can easily accommodate partition switching. The more complexity a source or target table exhibits, the more likely that careful planning
and extra work will be required to even make partition switching possible, let alone efficient.
Here’s an example where we create a partitioned table using a previously created partition scheme, called Date_Range_PartScheme1.
We then create a new, nonpartitioned table identical to the partitioned table residing on the same filegroup. We finish up switching the data from the partitioned table into the nonpartitioned table:
CREATE TABLE TransactionHistory_Partn1 (Xn_Hst_ID int, Xn_Type char(10)) ON Date_Range_PartScheme1 (Xn_Hst_ID) ; GO CREATE TABLE TransactionHistory_No_Partn (Xn_Hst_ID int, Xn_Type
char(10)) ON main_filegroup ; GO ALTER TABLE TransactionHistory_Partn1 SWITCH partition1 TO TransactionHistory_No_Partn; GO
The next section shows how to use a more sophisticated, but very popular, approach to partition switching called a sliding
window partition.
Example and Best Practices for Managing Sliding Window Partitions
Assume that our AdventureWorks business is booming. The sales staff, and by extension the AdventureWorks2012 database, is very busy. We noticed over time that
the TransactionHistory table is very active as sales transactions are first entered and are still very active over their first month in the database. But the older the transactions are, the less activity they see. Consequently, we’d like to automatically group
transactions into four partitions per year, basically containing one quarter of the year’s data each, in a rolling partitioning. Any transaction older than one year will be purged or archived.
The answer to a scenario like the preceding one is called a sliding window partition because
we are constantly loading new data in and sliding old data over, eventually to be purged or archived. Before you begin, you must choose either a LEFT partition function window or a RIGHT partition function window:
1. How
data is handled varies according to the choice of LEFT or RIGHT partition function window:
• With a LEFT strategy, partition1 holds the oldest data (Q4 data), partition2 holds data that is 6- to 9-months old (Q3), partition3
holds data that is 3- to 6-months old (Q2), and partition4 holds recent data less than 3-months old.
• With a RIGHT strategy, partition4 holds the holds data (Q4), partition3 holds Q3 data, partition2 holds Q2 data, and partition1
holds recent data.
• Following the best practice, make sure there are empty partitions on both the leading edge (partition0) and trailing edge (partition5)
of the partition.
• RIGHT range functions usually make more sense to most people because it is natural for most people to to start ranges at their lowest
value and work upward from there.
2. Assuming
that a RIGHT partition function windows is used, we first use the SPLIT subclause of the ALTER PARTITION FUNCTIONstatement
to split empty partition5 into two empty partitions, 5 and 6.
3. We
use the SWITCH subclause
of ALTER TABLE to
switch out partition4 to a staging table for archiving or simply to drop and purge the data. Partition4 is now empty.
4. We
can then use MERGE to
combine the empty partitions 4 and 5, so that we’re back to the same number of partitions as when we started. This way, partition3 becomes the new partition4, partition2 becomes the new partition3, and partition1 becomes the new partition2.
5. We
can use SWITCH to
push the new quarter’s data into the spot of partition1.
Tip
Use the $PARTITION system
function to determine where a partition function places values within a range of partitions.
Some best practices to consider for using a slide window partition include the following:
• Load newest data into a heap, and then add indexes after the load is finished. Delete oldest data or, when working with very large
data sets, drop the partition with the oldest data.
• Keep an empty staging partition at the leftmost and rightmost ends of the partition range to ensure that the partitions split when
loading in new data, and merge, after unloading old data, do not cause data movement.
• Do not split or merge a partition already populated with data because this can cause severe locking and explosive log growth.
• Create the load staging table in the same filegroup as the partition you are loading.
• Create the unload staging table in the same filegroup as the partition you are deleting.
• Don’t load a partition until its range boundary is met. For example, don’t create and load a partition meant to hold data that is
one to two months older before the current data has aged one month. Instead, continue to allow the latest partition to accumulate data until the data is ready for a new, full partition.
• Unload one partition at a time.
• The ALTER TABLE...SWITCH statement
issues a schema lock on the entire table. Keep this in mind if regular transactional activity is still going on while a table is being partitioned.
Thanks Shiven:) If Answer is Helpful, Please Vote -
Modeling: Is Fact Table partitioning that important?
I read of how much partitioning a fact table can speed a query. On an upcoming project with specifications for only 4 InfoCubes, how can we take advantage in partitioning to fact tables to speed up queries?
Can this be factored into the design now or, we should wait till queries on Cube begins to perform poorly?
Thanks.Spend some time reviewing the links others have provided and serach SDN.
As mentioned, there are two types of partitioning generally talked about with SAP BW, logical and physical partitioning.
<u><b>Logical partitioning</b></u> - instead of having all your data in a single cube, you might break into separate cubes, with each cube holding aspecific year's data, e.g. you could have 5 sales cubes, one for each year 2001 thru 2005.
You would then create a Multi-Provider that allowed you to query all of them together.
A query that needs data from all 5 years would then automatically (you can control this) be split into 5 separate queries, one against each cube, <b>running at the same time</b>. The system automatically merges the results from the 5 queries into a single result set.
So it's easy to see when this could be a benefit. If your queries however are primarily run just for a single year, then you don't receive the benefit of the parallel processing. In non-Oracle DBs, splitting the data like this may still be a benefit by reducing the amount of rows in the fact table that must be read, but does not provide as much value to an Oracle DB since Infocube queries are using a Star_Transformation.
<u><b>Physical Partitioning</b></u> - I believe only Oracle and Informix currently support Range partitioning. This is a separately licensed option in Oracle.
Physical partitioning allows you to split an Infocube into smaller pieces. The pieces, or partitions, can only be created by 0FISCPER or 0CALMONTH for an InfoCube (ODSs can be partitioned, but require a DBAs involvement). The DB can then take advantage of this partitioning by "pruning" partitions during a query, e.g. a query only needs data form June 2005
The DB is smart enough to restrict the indices and data it will read to the June 2005 partition. This assumes your query restricts/filters on the partitioning characteristic. It can apply this pruning to a range of partitions as well, e.g. 0FISCPER 001/2005 thru 003/2005 would only look at the 3 partitions.
It is <u><b>NOT</b></u>smart enough, however, to figure out that if your restrict to 0FISC<u>YEAR</u> = 2005, that it should only read 000/2005 thru 016/2005 since 0FISCYEAR is NOT the partitioning characteristic.
An InfoCube MUST be empty in order to physically partition it. At this time, there is no way to add additional partitions thru AWB, so you want to make sure that you create partitions out into the future for at least a of couple of years.
If the base cube is partitioned, any aggregates that contain the partitioning characteristic (0CALMONTH or 0FISCPER) will automatically be partitioned.
In summary, you need to figure out if you want to use physical or logical partitioning on the cube(s), or both, as they are not mutually exclusive.
So you would need to know how the data will be queried, and the volume of data. It would make little sense to partition cubes that will not be very large. -
hi everybody !
I have a table which also has data in it. Now, before i add some more data to this table i want to create a partition with all the existing data. Following is the error message i get when executing the altertable command.
ALTER TABLE address_header_temp
add PARTITION add_head_temp
VALUES LESS THAN (MAXVALUE);
error :-
ORA-14501: object is not partitioned
Please help me in solving this problem.
Thanks in advance
MoloyIf you wanna do it online, then, use dbms_redine package to redifine objects online. I believe this is one time process. Once you add partitions and you can drop and create partions accordingly. At least you get out of heap table to meet your requirements.
Otherwise, create another table with required partions and move data from heap (non partitoned) table to partitioned table, drop the old one and rename the new one to old one.
Jaffar -
Can you use Windows 7 to partition a Boot Camp created dedicated PC drive (not just a PC partition on a Mac drive) into multiple PC partitions?
Can you download this utility, it is a close equivalent of the gpt command, but has more features? (It is more than likely that Windows took over and converted this to an MBR disk).
http://sourceforge.net/projects/gptfdisk/
Once you have it installed you run it as follows. You can execute using either /dev/disk1 or /dev/rdisk1 as the parameter.
type gdisk
gdisk is /usr/sbin/gdisk
sudo gdisk /dev/disk0
Password:
GPT fdisk (gdisk) version 0.8.9
Warning: Devices opened with shared lock will not have their
partition table automatically reloaded!
Partition table scan:
MBR: hybrid
BSD: not present
APM: not present
GPT: present
Found valid GPT with hybrid MBR; using GPT.
Command (? for help): p
Disk /dev/disk0: 1954210120 sectors, 931.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 6ED0C429-00D1-4759-B50E-04B6FB80D0E3
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1954210086
Partitions will be aligned on 8-sector boundaries
Total free space is 1293 sectors (646.5 KiB)
Number Start (sector) End (sector) Size Code Name
1 40 409639 200.0 MiB EF00 EFI System Partition
2 409640 1452940543 692.6 GiB AF00 Customer
3 1452940544 1454210079 619.9 MiB AB00 Recovery HD
4 1454211072 1954209791 238.4 GiB 0700 BOOTCAMP
Command (? for help): q
Maybe you are looking for
-
Delete in database based on multiselect list values
Hi, I have a selectlist in Apex and a function in the database to do some delete based on the selected value from the select list. FUNCTION delete_batch (v_batch VARCHAR2) RETURN VARCHAR2 IS BEGIN IF v_batch like 'M%' THEN RETURN ('A monthrun cann
-
from where does the system pick the base value for condition type BSAB in tax code as we are not maintaining any condition records.
-
CPO on Activity Monitor over 100%
I run Power eTrade Pro, a java based application with a continuous internet feed, and experience periods of over 100% CPU activity according to Activity Monitor. During those periods the program is frozen. This didn't happen with 10.4. It happens bot
-
Some characters from xerces are ?. j2sdk1.3 doesn't do this.
Hi, I used to use j2sdk1.3 and now I'm using j2sdk1.4.1, and I wrote a program befor that uses Xerces that reads various strange character entities which are then stored in a hashmap with the idea of translating certain weird characters into normal c
-
Help With Putting Local Files on my Phone
I have been attempting to follow the instructons on how to put Local Files from my computer onto my phone. My phone and computer are connected to the same Wi-Fi network, but my phone cant seem to find the songs. Can anyone help me out? Much appreciat