We want to implement a cold DRP strategy here, Is there any info where:
1. To transfer syslogins to DR Server (is BCP in/out sufficient).
2. SQL to extract DTS/Agent jobs from msdb.
3. I am aware of how to fix broken logins.
thanks all,
Paul
I'm running Windows 7 64-bit (yes I'm sure) and when trying to install any version of SQL Server Express 2012 I get the following Error messages:
1) The following error has occurred:SQL Server Setup has encountered an error when running a Windows Installer file.Windows Installer error message: Error opening installation log file. Verify that the specified log file location exists and that you can write to it. Windows Installer file: C:UsersStudent AppDataLocal TempSQL Server 2012Setup1033_ENU_LPx64setupsqlsupport_msiSqlSupport.msi Windows Installer log file: C:Program FilesMicrosoft SQL Server110Setup BootstrapLog20130125_224835SqlSupport_Cpu64_1_ComponentUpdate.log Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup. URL... LinkID=20476&ProdName= Microsoft%20SQL%20Server& EvtSrc=setup.rll&EvtID=50000& ProdVer= 11.0.21 00.60&EvtType=0xDC80C325
2) SQL Server Setup failure.
SQL Server Setup has encountered the following error: Could not find a part of the path 'C:Program FilesMicrosoft SQL Server110Setup Bootstrap Log 20130125_131045'..
I have all .NET framework 3.5 and 4.0 installed, Visual Studio 2012, Visio 2012... everything else is running fine, but I can't get this to work!
Hi All,
my dba folks are coming back with an answer to a question that sounds strange and I thought I would check on here.
Situation.
We are using an ETL tool I developed to move data around and building a DW on 2005. In some cases we are using the bulk loader to load and in some cases the tool itself.
One of the defaults of the tool is to truncate trailing blanks....and so fields that contain only blanks get truncated to a zero length character string.
When reloading the data with the tool it carries a null indicator next to the field value so the zero length character string is loaded as not null.
When loading with the bulk loader the dbas are telling me that the field is translated to a null. Note that they want some fields translated to null so they are using the keepnulls parameter.
On other databases (and built into the tool because this is so) the bulk loaders usually allow the specification of the load statement at column level and the specification of a 'null character sting' to be translated to null if this string is found. I put an example below.
I seem to recall that SQL Server 7 had some sort of bulk loader that allowed specification of columns at column level......for example offsets or whatever and the specification of fields to be interpreted as nulls. (Though that was a long time ago.)
I have searched through the manual and I don't see an option there any more to specify a character that will be interpreted to a null by the bulk loader.
Is it possible in 2005 to specify a character such that when the bulk loader sees it the field will be set to null?? And not just set fields to null which are not present in the load file?
(Just by the way, we are going to make the truncate trailing blanks optional and it's easy....it's just that I thought this kind of null if option was available in 2005 and I am keen to know if it is not there, either gone or never was...)
Thanks in Advance and Best Regards
Peter
Example of how Oracle does it...on page
http://www.csee.umbc.edu/help/oracle8/server.815/a67792/ch05.htm#5754
NULLIF Keyword
Use the NULLIF keyword after the datatype and optional delimiter specification, followed by a condition. The condition has the same format as that specified for a WHEN clause. The column's value is set to null if the condition is true. Otherwise, the value remains unchanged. NULLIF field_condition
The NULLIF clause may refer to the column that contains it, as in the following example: COLUMN1 POSITION(11:17) CHAR NULLIF (COLUMN1 = "unknown")
when I restart the computer always come a massage telling me that the SQLDUMPER library failed initialization. Your installation is either corrupt or has been tampered with. Please uninstall then re-run setup to correct this problem.
View 2 Replies View RelatedHi,
I have a package which reads data from set of tables, goes thru a script component for some data changes and written to a flat file. To speed up the process, I have created 6 threads of this same sequence, but instead of writting to different files, I am joining the outputs of all 6 scripts components using 'UNION ALL' and writting it to a single file. I have to execute this for different input years and so calling this data flow within a 'Foreach loop' container for multiple years. When I ran this package for single year, it ran without any error. But when I ran it for multiple years (in debug mode), after processing 3 years, the package just stopped running. It does not abort, but just created a SQLDUMPER Error log file with the following contents.
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 2184
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags = 0x0
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x0100C5D0
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExceptionRecordPtr = 0x00000000
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x00000000
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName = <NULL>
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
07/08/06 22:59:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
07/08/06 22:59:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:Program Files (x86)Microsoft SQL Server90SharedErrorDumpsSQLDmpr0002.mdmp
07/08/06 22:59:09, ACTION, DtsDebugHost.exe, Watson Invoke: No
I have searched this forum and saw one thread with this error message, but there is no response for that. Do you guys know what could be the problem?
Thanks.
Does anyone know if this SQL is part of MS Office or is it XP... I haven't figured that out. It says reinstall the program but doesn't say what program. I know I never intentionally installed an SQL program.
At this time I get the same message as everyone seems to be getting - SQL Dumper Library failed... reinstall ....
The problem for me started when I added Office 2007 and added the business contacts program.
Any ideas are appreciated!
I just added a post but I don't see it so here I go agian, sorry if it shows up later and there ends up being two of them.
I started getting the error message - SQL Dumper Library failed ... Please reinstall... it doesn't say what to reinstal. Does anyone know if this is part of Office or XP? My problem started when I added Office 2007 and the additional Business contacts program from the web site.
I did get SQL 2005 and installed it but it says it isn't working. When I click to repair it, it wants the disk, again I don't know what disk or program it wants, although it will not fix it from the XP disk.
Any help would be appreciated!
Hi
I am constantly getting this error message in the Application log after installing SQL 2005 last night followed by SP1 (say 5 times a minutes). See below:
EventType sql90exception, P1 reportingservicesservice.exe, P2 9.0.2047.0, P3 443f5953, P4 sqldumper_unknown_module.dll, P5 0.0.0.0, P6 00000000, P7 0, P8 00e8ed9d, P9 00000000, P10 NIL.
I have reservice packed SQL 2005 but made no difference - it is running on a Windows 2003 server with all the latest MS patches.
Does anyone know the solution or possible solution to this issue?
Thanks
Matt