Tag Info

New answers tagged

1

I found an utility that does exactly what I need : SQLYog (Database Synchronization Wizard)


1

"On what parameters can we monitor data warehouse?". Exactly the same ones that you use for monitoring an OLTP database. You might want to pay more attention to things like slow query log (MySQL) for a DW, but that should be on the radar for an OLTP system also. The common "gotchas" may change, but databases all sit on machines with disk, RAM, CPU and ...


1

As u told it possible to create another database(with different name) with in the server. try once in local db then you can go into production.


1

Forfiles doesn't work with UNC. The trick is to map the shared UNC using pushd. This maps and entered a temporarily drive. Popd will pushd \RemoteHostName\sharedFolderName forfiles /P "\RemoteHostName\sharedFolderName" /s /m *.bak /D -7 /C "cmd /c del @path" popd


0

See my answer to this question which is similar in scope to your own question, except that your project is already up and running, so you can ignore the recommendation to use PostgreSQL instead of MySQL if starting from scratch. As Lmu92 points out, the one thing that is critical in a scenario like this is to have a very clear set of procedures about ...


0

You should store all information that is common for all companies in one database and copy the data that are needed to the database that needs the information. Adding a new customer would be done in the common db. After that the information will be copied to company1. If it's needed in company2, then the data will be copied to company2. Make sure you also ...


1

Your sql query is wrong: - Assume there is a student s1 who has passed one exam after '2000-01-01' and none before. Your query results in {s1} - {} = {s1}. This will be a false positive. - Assume there is a student s1 that passed three exams after '2000-01-01' and one exam before. Your query results in {s1} - {s1} = {}. This will be a false ...


1

At this time, only superusers can see others' activity details in pg_stat_activity. PostgreSQL could use a finer-grained rights model, where you can GRANT the MONITOR_QUERIES right to a user, for example. But right now it doesn't have one, and quite a few things are superuser-only. This is one of them.


1

I particularly like this one which works from within your (firefox) browser. If you're not a firefox user, then here is a list of alternatives.


0

Use the official sample databases from MySQL: http://dev.mysql.com/doc/index-other.html.


0

@user129400 is right - replacing UNDO tbs is a good idea. You can also try: contact Oracle support disable parallel media recovery If you have at least two copies of redo logs you can also check whether they are identical. If not remove one of the copies bypass media recovery completely, start the database, export application schemas and import them into ...


0

Since the problem is in your undo tablespace. You can drop it and create a new one. Steps in this article: http://www.my-whiteboard.com/how-to-drop-and-recreate-oracle-undo-tablespace-and-its-data-files/


0

I have had success in general replacing lengthy IN operations with a join against a temporary table. This makes sense because RDBMS are optimized to perform JOIN's as efficiently as possible, and the handling of lengthy IN lists will most likely be done by repeating the query for every value in the IN list. The performance issue you see could easily be ...


-1

configure the listener using Net Configuration Assistant or delete and recreate the listener with the same name and port


1

You can do this with Soft-NUMA. Here's a Perfmon screen shot from a 4-CPU VM I set up to test using your settings, 2 soft NUMA nodes, 1 CPU to Node 0, 3 CPUs to Node 1. I'm running a CPU intensive query for 20 seconds on node 0, and then the same query on node 2. You can see the CPU activity swap over: I'm running the query via sqlcmd and connecting ...


1

Is there a way to make queries from a database to use only certain core on the host? One way is to use query hint OPTION (MAXDOP 1). The problem with above apporach is that you have to hint everything that you don’t want to be limited by the server-wide setting, or use 0 (i.e. unlimited) for the server-wide setting and hint everything that you do want ...


0

There are two problems here, which must be solved independently. Creating a slave With that size, 100GB, mysqldump is usually to slow too be done efficiently. Try using a binary backup. You have several options: @paul is telling you one, but it has the inconvenient that the master will be locked for the duration of the copy process. Additionally, rsync can ...


0

Do you have log backups or differential backups ? I did not find any information about them in your post. Since(I assume) you do not have transaction log backup point in time recovery is not possible and you cannot recover data changes done after 1 AM. Since your query executed in AUTO COMMIT mode its possible that transaction has committed and changes ...


2

That's called a Major Whoopsie. Assuming you didn't use transactions around the delete you are stuck with scanning the log files and redoing all the INSERT and UPDATE queries. If you don't have a query log then it's manual entry time. If it's any consolation the Government of Alaska had a similar issue a while ago, further compounded by the backup tapes ...


0

A major issue with recreating a database of that size is the indexes. It's going to take a while to index what I assume is rows in the billions. Solution is to copy the indexes along with the data, and that means skipping the dump. It also means skipping the move of >700Gb of data. Here's what you do now: full table read, write to disk (100Gb read, 100Gb ...



Top 50 recent answers are included