BIDS or SQL data Tools for SQL 2012 SP1 database

I want to start customising reports from my Win 7 workstations. The SCCM server is SQL 2012 SP1
Do I need to install SQL Server Data Tools onto the workstation or can you still use BIDS (Visual Studio) from SQL 2008 media
Also I have saved some custom report .RDL files from previous assignments. Can I convert these to point to this site's database for use in SQL 2012 ?
Ian Burnell, London (UK)

Thanks Garth - so if I install 2008 BIDS on my W7 workstation then I will be able to connect to the CM2012/SQL 2012 database?
Yes you will be able to do that. I do it all the time for SQL 2005 or 2008 to SQL 2012 and SQL 2014. :-)
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Similar Messages

SQL Server Data Tools for SQL 2014 setup

Hello,
I have been using SQL server 2008 with Visual Studio 2008 to perform the ETL processes.
I have recently got SQL 2014 and realized that Business Intelligence Development Studio does not come with it so I have to download SQL Server Data Tools for Visual Basics 2012 or 2013 from:
https://msdn.microsoft.com/en-us/data/hh297027
Can someone advise what exactly I have to do if I want to start using SQL 2014 with SSDT? I still have VB 2008 installed and all my packages were created with that version.
Do I need to download VB 2012 or 2013 plus SSDT and then SSDT? Do I also uninstall VB2008?
Thanks in advnce

Hello,
If you want to keep developing packages for SQL Server 2008 then you need to use BIDS 2008, you cannot use SSDT.
If you want to upgrade BIDS projects to SSDT, then you can use Integration Services Project Conversion Wizard from Visual
Studio or SSIS Package Upgrade Wizard from SQL Server Management Studio (SSMS).
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Connection problem SQL Data Tools for VS

Hi
Appologies I hace this question in SSIS forum- but think this is a better place to ask.
I downloaded SSDT for VS in order to try some data mining on my developement edition of SS
When I try to use the mining model viewer (setting up source, sourec view and mining structure all worked fine) - it fails and tells me that "OLE DB error: OLE DB or ODBC error: Login failed for user 'XXXXX\DAVID-PC2$'.; 28000.
When settiing up the Impersanation Info- I used "Use the Service Account".
To get past this bit I was advised by Olaf Helper to change to "Use Credentials of current User" but then it also fails as apparently when you set up SSDT the system creates user credentials that differ to my windows authincation in my SSMS- So
the question is how and what do I change in SSDT so that my Windows Authincation becomes the same as "Use the service Account"- or make both talk to each other.
Hope you can help
Thks

What I'm doing is based is SSDT.
It appears to me that SSDT is configured for Analysis Services to be called Localhost
Went into the Analysis service project- and changed target server from localhost to DM_DEV - when I go into Config Manager I can see that SQL Services Analysis Services (DM_DEV) is running- so is SQL Server Brouser.
But when I'm in the project and try to run it I get
The project could not be deployed to the 'DM_DEV' server because of the following connectivity problems : A connection cannot be made. Ensure that the server is running. To verify or update the name of the target server, right-click on the project
in Solution Explorer, select Project Properties, click on the Deployment tab, and then enter the name of the server.
Is there maybe some specific way of putting DM_DEV- e.g in barckets use " " etc? what am I missing here!!
Thanks
D

Missing BI Data Tools in SQL Server 2014

Hi All!
I just doing the first steps in SSIS 2014 (RTM) after I played around a lot with SSIS 2014 (CTP2).
In case of CTP2 there was a separate download in MSDN called "SQL Server Data Tools for SQL Server 2014 CTP2" which contained VS2012 + the projects for SSIS, SSRS etc...
I'm missing these tools for SQL 2014 RTM. What do I do wrong? Could it be, that they are still unreleased?
Thanks in advance for your help.
Regards,
Patrick

Hi Patrick,
It's true that the SQL Server Data Tools (SSDT) is not shipped with SQL Server 2014 RTM DVD, and we need to download and install it from:
Microsoft SQL Server Data Tools - Business Intelligence for Visual Studio 2013
http://www.microsoft.com/en-us/download/details.aspx?id=42313
Regards,
Mike Yin
TechNet Community Support

