file program .exe the result of database failI think the problem of long term storage files change utf 8 to ansi I can in .txt but database files is difficult I dont know how to do it.
It can open by excel readonly but codecs changed
Related
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'm currently working in Auditing a software we are supposed to start working on February. As part of the source code, we've recevied what seems to be a C file generated from a Pro*C file.
Pro*C files are compiled using the application "proc" into a C file, then you would use gcc to compile it into an actual executable file.
We are having some troubles with the previous owner of the application, and they refuse to provide us so far with the Pro*C file (pc extension).
I'm not sure if it's possible to revert it back from the C file to the Pro*C, using "proc" or any other tools.
Has anyone been able to do so, and if so, how?
Thanks in advance.
There is no decompiler for C to *Proc file. A C file containing SQL statement in it is call an embedded *Proc file, an utility provided by Oracle. Once you translate this embedded file to C by using a proc translator provided by Oracle it turn that *Proc file into a C file which modify these SQL statement with oracle provided library APIs.
Now my advice to you is, find out all the methods/functions in that C file (generated from a *Proc file) and check and understand what they are doing in Oracle database, especially all the database transactions. Once you understood that, just try to create your own C or C++ file by using ODBC driver api provided by Oracle.
While saving .sql files from SQL Server Management Studio in to my local windows folder, it looks to be including some binary characters making AccuRev comparisons impossible. I looked for possible save options and couldn't locate any. and couldn't find any. Any suggestions please?
If you can't tell AccuRev to handle this as UTF-8 files (this sucks - these days, all software should really know about UTF-8 and handle it correctly!), then you might need to do something in SQL Server Management Studio instead.
When you have a SQL statement open and you click on "File > Save", in the "Save" dialog, there is a little down-arrow to the right of the Save button:
If you click that (instead of just clicking on the button itself), you can select "Save with Encoding", which allows you to pick what encoding to use for your files - pick something like the Windows-1252 Western European - that should not have any UTF-8 Byte-Order Mark bytes at the start:
AccuRev does handle UTF-8 character encoding. However, older versions may not have that capability.
Make sure that the file is being saved using UTF-8. Anything else will have binary content and should be typed as such.
When you export sql files from MS SQL Server Management Studio in unicode (by default), it puts a "FF FE BOM" at the front of the file which forces programs to treat it as binary. Exporting as ANSI solved it. Choose "Save as ANSI Text".
I have a .sql file in my computer and I use msql command line client to open it presently. But it lacks graphical interface. Is there any software that i can install in my windows 7 PC so that i will have an interface similar to phpmyadmin to open .sql file saved in my PC?
maybe you can try MySQL Workbench. Here's the link
http://www.mysql.com/products/workbench/
Also, if you only need to read the contents of the .sql file, you can use Notepad++ or any other text file editor. But I would suggest Notepad++ since it supports alot of files and also provides formatting too.
http://www.notepad-plus-plus.org/
Export it as csv and use excel
In the Flat File Connection Manager screen there is a checkbox to specify that the file is encoded as Unicode, but there is no way to tell which encoding will be used (UTF-8, UTF-16, ...)
Is there an official Microsoft resource as to which encoding is used?
"Unicode" in Microsoft products tends to be UTF-16LE.