I've seen a lot of stuff regarding 64 bit and Jet drivers. Apparently the only way to overcome this situation is using the command line 32 version of DTEXEC found in C:Program Files (x86)Microsoft SQL Server90DTSBinn. Is that trick what SSIS is using under the cover when it successfully executes my export package? Or is there a mean of building the managed application so it uses the traditional 32 bit libraries of Jet/Access?
I (obviously) prefer using managed code approach when loading and executing SSIS from my end user application. Any suggestion would appreciated.
We have a BI-Stack configuration for server SQL 2012 that includes a gateway server that houses the app, a second server which houses SQL Server DB and SSIS, and a third server that houses SSAS and SSRS. Where should SSDT tools be installed? I assume on the gateway? This is a production environment, so should VS and/or SSDT not be here at all?
I am attempting to write a Windows service that watches a database for uploaded files to import. When a new file is found, the corresponding SSIS package is run from the file system with variables passed through. I started development as a Windows app and copied the functionality to a service.
The app runs fine. The service does not. I get a "Failure" each time a package is executed. Everything is identical behind the scenes with the obvious exceptions that OnStart and OnStop handlers are buttons in the app. I added a script task at the beginning of one of the SSIS packages to notify me that it is even running at all. It doesn't even hit that initial task.
Again, the app will run all packages just fine. The data is imported and the results return as "Success."
The following is the code executing the package. Any help is appreciated. I've been banging my head on this one for a few days now. (Is there a tag to format a code sample?)
Dim pkgLocation As String Dim pkg As New Package Dim app As New Application Dim pkgResults As DTSExecResult
Have two C# applications - one WinForms desktop app, the other a WinForms smart device app. Both use SQL Server Compact CE 3.5 to store data locally. Both work just fine.
Now the desktop app needs to open and update the .SDF file that is stored on the Windows Mobile device. (Device will be docked via USB.)
What format would the path to the .SDF look like that the WinForms application would need to specify in order to open it?
I just upgraded from Windows XP Pro to Windows Vista Bussiness and tried to reinstall SQL Server 2005 Developers Edition. After the installation i downloaded (using microsoft windows update) and installed all the service packs for sql and vista available.
My problem is when i open sql server management studio and try to connect to my default instance using windows authentication and database engine, an 18456 error occurs.
I enabled all the protocols and all the ports I disabled windows firewall and antivirus (eset nod32) I installed all service packs available I have also installed Visual Studio 2005 without installing sqlexpress
But nothing happens!
Please i am very desperate, any information will be gratefully accepted.
This is my installation Information
Code Snippet
Microsoft SQL Server Management Studio 9.00.3042.00 Microsoft Analysis Services Client Tools 2005.090.3042.00 Microsoft Data Access Components (MDAC) 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft MSXML 3.0 5.0 6.0 Microsoft Internet Explorer 7.0.6001.18000 Microsoft .NET Framework 2.0.50727.1434 Operating System 6.0.6001
Hi all,I have a Windows 2003 server, which is also a terminal server forapplication, with sql 2000 installed. My company has developed anapplication that uses SQL 2000 as its database. The application is aclient/server one. In each client computer there's a link to theapplication on the server. There is no problem with Windows 98,Windows 2000 pro, Windows xp pro clients, but the windows 95 onescannot log in to the database. The log of the application shows thefollowing error:connection error -2147467259. Cannot open database requested in login'database name'. Login fails.Till a week ago the application was running on a Windows 2000 serverwith SQL 2000 install and the W95 clients had no problem connecting tothe database, so my guess is the error has something to do withWindows 2003 server, but what'causing the error?I tried to install a newer version of MDAC (MDAC 2.5, the last versionof MDAC you can install on W95)but with no success. By the way W95clients have no problem accessing shared folder on the Windows 2003server.Any idea?ThanksMarino
We just moved the back end of an Access db to an SQL server and upgraded to Access 2000. A strange problem has arisen. The execution of a query in a certain function seems to be causing the function to prematurely terminate (that is, the query does not complete, and the function does not execute beyond the execution of the query). This error occurs only on workstations loaded with Windows 98. Windows 2000 users are unaffected, and the function runs uninterrupted. The query in question contains date parameters. On the SQL server, dates are enclosed in single quotes (')'s, whereas in Access they are enclosed in pound signs (#)'s. When a query is sent by Access to the SQL server, it is filtered through a program that converts the Access format to SQL-friendly code. Our theory is that this process fails to occur on the machines running Windows 98. Does anyone know why this is occuring?
We have an installation of MS SQL Server (MSDE actually) runnning on a group of Windows 2k machines. Due to IT constraints at the customer site, we are using Windows authentication, but it is all done with local user accounts, not domain accounts.
We have the same user account witht he same password locally created on each machine. This works fine with all the Win2K machines (not the best solution, but under the client's insane IT department, it's all we were allowed to do).
The problem is that we tried to add an XP machine. While we can connect to a DB running on a 2K machine from the XP workstation, the XP system will not accept connections from the 2K systems. We have done a little research and think we have found out why- the 2K systems are sending usernames for authentication, but the XP is looking for the UID- which is different on every system.
We cannot go to SQL authentication, and we cannot use Domain authentication. Is there a way to change XP to authenticate from username instead of UID?
I have been trying to install MS SQL Enterprise V7 on Windows ME the first time it worked but then it stopped with a Connection error message, ever since then I have tried and tried to install it properly but it keeps giving the same connection error.I've successfully installed it on NT and 2000 adv server, so what gives I'm I barking up the wrong tree will MS SQL not install on ME?Or I'm I missing something
My SQLExpress seems to be set for windows authentication and not sql server authentication ... I am not quite sure why it is set to windows authentication - I installed this with Visual Studio 2005 and it just seemed to be set that way.Am I able to change this - if I choose sql authentication when connecting I get an errorIf someone could answer this point I would be most grateful !!Patrick
My machine is running Windows 98. I want to install window 2000 in order to enable me work with SQL Server 2000. Please what is the best way to go about it. Do I use an Upgrade or do I uninstall Windows 98 and install Windows 2000. Thanks for your help!!!!!
Does anyone know how SQL Server works with Active Directory users? Specifically, I'm wondering if I'm going to encounter problems if our Windows 2000 environment is setup with multiple forests. I'm assuming as long as there's a trust between the forests, SQL Server will be able to authenticate.
Need to install SQL 7 under windows 2000 (professional version), thought it should be. However, in the install (Standard) process, first msgbox "You could only have client utility". Hit 'OK' to ignore this message, and the whole installation finished completely.
Issue: could not register the server name of 'SQA-Test1' nor connect through the isql/w. Thus, not quite sure the relationship between SQL 7 and Win2000.
In an effort to eliminate the need to code accounts and passwords into the VB Com calling stored procedures, I would like to use Windows Authentication. I have setup the account that the com is running under to have access to the database. How does this change my connection string. Do I just drop the account and password parameters or do I need to let it know somehow that I want to use Windows Authentication?
When am accessing some folder ( with full permission) in different domain after configuring the trust relationship in User domain mangaer I get some error
mavhinename foldername not accessible The credentials supplied Conflict with an existing set of Credentials.
I try to install SQL Server 2000 SP3 on my Windows XP server.
During the installation, the setup process inform me database services can't be install on my machine. I can only install client tools.
It seems to success, but when I try to connect register a new database in the Enterprise Manager tool, connection to my server databases always fail with error: "waiting time expire"
If I try to connect to the same database with the Querty Analyzer it works.
How can I solve this problem ? His there a patch ?
Hi all, I'm about to install SQL 2000 SP4 on a Windows cluster and I was wondering if there is anything to look for in particular. I went through the readme.txt and microsoft has one aticle but I was hoping to find out a little more.
I'm having problems with windows authentication. I'm new to using using Microsoft SQL Server. I just migrated from powerbuilder 8 to powerbuilder 10. I'm using OLE DB and can't get the windows authentication to work within the application. Can anyone help....