SQL Server Data Tools - for visual studio 2013

Hi
I have recently installed Visual Studio 2013 and need to install the SQL Server Data Tools too, as I have done in Visual Studio 2012, but I can not find the software, where can I get it?
thanks
MsdnMezzo

Hi,
I hope you serve.Regards
SQL Server Data Tools for Visual Studio 2013 - 12.0.40403.0
Portuguese (Brazil)
http://download.microsoft.com/download/2/A/4/2A4211D0-AA9B-4496-A9D4-48CDBED5C25C/BR/SSDTSetup.exe
Chinese (PRC)
http://download.microsoft.com/download/2/A/4/2A4211D0-AA9B-4496-A9D4-48CDBED5C25C/CN/SSDTSetup.exe
German
http://download.microsoft.com/download/2/A/4/2A4211D0-AA9B-4496-A9D4-48CDBED5C25C/DE/SSDTSetup.exe
English (United States)
http://download.microsoft.com/download/2/A/4/2A4211D0-AA9B-4496-A9D4-48CDBED5C25C/EN/SSDTSetup.exe
Spanish
http://download.microsoft.com/download/2/A/4/2A4211D0-AA9B-4496-A9D4-48CDBED5C25C/ES/SSDTSetup.exe
French
http://download.microsoft.com/download/2/A/4/2A4211D0-AA9B-4496-A9D4-48CDBED5C25C/FR/SSDTSetup.exe
Italian
http://download.microsoft.com/download/2/A/4/2A4211D0-AA9B-4496-A9D4-48CDBED5C25C/IT/SSDTSetup.exe
Japanese
http://download.microsoft.com/download/2/A/4/2A4211D0-AA9B-4496-A9D4-48CDBED5C25C/JA/SSDTSetup.exe
Korean
http://download.microsoft.com/download/2/A/4/2A4211D0-AA9B-4496-A9D4-48CDBED5C25C/KO/SSDTSetup.exe
Russian
http://download.microsoft.com/download/2/A/4/2A4211D0-AA9B-4496-A9D4-48CDBED5C25C/RU/SSDTSetup.exe
Chinese (Taiwan)
http://download.microsoft.com/download/2/A/4/2A4211D0-AA9B-4496-A9D4-48CDBED5C25C/TW/SSDTSetup.exe

How to Custom Report using sql server report builder for SCCM 2012 SP1

Hi ,
I am new to database, if i want to create a manual report using sql server report builder for SCCM 2012 SP1, what step should i take.
i want to create a report in which computer name, total disk space, physical disk serial no come together. i already added class (physical disk serial no.) in hardware inventory classes. refer snapshot

Hi,
Here is a guide on how to create custom reports in Configuration Manager 2012, it is a great place to start, change to the data you want to display instead.
http://sccmgeekdiary.wordpress.com/2012/10/29/sccm-2012-reporting-for-dummies-creating-your-own-ssrs-reports/
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

Date formats for SQL statements used by recordset object

Hi,
Date formatting appears to be quite problematic for Business One. I did a forum search for date issues and I don't think I saw any of them with an "answered" status. I have an issue with formatting a date for the creation of an SQL statement that the DI sends to SQL Server 2005. I need to format a date so that the localization parameters don't matter for either the client machine or SQL Server's machine. We don't have a problem as long as our machines are localized as USA.
I have PL 22 and I have a form - ours - where I use the Today() function to fill a date field. So this is a date that is not entered by the user. The result of this function is consistent with the localization parameters on my machine. We have two other date fields on the form where the user must type in the date.
As a test, I changed my machine to the UK parameters. I then set up the language parameters of Business One for English(United Kingdom). I changed the date format specifications in Business One so that its format is dd/mm/yy. I then brought up the form and the field that is formatted by the above function arrived in the form's field as dd/mm/yy. I then typed in the two other dates in the same format and added the record to the database. The form's table is user-defined.
I dismissed the form then brought it back up loaded with the new record. The date that was entered by the function appeared in USA format (mm/dd/yy). The dates that were typed in appeared in the Business One format (dd/mm/yy). This of course is not consistent.
When I looked at what got into the database, the formats were the opposite. Weird! To make matters really confusing, I run an SQL statement within SQL Server Mgt Studio, and use the WHERE clause to filter on the date that was based on the function. It didnt matter what format I used for the WHERE clause, the record came up. Does anyone have any idea about how I can ensure that I always use the correct date format for SQL statements passed by Business One to SQL Server regardless of where in the world the application is being run?
Thanks,
Mike

