I'm trying to make simple backup of my database. I clicked "Create Manual Backup" and it created b004 file.
my heroku/postgres panel
When I open b004 file in TextEditor there are mostly weird signs (for example: Ym|∏€◊n....)
I was expecting simple .xml file. I assume that all my data is in b004, but is there a way to convert it to more "readable" format?
Related
I cannot find much in the way of written instructions on how to copy my database to Plesk.
This page simply says, "To create a database and a database user: Go to Databases > Add Database."
And then it shows a screenshot which does not match what I have; specifically, it shows an "Import Dump" button which I do not have:
This is what I see in my session (no Import Dump button):
I zipped a .bak file of my database contents and uploaded it to the File Manager's Files section:
...but how do I move it from there to the Database area, and what do I then do to populate my tables with the contents of the .bak file?
Is this something that should be done using Microsoft SQL Server Management Studio, or from "My Little Admin," or what?
I was able to create the (empty) tables by running a script.sql file I generated from my local database. My Little Admin indicates that the empty tables do exist on the server, for example here is the ACTORS table:
OTOH, SSMS shows that the database exists, but shows no tables:
I am new to SSIS, I have already designed a package and configured SSIS Log provider for Text Files.
This works fine and log files are generated successfully.
We have a monitoring team, they use this log file for monitoring. They are unable to read the log files since the file encoding is in Unicode format.
They are expecting a non unicode format for their monitoring.
I tried to change the existing log file encoding to ANSI but when I re-run the package my log file has been created again with UNICODE encoding.
Is any way we can create log files using SSIS Log provider for Text Files with non unicode encoding. Kindly suggest me any workaround. I am unable to find solution for the past two days.
Trying to figure out the issue
Since SSIS Log provider for Text Files use a File connection manager for logging purposes, you don't have the choice to edit the file encoding within the SSIS package because this type of connection manager can be used for different files format (excel, text ...).
While searching for this issue it looks like if the log is created for the first time by SSIS it will write unicode data.
why are my log files getting generated with a space between every two characters?
Why is my SSIS text logfile formatted in this way?
Possible workaround
Try to create an empty text file using notepad and save it with ANSI encoding.
Then select this file from the SSIS logging configuration.
Other helpful links
Change the default of encoding in Notepad
Add Logging with SSIS
Update 1 - Experiments
To test the workaround i provided i have run the following experiments:
I add SSIS Logging and created and a new log file
After executing the package the file is create in Unicode (to check that i opened the file using notepad and click Save As the encoding shown in the combobox is Unicode)
I create a new file using Notepad and save it using Ansi encoding as mentioned above.
In SSIS i changed the File connection manager to Use Existing instead of Create New and i selected the file i created
After executing the package the log is filled within the file and the encoding is still Ansi
I repeated executing the package several times and the undoing wont changes.
TL DR: Create a file with ANSI encoding outside the ssis package and within the package create a file connection manager, select Use Existing option and choose the created file. Use this file connection manager for logging purposes.
I am trying to read the content of my backup E.g.(testdb.bak) in a text format E.g.(Notepad or another text editor)
This command is retrieving only the file holds:
Restore HEADERONLY From disk = 'C:\backups\testdb.bak'
Is there any way or file extension, file type or format, where I can see the whole content of a backup? without restoring it.
Is there any way or file extension, file type or format, where I can see the whole content of a backup? without restoring it.
No there is no command in SQL Server which would let you see the content of .bak file. If you open it in notepad you would see some information and lots of garbage characters. This is also not supported
The best way to see its content is restore it on SQL Server database and run as many select statements you like on the tables.
I am using SQLite Database Browser to manage my databases.
However, I can't find a way to create a .db file out of my database.
Here is a picture of the options in SQLite Database Browser.
In File->Export, I can only create a sql file or a CSV file.
Is there a way to create a .db file out of SQLite Database Browser ?
If no, is there any other way of doing it ?
Sqlite doesn't really have a file extension. By convention, most people use sqlite3 - but you can use anything. Sqlite database is defined by the file format. (See more: http://www.sqlite.org/fileformat.html)
Is there something you're trying to accomplish specifically by using the .db format? If not, you can name it .db, or sqlite3, or whatever you'd like.
Rename HearthStoneData to HearthStoneData.db.
You need to find the file you are working on. Do not use "save as" . The address of the db file is in the top bar. Rename the file in the directory to .db
I use a Wordpress plugin called 'Shopp'. It stores product images in the database rather than the filesystem as standard, I didn't think anything of this until now.
I have to move server, and so I made a backup, but restoring the backup is proving a horrible task. I need to restore one table called wp_shopp_assets which is 18MB.
Any advice is hugely appreciated.
Thanks,
Henry.
For large operations like this it is better to go to command line. phpMyAdmin gets tricky when lots of data is involved because there are all sorts of timeouts in PHP that can trip it up.
If you can SSH into both servers, then you can do a sequence like the following:
Log in to server1 (your current server) and dump the table to a file using "mysqldump" --- mysqldump --add-drop-table -uSQLUSER -pPASSWORD -h
SQLSERVERDOMAIN DBNAME TABLENAME > BACKUPFILE
Do a secure copy of that file from server1 to server2 using "scp" ---
scp BACKUPFILE USER#SERVER2DOMAIN:FOLDERNAME
Log out of server 1
Log into server 2 (your new server) and import that file into the new DB using "mysql" --- mysql -uSQLUSER -pPASSWORD DBNAME < BACKUPFILE
You will need to replace the UPPERCASE text with your own info. Just ask in the comments if you don't know where to find any of these.
It is worthwhile getting to know some of these command line tricks if you will be doing this sort of admin from time to time.
try HeidiSQL http://www.heidisql.com/
connect to your server and choose the database
go to menu "import > Load sql file" or simply paste the sql file into the sql tab
execute sql (F9)
HeidiSQL is an easy-to-use interface
and a "working-horse" for
web-developers using the popular
MySQL-Database. It allows you to
manage and browse your databases and
tables from an intuitive Windows®
interface.
EDIT: Just to clarify. This is a desktop application, you will connect to your database server remotely. You won't be limited to php script max runtime, or upload size limit.
use bigdupm.
create a folder on your server witch is not easy to guess like "BigDump_D09ssS" or w.e
Download the http://www.ozerov.de/bigdump.php importer file and add them to that directory after reading the instructions and filling out your config information.
FTP The .SQL File to that folder along side the bigdump script and go to your browser and navigate to that folder.
Selecting the file you uploaded will start importing the SQL is split chunks and would be a much faster method!
Or if this is an issue i reccomend the other comment about SSH And mysql -u -p -n -f method!
Even though this is an old post I would like to add that it is recommended to not use database-storage for images when you have more than like 10 product(image)s.
Instead of exporting and importing such a huge file it would be better to transfer the Shopp installation to file-storage for images before transferring.
You can use this free plug-in to help you. Always backup your files and database before performing this action.
What I do is open the file in a code editor, copy and paste into a SQL window within phpmyadmin. Sounds silly, but I swear by it via large files.