Hi
Apologies for the long post, but I am in a bit of a scrape at the moment. Up SC without a paddle. I am doing a short SQL 2005 with SAP BW contract as a DBA overseas, and am encountering problems. I had told the agent that I don´t know either of these two, and only know SQL 2000, yet they still hired me.
What should I do? Give up and fly home, try to muddle my way through, fess up that I don´t think I can do it, or what.
I´ve given a description of the problems below in case anyone here knows anything about SAP and a thing called ABAP which I think is about automating SAP procedures.
The first problem is with tempdb. The client says that overnight there are five sets of data loads that run every hour from 1am to 5am. The data loads involve loading around 1 million records from a SAP R/3 system into "flat tables" in the SQL Server 2005 database. Then a second process merges these records into OLAP cubes in the database. Then a third process called "Activation" runs to recalculate the index values of these cubes.
The problem is that the size of tempdb sometimes grows to more than 15Gb during this process, and it runs out of disk space, causing the process to fail.
Is this large use of tempdb normal? If so how large could I expect it to get? Perhaps the solution is to ask the client to get a larger drive to hold tempdb - how large?
The second problem is more general, and is that a user says that when he runs a report, reading data from the cubes, it takes more than a minute to read the data out, even if it is only 40 rows that are returned.
Presumably this is because there are insufficient indexes on the tables, but there are apparently 120 tables involved with the cubes, and an amazing 15000 or so tables in total.
Also it seems to be the case that the SAP software itself creates and manages tables and indexes in the SQL database. Is this true? If so then presumably I would need to make any changes in the SAP software, and I know nothing about this.
The third problem is that they have shown me a printout from the SAP system that shows around 20 stored procedures that are taking between 30 seconds to 2 minutes to run. Again this is probably an index problem but I don´t see how I can resolve this if SAP handles the indexes.
Many Thanks
Apologies for the long post, but I am in a bit of a scrape at the moment. Up SC without a paddle. I am doing a short SQL 2005 with SAP BW contract as a DBA overseas, and am encountering problems. I had told the agent that I don´t know either of these two, and only know SQL 2000, yet they still hired me.
What should I do? Give up and fly home, try to muddle my way through, fess up that I don´t think I can do it, or what.
I´ve given a description of the problems below in case anyone here knows anything about SAP and a thing called ABAP which I think is about automating SAP procedures.
The first problem is with tempdb. The client says that overnight there are five sets of data loads that run every hour from 1am to 5am. The data loads involve loading around 1 million records from a SAP R/3 system into "flat tables" in the SQL Server 2005 database. Then a second process merges these records into OLAP cubes in the database. Then a third process called "Activation" runs to recalculate the index values of these cubes.
The problem is that the size of tempdb sometimes grows to more than 15Gb during this process, and it runs out of disk space, causing the process to fail.
Is this large use of tempdb normal? If so how large could I expect it to get? Perhaps the solution is to ask the client to get a larger drive to hold tempdb - how large?
The second problem is more general, and is that a user says that when he runs a report, reading data from the cubes, it takes more than a minute to read the data out, even if it is only 40 rows that are returned.
Presumably this is because there are insufficient indexes on the tables, but there are apparently 120 tables involved with the cubes, and an amazing 15000 or so tables in total.
Also it seems to be the case that the SAP software itself creates and manages tables and indexes in the SQL database. Is this true? If so then presumably I would need to make any changes in the SAP software, and I know nothing about this.
The third problem is that they have shown me a printout from the SAP system that shows around 20 stored procedures that are taking between 30 seconds to 2 minutes to run. Again this is probably an index problem but I don´t see how I can resolve this if SAP handles the indexes.
Many Thanks
Comment