Ian,
Here's what I'm concerned about: Im using the date in a WHERE clause.
Assume the date is Aug 3, 2007.
"SELECT * FROM Table WHERE StartDate > 8/3/2007"
OR
"SELECT * FROM Table WHERE StartDate > 3/8/2007"
If the client machine is set up as USA, the today function will provide the date as formatted in the first query. If the database server is setup as lets say the UK, I believe that SQL Server query parser will interpret the date as Mar 8, 2007.
If the client machine is set up as UK, the today function will provide the date as formatted in the second query. If the database server is setup as lets say USA, I believe that SQL Server query parser will also interpret the date as Mar 8, 2007.
In both cases it would be wrong.
I know I could use the DATEPART function to get the three parts and this will make the code indifferent to the localization specs of the client machine. I need to then be able to concatenate those date parts for the WHERE clause so that the localization specifications of the database server dont matter.
Thanks,
Mike

Versioning Tool for SQL Server?

Problem:
Does Microsoft have a versioning tool for SQL server?
I'm thinking about similiar tool as visual studio team foundation but for SQL server?
WOuld like to see any changes in a stored procedure in different version.

Additionally you can also refer below article.
http://blogs.msdn.com/b/bahill/archive/2009/07/31/come-visit-revisit-the-beer-house-continuous-integration.aspx
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
Praveen Dsa | MCITP - Database Administrator 2008 |
My Blog | My Page

SQL 2014 license for SQL 2008

Hi,
I'm purchasing SQL 2014 license.
Can I use the SQL 2014 license for SQL 2008 or 2012.
Thanks,
Sathish
Sathish

Hi Sathish,
For more detailed information regarding to the license issue, please call 1-800-426-9400, Monday through Friday, 6:00 A.M. to 6:00 P.M. (Pacific Time) to speak directly to a Microsoft licensing specialist. For international customers, please use the
Guide to Worldwide Microsoft Licensing Sites to find contact information in your locations.
Regards,
Elvis Long
TechNet Community Support

SSIS 2008 package conversion to SSIS 2012 using SQL Data Tools generating warning There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "Microsoft.SqlServer.DTSRuntimeWra

