I've got XEON x64 server and after SQL Server 2005 installation found that the platform in property says AMD64 and not INTEL64 as expected.
I was assured by our service provider that AMD64 platform is the correct one as it was compiled for INTEL x64.
Does anybody have an answer to it?
I am using windows 98 and I want te use SQL server 7.0. I have installed the non-enterprise edition....But it won't work.... The service manager in istalled succesfully and all the other utilities to. But it still wont work. Is somebody out there who can help me on this.
I am writing applications for barcode readers that send and receive information via wi-fi to a 2003 Server running the full MS SQL Server 2005. The readers are both XP and CE .NET 5.00 based.
The information is time critical so I need to scan a barcode then send that information to the SQL Server and then in turn run a query based upon it which then displays on the reader. I have no problem with the XP devices as I can link via ODBC to the SQL Server. These work perfectly.
I can also run a program on a XP desktop using Remote Desktop on the CE device which again works fine.
The CE .NET 5.00 readers are a problem as I cannot use OBDC or OLE DB owing to the platform.
Is there any method available where I can query the SQL Server directly without using some kind of third party product like ViaDB from Odyssey Software? I cannot use replication owing to the time constaints.
Any suggestions or gentle prods would be appreciated.
We have to migrate several 64Bit SQL Servers to 32Bit platform. Due to the 64Bit source systems are all production system, the downtime is too limited. So we can only get the DB files via Detach way. Among the source systems, both SQL2000 and SQL2005 exist.
My question are:
Is it possible to migrate the DB from 64Bit to 32Bit via Detach/Attach?
We want to install 2 applications that run on SQL server 2005 but the requirement of database installation are different Collation setting ( One require Dictionary order, case-insensitive, for use with 1252 Character Set and other require Dictionary order, case-sensitive, for use with the 437 (US English) Character set). So the question here could I install both two applications successfully on same platform ? and if yes how?
Since 2 weeks now I'm trying to figure out how to get SQL CE 3.5 into the CE 6.0 R2 image (I'm building my own image with platform builder 6.0, latest patches - until march 2008 - installed).
There is no Catalog item in my "Catalog item view" not even an older version of SQL! In Platform builder 5.0 there were Items in the Catalog and - as expected - by selecting them I got the server into the image.
I also tried to add "SYSGEN_SQLMOBILE = 1" to the project environment variables, which resulted in having build errors instead of getting a working image.
There are also some postings around in the internet telling how to add the required dll's manually. (Hey, Microsoft, do we live in stone age or in the 21st century?)
Btw. installing the cab files is possible for me, but of course not for our customers.
Are there any sugesstions how to get a catalog item?
I am doing some technology research for a new app and was wondering about the desktop operating system support for SQL Server compact edition. This app has a PC component and a mobile component, and both need to be data enabled, with syncronization between the PC and the mobile device.
So it seems like SSCE would be a good fit. Just run the SSCE client on both the PC and the device. But in the system requirements for SSCE it only gives XP as a valid desktop OS...
Is that correct? Obviously, desktop platform support for a production app will need to be broader than just XP.
Will SSCE desktop run on Win98,Win2000,XP Home, and Vista?
Is this possible to connect do the Database Engine (on sql server 2005 on XP platorm - file *.mdf (not mobile *.sdf)) from win CE 5.0?
I tried to do this : ConnectionStringSQLServerCE = "Data Source=WORK_STATION\SQLEXPRESS;Initial Catalog=dbMachines;Integrated Security=False;Password=Panel;User ID=Panel";
SqlCeConnectionCE = new SqlConnection(ConnectionStringSQLServerCE);
SqlCeConnectionCE.Open();
but I catch error: catch (PlatformNotSupportedException ex) €žPlatformNotSupportedException€? I noticed that I see server because when I use: ConnectionStringSQLServerCE = "Data Source=WORK_STATION\SQLEXPRESS";
zwraca błąd typu
catch (SqlException ex) €œLogin failed for user ''. The user is not associated with a trusted SQL Server connection.€?
I used using System.Data.SqlClient;
from Compact Framework 2.0 under Visual Studio 2005 Device Application Windows CE 5.0
Our server is 64 bits OS. After SQL instalation we try to load the Reports web site and the server return the following error, can anyone help us?:
Attempted to load a 64-bit assembly on a 32-bit platform. Use ReflectionOnlyLoad() instead if trying to load for reflection purposes.Server Error in '/Reports' Application.
Attempted to load a 64-bit assembly on a 32-bit platform. Use ReflectionOnlyLoad() instead if trying to load for reflection purposes. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.BadImageFormatException: Attempted to load a 64-bit assembly on a 32-bit platform. Use ReflectionOnlyLoad() instead if trying to load for reflection purposes.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[BadImageFormatException: Attempted to load a 64-bit assembly on a 32-bit platform. Use ReflectionOnlyLoad() instead if trying to load for reflection purposes.] System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) +0 System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +211 System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +141 System.Reflection.Assembly.Load(String assemblyString) +25 System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +32
[ConfigurationErrorsException: Attempted to load a 64-bit assembly on a 32-bit platform. Use ReflectionOnlyLoad() instead if trying to load for reflection purposes.] System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +596 System.Web.Configuration.CompilationSection.LoadAllAssembliesFromAppDomainBinDirectory() +3479065 System.Web.Configuration.CompilationSection.LoadAssembly(AssemblyInfo ai) +46 System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection compConfig) +177 System.Web.Compilation.BuildProvidersCompiler..ctor(VirtualPath configPath, Boolean supportLocalization, String outputAssemblyName) +180 System.Web.Compilation.ApplicationBuildProvider.GetGlobalAsaxBuildResult(Boolean isPrecompiledApp) +3446645 System.Web.Compilation.BuildManager.CompileGlobalAsax() +51 System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled() +462
[HttpException (0x80004005): Attempted to load a 64-bit assembly on a 32-bit platform. Use ReflectionOnlyLoad() instead if trying to load for reflection purposes.] System.Web.Compilation.BuildManager.ReportTopLevelCompilationException() +57 System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled() +612 System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters) +456
[HttpException (0x80004005): Attempted to load a 64-bit assembly on a 32-bit platform. Use ReflectionOnlyLoad() instead if trying to load for reflection purposes.] System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +3426871 System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +88 System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +149
Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42
As painful as it is proving out to be, I am trying to create a single package that is vendor neutral between SQL Server and Oracle.
At first, I thought that as long as I was going OLEDB in and out, and I ensured that my SQL syntax was generic enough, I'd be OK.
Well, not exactly. I am finding there is more to this. Specifically, metadata gets generated differently based on the source/targets.
For example, on an OLE DB Source task, datatypes will vary (i.e. NUMBER in Oracle vs Int in SQL). The job here is to pick the common denominator for the SSIS specific type. Time consuming, but doable, I think.
Another issue is on an OLE DB Desitnation. If you choose Table for Data Access Mode, this value gets written to the dtsx XML file. So, even when both RDBMS have the same schema (which is an obvious prereq) if choosing SQL Server "dbo.DimTable" will get written to the file and for Oracle "SCHEMA.DIMTABLE" will get written.
So, I am am wondering, what is the best way to address this?
My inital thought was using a dtsConfig file (which I am already using extensively) and set the target table names accordingly. This approach would have the added benefit of allowing for post-deployment configuration changes should a table name change, for example.
This section of the dtsx file shows the values of interest:
Code Snippet <component id="138" name="OLE_DST_DimTable" componentClassID="{E2568105-9550-4F71-A638-B7FE42E66922}" description="OLE DB Destination" localeId="-1" usesDispositions="true" validateExternalMetadata="True" version="4" pipelineVersion="0" contactInfo="OLE DB Destination;Microsoft Corporation;Microsoft SqlServer v9; (C) 2005 Microsoft Corporation; All Rights Reserved; http://www.microsoft.com/sql/support;4"> <properties> <property'>http://www.microsoft.com/sql/support;4">http://www.microsoft.com/sql/support;4"> <properties> <property id="139" name="CommandTimeout" dataType="System.Int32" state="default" isArray="false" description="The number of seconds before a command times out. A value of 0 indicates an infinite time-out." typeConverter="" UITypeEditor="" containsID="false" expressionType="None">0</property> <property id="140" name="OpenRowset" dataType="System.String" state="default" isArray="false" description="Specifies the name of the database object used to open a rowset." typeConverter="" UITypeEditor="" containsID="false" expressionType="None">"ORASCHEMA"."DIMTABLE"</property> <!-- More Properies --> </component>
Ideally, I'd like configuration time control over the name attribute of the component element (highlighted) so that I can set the value of the property element with the OpenRowset attribute type (also highlighted). This way, presumambly as long as datatypes were generic enough, the mapping would just work.
But, in walking through the dtsConfig tree, I don't see these elements or attributes exposed.
I would sincerely appreciate any suggestions on how to accomplish this.
I am having problems exporting data into a flat file using specific code page. My application has a variable "User::CodePage" that stores code page value (936, 950, 1252, etc) based on the data source. This variable is assigned to the CodePage property of desitnation file connection using Property expression.
But, when I execute the package, the CodePage property of the Destination file connection defaults to the initial value that was set for "User:CodePage" variable in design mode. I checked the value within the variable during runtime and it changes correctly for each data source. But, the property of the destinatin file connection doesn't change and results in an error.
[Flat File Destination [473]] Error: Data conversion failed. The data conversion for column "Column01" returned status value 4 and status text "Text was truncated or one or more characters had no match in the target code page.".
[DTS.Pipeline] Error: The ProcessInput method on component "Flat File Destination" (473) failed with error code 0xC02020A0. The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running.
If I manually update the variable with correct code page and re-run the ETL, everything works fine. Just that it doesn't work during run-time mode.
I developed a simple custom control flow component which has several read/write properties and one readonly property (lets call it ROP) whichs Get method simple returns the value of a private variable (VAR as string). In the Execute method the VAR has a value assigened. When I put the value of ROP or VAR into MsgBox I can see the correct value. However when I execute the component I can not see the value of the ROP in the property window. I see the property but its value is empty string. For example when I put a breakpoint to postexecute or check the property before click OK in a MsgBox I would expect that the property value would be updated in SSIS as well. Is there a way how to display correct values of custom tasks properties in property window?
Untill recently I had a smooth running SSIS package,but suddenly it throws error syaing "OnError,,,,,,,The result of the expression
"@[User:trTextFileImpDirectory] +"SomeTextStringHere"+ @[User:trANTTextFileName] +(DT_STR,30,1252) @[User:taging_Date_Key]+ "SomeTextStringHere" " on property "ConnectionString" cannot be written to the property. The expression was evaluated, but cannot be set on the property."
I have child SSIS package running under a parent package (through execute package task)
I have few flat file connection managers in child package for text file import , in which I am building text file path dynamically at run time by assigning an expression in connection string property of connection manager. The Expression is as follows
Where @[User:trTextFileImpDirectory] is a variable which contains path of directory containg text files.Value in this variable is assigned at runtime from parent package's variable,which in turns fetch value from a configuration file on local server.
With my current configuration this path has been configured to some other server's directory over network ( I.e my package picks text files from some other servers folder over network)
While "Some string here"+ @[User:trANTTextFileName]" part of file name string.
(DT_STR,30,1252) @[User:taging_Date_Key] Contain the date of processing ,value in this variable is also picked up at run time from parent package variable.
1) So can someone give me some insight into possible reason of failures. 2) Is it possible that problem arises if directory (from which I m picking text files) is assigned password or is there exist some problem in accessing forlders over network ? 3) Or there can be some problem in package configuration at design time( I.e where I m assigning value in variable from parent package vriables)?
Hi, I'm developing an application that will access a database, and then send the data to a server either in batch or as each item is updated over GPRS. The database will have a large table, with 20,000 records. Each record is about 150 characters. The data access needs to be as fast as possible. I'm not sure which platform/hardware to use to achieve maximum speed. I have experience with c#, sql server ce. Worked mostly on Windows Mobile 2003, but thinking of moving to WM 5 or 6. My question is what is the best combination of hardware, OS, development environment, and software to use?
I need some feedback to bolster my position with a client who is planning a platform migration. They are currently running SQL 7.0 SP3 on Windows NT4 and want to upgrade to Windows 2003. First off, SQL 7.0 isn't going to run on Windows 2003, so their first response is "let's buy the licenses and run Win2000 and SQL7 until we're ready to migrate to SQL2000". Ok... licensing cost controls aside, they're investing significant $$ in acquiring the hardware. What's my most compelling argument for moving them to a Win2003/SQL2000 platform now. (Other than the wait for Yukon is likely to be significant ;-) )
Hi,I'm planning to purchase Sql Server2000 St. Edt. and install it onwindows 2000 server machine. I would like to know please if it isadvisable to work on the same machine that host both servers or shouldI work on a separate one???MTIA,Grawsha
I'd like to integrate SQL CE 3.5 into a platform builder image(using PB 5 targeting CE 5), but I don't see it in the catalog. Is it currently possible to Sysgen an image with 3.5? Can I somehow deploy the files from the .cab files? Sorry if this has been answered before, I searched around a bit but didn't find anything.
hello... my SQL database is being not able to be accessed by application when i run through VS2005 . I created the database in XP sys now brought to a NT systeem..what shd i do ..??? pls help
When I try to run the x86 version of SP1 on my development desktop (for tools only), I get an 'Incorrect Platform' error: Setup cannot update x86 products on this computer To proceed, run the Service Pack Setup program for the x86 platform.
The filename I downloaded is SQLServer2005SP1-KB913090-x86-ENU.exe
and it successfully installed on my Wk2003 server (dual PIII). My desktop is a single P4 2.8Ghz running WinXP Pro.
Our company needs to (restore/migrate) our Alpha Nt4sp4 sql 6.5sp5a databases to an Intel hardware platform. For the time being the new intel server will be runing Nt4sp4 sql 6.5 sp5a. I understand that if we were to upgrade to sql 7 we would be able to restore the databases without any problems. However upgrading to sql 7 is not an option right now. I have tried to restore a backup from the alpha to an intel based machine, and it fails because the processor types are different.
I have already search technet, but found nothing, except upgrade to sql 7.
I am hoping someone out there could point me in the right direction.
Thank inadvance for your help, I appreciate it very much.
For the last couple of days i've been trying to transfer a SQL6.5 database from an Alpha platform to an Intel one.
At one point i loaded SQL7 on the Intel platform and tried to perform an upgrade (using the wizard), across the network - but it just did not want to play.
Using Veritas Backup Exec, with SQL6.5 on both machines, i've tried doing a backup of the database on the Alpha platform and then restore to the Intel Platform, but this fails stating that the processors are incompatible
Am i trying something that is impossible?
If anyone could point me in the right direction i'd be truely grateful.
Does anyone know why the Extended Stored Procedure API (formerly Open Data Services) headers and libraries (e.g. srv.h, srvdbtyp.h, opends60.lib) are not in the new Platform SDK? Older versions of the Platform SDK had these tools included, but I installed the new Platform SDK and they're not included. Is there another SDK that I need to download and install now?
I have to move our dedicated Sql 2000 transactional distributor to a new and faster machine. Great! Can someone give me or point me to a cookbook of the best way to do this? This has to be done quickly so I would like to script it and have it ready ahead of time. I am not a replication guru so I am a bit nervous . . . I have looked at the scripts output by EM, but I am sure there are some assumptions . .
My client has just moved their SQL boxes to a 64bit platform and this process no longer runs.
Now im also running some packages in a SQL Agent job on the SQL box and im aware of the issue of an SSIS job step defaulting to using the 64bit version of DTExec.exe. Ive updated those job steps to be operating system (cmdExec) type steps calling the 32bit version of DTExec.exe, and everything is fine there.
Is there anyway to force the Microsoft.SqlServer.Dts.Runtime.Package object in my C# code to use the 32bit version of DTEexec.exe? This code is running on the same 64bit SQL server box as the SQL agent job. Or will Microsoft.SqlServer.Dts.Runtime.Package object always default to using the 64 bit version if it is executed on a 64bit box ?
I would just call sp_start_job from C# and implement the IS packages in another job but unfortunatly my code cannot be given correct permissions to see the SQL agent jobs.
I need to connect to Express edition of sql server installed on my machine, from perl (solaris platform). How should the connection string containing server, port, database etc look like ??
How do i call an application, which is reside in another unix platform in my flow of execution. I'll need to call this application after my data extraction is successfully run.
While SQL Server installed into our clustered environment with no significant problems Service Pack 2 will not install with the Error "Unable to install Windows Installer MSP file" during the update to the Database Services.
Subsequently, Integration Services, Native Client and Backwards Compatibilty also fail to upgrade due to suspended installs.
Searching for this returns a number of articles none of which match what we are seeing, including:-
http://support.microsoft.com/kb/918357 indicates this is a problem with the Setup Support Files. This is not the case and the Setup Support files are updated. Also the permissions are correct on the folder and files mentioned,
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=448685&SiteID=1 also point to a problem when installing the Setup Support Files. Our install gets past this but fails on the database engine then sets up a chain of suspended installs.
Other finds indicate there may be another msi running, again this is not the case and the server has been failed over and rebooted a number of times.
At the moment we are sitting at RTM having rebuilt the machine completely but would like to move forward onto SP2. Has anyone come across this and provide any further information or resolution?
We have successfully deployed SP2 onto a number of other servers cover both clustered and non clustered, 32 bit and X64 installations with no problems and now wondering if the problem is Itanium edition specific.
extract from the install log from the failed install. The logs mentioned in this log do not exist post install, in fact the Hotfix folder is not there.
Prerequisites Check & Status SQLSupport: Passed ********************************************************************************** Products Detected Language Level Patch Level Platform Edition Setup Support Files ENU 9.00.1399.06 IA64 Database Services (MSSQLSERVER) ENU RTM 2005.090.1399.00 IA64 ENTERPRISE Integration Services ENU RTM 9.00.1399.00 IA64 ENTERPRISE SQL Server Native Client ENU 9.00.1399.06 IA64 Client Components ENU RTM 9.00.1399.06 IA64 ENTERPRISE MSXML 6.0 Parser ENU 6.00.3883.8 IA64 SQLXML4 ENU 9.00.1399.06 IA64 Backward Compatibility ENU 8.05.1054 IA64 Microsoft SQL Server VSS Writer ENU 9.00.1399.06 IA64 ********************************************************************************** Products Disqualified & Reason Product Reason ********************************************************************************** Processes Locking Files Process Name Feature Type User Name PID ********************************************************************************** Product Installation Status Product : Setup Support Files Product Version (Previous): 1399 Product Version (Final) : 3042 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_SqlSupport.msi.log Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : Database Services (MSSQLSERVER) Product Version (Previous): 1399 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log Error Number : 1601 Error Description : Unable to install Windows Installer MSP file ---------------------------------------------------------------------------------- Product : Integration Services Product Version (Previous): 1399 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixDTS9_Hotfix_KB921896_sqlrun_dts.msp.log Error Number : 1601 Error Description : MSP Error: 1704 An installation for Microsoft SQL Server 2005 (64-bit) is currently suspended. You must undo the changes made by that installation to continue. Do you want to undo those changes?
I have a query of the kind brains of this group.Is it possible to access a microsoft sqlserver database (for select, insert,update, delete, and for miscellaneous administrative actions such as tableand index creation and deletion) remotely from a compiled C program (and/or,from Perl) running on a NON microsoft platform, such as Sun's Solaris and/orLinux?What toolset(s) could be used (on the UNIX/Linux end) for such a purpose?Would it require a corresponding special toolset to be installed on theWindows server end as well? (I'd prefer not to have to do that ifpossible.)If you are not now rolling on the floor laughing at the "heresy" of such anotion, thanks in advance.DanJoin Bytes! (replace 'glowing' with 'lucent')
Hi all,We're looking at a vendor who uses the InterSystems Cache DatabasePlatform, but our IT department has zero experience with this system.This software package will have a pivotal and mission critical roll inour organization, so I'd like some comments on what others think ofthis database platform.Mainly I'm curious how easy/difficult it is to query a Cache Database,and does it use standard SQL calls like Oracle and MS SQL? What aboutODBC connections into the database from Crystal, MS Access, and OLAPtools? Any other caviets (backup, maintenance, etc)?Thanks in advance for any suggestions or comments Cache.Sam
We have build configuration setup for each environment that we automatically deploy to (DEV, UA, PROD 1, PROD 2, etc.) Â We've recently come across a scenario where one environment will now be running a different version of SQL Server than the others.
Is it possible to tie the Target Platform version to a configuration. Such that one configuration could target 2012 while another targets 2014?