I am seeing the following warning is a SSIS C# script and receive a SSIS abort when I attempt to run the package.
The SSIS log indicates the package is failing at about this same step in the process.
I have also included the file SSQLDUMPER_ERRORLOG.log that SSIS generates when it aborts below.
My SSIS package has been set to 64-bit and I only have 64-bit SQL Server 2012 installed on the box.
I migrated the package using the latest version of Data Tools that came out around mid July 2014.
I edited all connection manager strings to point to 64-bit SQL Server and I run using the following command
I edited the run string to point to the new 64 bit DTExec and attempted to run.
C:\Program Files\Microsoft SQL Server\110\DTS\Binn\DTExec.exe" /Rep V /F PkgMigration.dtsx .........................
A significant amount of work does occur as reflected by the log steps prior to DTEXEC aborting but the log does just quit in mid sentence so not sure if it might have actually got a bit further.
Any help on understanding what is happening here would be most appreciated.
Warning 1 There was a mismatch between the processor
architecture of the project being built "MSIL" and the processor architecture of the reference "Microsoft.SqlServer.DTSRuntimeWrap, Version=11.0.0.0, Culture=Neutral, PublicKeyToken=89845dcd8080cc91", "x86". This mismatch may
cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a
processor architecture that matches the targeted processor architecture of your project. C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets
1605 5 sc_5756696d96034309a51afe69fed2eb44
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 1: 6100
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 2: 0
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 3: 0:0
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 4: 00A8B770
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 6100
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags = 0x0
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x00A8B770
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExceptionRecordPtr = 0x00000000
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x00000000
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName = <NULL>
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0007.mdmp
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
(1CBC:1808) 08/14/14 10:36:47, ACTION, DTExec.exe, Watson Invoke: No
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 1: 10124
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 2: 0
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 3: 0:0
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 4: 0012B770
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 10124
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags = 0x0
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x0012B770
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExceptionRecordPtr = 0x00000000
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x00000000
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName = <NULL>
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0008.mdmp
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
(2724:2488) 08/14/14 10:43:09, ACTION, DTExec.exe, Watson Invoke: No
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 1: 8716
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 2: 0
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 3: 0:0
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 4: 0072B770
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 8716
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags = 0x0
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x0072B770
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExceptionRecordPtr = 0x00000000
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x00000000
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName = <NULL>
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0009.mdmp
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
(2240:89C) 08/14/14 10:51:56, ACTION, DTExec.exe, Watson Invoke: No
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 1: 8856
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 2: 0
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 3: 0:0
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 4: 009AB770
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 8856
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags = 0x0
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x009AB770
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExceptionRecordPtr = 0x00000000
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x00000000
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName = <NULL>
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0010.mdmp
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
(7B8:1E68) 08/14/14 11:01:36, ACTION, DTExec.exe, Watson Invoke: No
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 1: 1292
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 2: 0
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 3: 0:0
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 4: 00BFB770
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 1292
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags = 0x0
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x00BFB770
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExceptionRecordPtr = 0x00000000
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x00000000
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName = <NULL>
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0011.mdmp
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
(229C:1CD8) 08/14/14 11:45:45, ACTION, DTExec.exe, Watson Invoke: No
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 1: 4220
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 2: 0
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 3: 0:0
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 4: 0019B770
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 4220
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags = 0x0
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x0019B770
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExceptionRecordPtr = 0x00000000
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x00000000
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName = <NULL>
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0012.mdmp
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
(2520:2624) 08/14/14 12:05:47, ACTION, DTExec.exe, Watson Invoke: No
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 1: 8408
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 2: 0
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 3: 0:0
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 4: 00000000003ECC18
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 8408
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags = 0x0
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x00000000003ECC18
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExceptionRecordPtr = 0x0000000000000000
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x0000000000000000
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName = <NULL>
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
(1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
(1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0001.mdmp
(1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll'
(1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
(1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
(1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
(1B5C:20C0) 08/18/14 14:21:50, ACTION, DTExec.exe, Watson Invoke: No

Hi GaryAMiller,
It seesm this is a know ssue. Please take a look at the following simialr issue at Microsoft Connect site:
MSB3270: Mismatch between the processor architecture:
https://connect.microsoft.com/VisualStudio/feedback/details/804933/msb3270-mismatch-between-the-processor-architecture-fakes-framework
If this issue still persists, I would suggest
opening a case with Microsoft Customer Support Services (CSS)(http://support.microsoft.com), so that a dedicated Support Professional can assist you in a more efficient manner.
If you have any feedback on our support, please click
here.
Elvis Long
TechNet Community Support

Tools for SQL upgrade

Hi Team,
Are you aware of any tool(MS or third party) which can be used for upgrading SQL 2005 to 2012 side by side.Something which can help migrate at an instance level i.e move databases, copy logins,jobs etc.Manual backup and restore process is
very tedious and also time consuming specifically in case of upgrades in higher numbers.
Thanks

Hello,
Try the following tools:
http://www.apexsql.com/sql_tools_diff.aspx
http://www.red-gate.com/products/sql-development/sql-data-compare/
http://www.activedbsoft.com/overview-migrate.html
Hope this help.
Regards,
Alberto Morillo
SQLCoffee.com

Error during DatabaseCopy using SAP tools for SQL Server (v7.12)

I'm trying to perform a system copy from PRD to QAS. The database has been mounted to QAS via detach and attach method. I did a DBCC on the database and everything looks OK. I'm running SAPINST (SAP Tools for MSSQL) and selecting the Database Copy option. The source database has a schema of DBO. Both PRD and QAS are running SAP 4.7/Basis 620. The target schema is QAS. SAPINST fails in step 2 (Define Params) with:
"This service cannot be used for a system with SAP ABAP release 620"
Is this message misleading? Has anyone receive this message before.
UPDATE:
I donwloaded the latest version of SAP Tools for MSSQL and now it failes during the execution phase on step, "Convert DB objects to new schema".
Here is the log:
Process environment
===================
Environment Variables
=====================
=::=::\
=C:=C:\Program Files\sapinst_instdir\MSS\CPY
ALLUSERSPROFILE=C:\Documents and Settings\All Users
APPDATA=C:\Documents and Settings\r3tadm.STAG\Application Data
CLIENTNAME=TRAIMONOTEBOOK
ClusterLog=C:\WINDOWS\Cluster\cluster.log
CommonProgramFiles=C:\Program Files\Common Files
COMPUTERNAME=STAG
ComSpec=C:\WINDOWS\system32\cmd.exe
DBMS_TYPE=MSS
FP_NO_HOST_CHECK=NO
HOMEDRIVE=C:
HOMEPATH=\Documents and Settings\r3tadm.STAG
LOGONSERVER=
STAG
MSSQL_DBNAME=R3T
MSSQL_SERVER=stag
NUMBER_OF_PROCESSORS=4
OS=Windows_NT
Path=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Dell\SysMgt\RAC5;C:\Program Files\Dell\SysMgt\oma\bin;C:\Program Files\Dell\SysMgt\oma\oldiags\bin;C:\Program Files\Microsoft SQL Server\80\Tools\BINN;C:\usr\sap\R3T\SYS\exe\run
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_IDENTIFIER=x86 Family 6 Model 15 Stepping 6, GenuineIntel
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=0f06
ProgramFiles=C:\Program Files
SAPINST_EXEDIR_CD=C:/STM/I386
SAPINST_JRE_HOME=C:/WINDOWS/TEMP/3/sapinst_exe.3012.1234409473/jre
SAPLOCALHOST=stag
SESSIONNAME=RDP-Tcp#25
SystemDrive=C:
SystemRoot=C:\WINDOWS
TEMP=C:\WINDOWS\TEMP\3
TMP=C:\WINDOWS\TEMP\3
USERDOMAIN=STAG
USERNAME=r3tadm
USERPROFILE=C:\Documents and Settings\r3tadm.STAG
windir=C:\WINDOWS
User: STAG\r3tadm, Id: S-1-5-21-2727398557-1322528747-1943968026-1019
Working directory: C:/Program Files/sapinst_instdir/MSS/CPY
Current access token
====================
Could not get thread token. Last error: 1008. I assume that no thread token exists.
Got process token.
Privileges:
Privilege SeBackupPrivilege, display name: Back up files and directories, not enabled.
Privilege SeRestorePrivilege, display name: Restore files and directories, not enabled.
Privilege SeShutdownPrivilege, display name: Shut down the system, not enabled.
Privilege SeDebugPrivilege, display name: Debug programs, not enabled.
Privilege SeAssignPrimaryTokenPrivilege, display name: Replace a process level token, not enabled.
Privilege SeSystemEnvironmentPrivilege, display name: Modify firmware environment values, not enabled.
Privilege SeIncreaseQuotaPrivilege, display name: Adjust memory quotas for a process, not enabled.
Privilege SeChangeNotifyPrivilege, display name: Bypass traverse checking, enabled.
Privilege SeRemoteShutdownPrivilege, display name: Force shutdown from a remote system, not enabled.
Privilege SeTcbPrivilege, display name: Act as part of the operating system, not enabled.
Privilege SeUndockPrivilege, display name: Remove computer from docking station, not enabled.
Privilege SeSecurityPrivilege, display name: Manage auditing and security log, not enabled.
Privilege SeTakeOwnershipPrivilege, display name: Take ownership of files or other objects, not enabled.
Privilege SeLoadDriverPrivilege, display name: Load and unload device drivers, not enabled.
Privilege SeManageVolumePrivilege, display name: Perform volume maintenance tasks, not enabled.
Privilege SeSystemProfilePrivilege, display name: Profile system performance, not enabled.
Privilege SeImpersonatePrivilege, display name: Impersonate a client after authentication, enabled.
Privilege SeSystemtimePrivilege, display name: Change the system time, not enabled.
Privilege SeCreateGlobalPrivilege, display name: Create global objects, enabled.
Privilege SeProfileSingleProcessPrivilege, display name: Profile single process, not enabled.
Privilege SeIncreaseBasePriorityPrivilege, display name: Increase scheduling priority, not enabled.
Privilege SeCreatePagefilePrivilege, display name: Create a pagefile, not enabled.
Groups:
Group count: 14
\LOCAL S-1-2-0 Attributes: SE_GROUP_MANDATORY SE_GROUP_ENABLED_BY_DEFAULT SE_GROUP_ENABLED
BUILTIN\Administrators S-1-5-32-544 Attributes: SE_GROUP_MANDATORY SE_GROUP_ENABLED_BY_DEFAULT SE_GROUP_ENABLED SE_GROUP_OWNER
\Everyone S-1-1-0 Attributes: SE_GROUP_MANDATORY SE_GROUP_ENABLED_BY_DEFAULT SE_GROUP_ENABLED
BUILTIN\Users S-1-5-32-545 Attributes: SE_GROUP_MANDATORY SE_GROUP_ENABLED_BY_DEFAULT SE_GROUP_ENABLED
STAG\SAP_R3T_LocalAdmin S-1-5-21-2727398557-1322528747-1943968026-1021 Attributes: SE_GROUP_MANDATORY SE_GROUP_ENABLED_BY_DEFAULT SE_GROUP_ENABLED
STAG\SAP_LocalAdmin S-1-5-21-2727398557-1322528747-1943968026-1023 Attributes: SE_GROUP_MANDATORY SE_GROUP_ENABLED_BY_DEFAULT SE_GROUP_ENABLED
STAG\None S-1-5-21-2727398557-1322528747-1943968026-513 Attributes: SE_GROUP_MANDATORY SE_GROUP_ENABLED_BY_DEFAULT SE_GROUP_ENABLED
NT AUTHORITY\INTERACTIVE S-1-5-4 Attributes: SE_GROUP_MANDATORY SE_GROUP_ENABLED_BY_DEFAULT SE_GROUP_ENABLED
NT AUTHORITY\NTLM Authentication S-1-5-64-10 Attributes: SE_GROUP_MANDATORY SE_GROUP_ENABLED_BY_DEFAULT SE_GROUP_ENABLED
NT AUTHORITY\Authenticated Users S-1-5-11 Attributes: SE_GROUP_MANDATORY SE_GROUP_ENABLED_BY_DEFAULT SE_GROUP_ENABLED
\ S-1-5-5-0-36828865 Attributes: SE_GROUP_MANDATORY SE_GROUP_ENABLED_BY_DEFAULT SE_GROUP_ENABLED SE_GROUP_LOGON_ID
NT AUTHORITY\REMOTE INTERACTIVE LOGON S-1-5-14 Attributes: SE_GROUP_MANDATORY SE_GROUP_ENABLED_BY_DEFAULT SE_GROUP_ENABLED
NT AUTHORITY\This Organization S-1-5-15 Attributes: SE_GROUP_MANDATORY SE_GROUP_ENABLED_BY_DEFAULT SE_GROUP_ENABLED
STAG\SAP_R3T_GlobalAdmin S-1-5-21-2727398557-1322528747-1943968026-1018 Attributes: SE_GROUP_MANDATORY SE_GROUP_ENABLED_BY_DEFAULT SE_GROUP_ENABLED
ERROR 2009-02-11 19:31:46.529 [sixxcstepexecute.cpp:984]
FCO-00011 The step MoveSchema with step key |SAPMSSTOOLS|ind|ind|ind|ind|0|0|MssSysCopy|ind|ind|ind|ind|4|0|MssSchemaMove|ind|ind|ind|ind|2|0|MoveSchema was executed with status ERROR .
TRACE 2009-02-11 19:31:46.544
Call block:CallBackInCaseOfAnErrorDuringStepExecution
 function:CallTheLogInquirer
is validator: true
WARNING 2009-02-11 19:31:46.544 [iaxxejshlp.cpp:150]
Could not get property IDs of the JavaScript object.
ERROR 2009-02-11 19:31:46.544 [iaxxejsctl.cpp:492]
FJS-00010 Could not get value for property .
TRACE 2009-02-11 19:31:46.544
A problem occurs during execution the inquirer callback. SAPinst will switch back to the standard behaiviour.
TRACE 2009-02-11 19:31:46.544 [iaxxgenimp.cpp:707]
 CGuiEngineImp::showMessageBox
<html> <head> </head> <body> An error occurred while processing service SAP Toools for MS SQL Server > Database Copy. You may now <ul> <li> choose Retry to repeat the current step. </li> <li> choose View Log to get more information about the error. </li> <li> stop the task and continue with it later. </li> </ul> Log files are written to C:\Program Files/sapinst_instdir/MSS/CPY. </body></html>
TRACE 2009-02-11 19:31:46.544 [iaxxgenimp.cpp:1245]
 CGuiEngineImp::acceptAnswerForBlockingRequest
Waiting for an answer from GUI
Edited by: Tony Raimo on Feb 12, 2009 4:37 AM

This is looks like permission issue on source folder
Copy source in to your local drive and try again.
I had same issue and able to resolve after copy EXP1 EXP2 and EXP3 folder in to local drive C: with Everyone full access
Yogesh

SQL Loader tool for control file creation

We are planning to use SQL*Loader to move a lot of data from mainframe to Oracle 10g database. We will write the data in flat files and use SQL*Loader to load these files into tha database. There are more than 100 tables with lot of columns in each. So, I was just wondering if there is any tool available (visual mappings etc.) that can help create the control files for the SQL*Loader, so that I don't have to manually type all the lengthy control files
Thanks for any help,
Sam

sql*loader is capable to generate the controlfile for external tables which are pretty much the same
Something like
sqlldr scott/tiger ulcase1 EXTERNAL_TABLE=GENERATE_ONLYhttp://download-west.oracle.com/docs/cd/B10501_01/server.920/a96652/ch08.htm#1006964

While creating the Data source for Sql server am getting this error?

Hi i new to Power BI sites and office 365,
For my first step
1. i have successful creaeted Gateway in Office 365
2.Now i have creating the Data source for that gateway using Sql server R2
3.While Creating the Data source using the Corresponding gateway i have given and next phase set Credentials phase i have noticed one pop up window and it will shows me like
Data source Settings and below in that window it will show's u the things like
Datasource Name.
Loading......
Credentials type:
Privacy Level:
Failed to verify parameter
I will get this results finally ,so hw should i achive this probelm ,Please let me know if any one knows
So kindly give me the proper answer for this.
Regards

Any suggestions for Chinnarianu?
Thanks!
Ed Price, Azure & Power BI Customer Program Manager (Blog,
Small Basic,
Wiki Ninjas,
Wiki)
Answer an interesting question?
Create a wiki article about it!

SQL Developer Data Modeler for SQL Server 2008

I am not able to connect to my SQL Server 2008 from the SQL Developer Data Modeler. Although I do have jtds-1.2.jar on my machine and I can connect the SQL server through the SQL Developer, but still i'm not able to connect through the data modeler. I need to re-engineer and generate data model for some existing schemas.
Here is what I'm following:-
File->Data Modeler -> import -> Data Dictionary -> Add new connection -> JDBC ODBC Bridge -> Other Third Party Driver
now when I'm giving the JDBC URL and the Driver, It throws an error message stating that the driver could not be found.
Please let me know what I can do to solve this, any help would be appreciated.
Regards,
AVA

I'd try 1st to connect to the db from sqldeveloper (through jtds - no ODBC involved) and see if you can browse your db and issue sql statements in a worksheet. Then export that connection in xml format and import that from the modeler.

BIDS or SQL data Tools for SQL 2012 SP1 database

Similar Messages

Maybe you are looking for