hi
I need to load a text file into sql server table using SSIS package.
the idea is to load this file with the help of dtexec command by giving the file path and name in the SET switch of dtexec command.
anyone having an idea; would be of great help.
Regards,
Salman Shehbaz.
Our application installation setup needs to be able to detect:
Is SQL Server 2005 Express Installed?
If false, run the SP2 Installation
Is SQL Server 2005 Express or SQL Express SP1 Installed?
If false, run the SP2 Installation with Update Switch
Is SQL Server 2005 (not Express) Installed
If true, abort installation with a mesage.
Can you direct me to some documentation about testing for these environments or just if someone has some scripts that will run in InstallShield, that would be great.
ALSO, can you direct me to information about using the command line update switch for the Express SP2 Installer?
Thanks.
Pat
I know that connecttimeout and commandtimeout are separate entities. Is it possible to change the default command timeout value by changing the connection string?
I need to increase the command timeout and want to know if I can do it without changing my code and rebuilding my ASP.NET 1.1 web app.
Thanks in advance. -- ZLA
Hey
I need to know what shall i specify in this connection string in visual studio web.confug file inorder to connect to ma registered server (locally) not directly to my dedicated server ....cuz i am facing network connection problems ....
b4 i used to use this connection string :
<add key="conn" value="data source=IP addresseel,1433;initial catalog=xxx;user id=username on the dedicated server;Password=password on the dedicated server;timeout=60"></add>
So how can i change it ???? to be able to connect locally ????
Please Help ???!
Thanks in advance
Hiba
Hi All,
I created a SSIS package to import an excel spreadsheet into my data warehouse.
When I run the package it runs fine. When I created a SQL Job to run the package I get the following error:
Option "Source=D:HelpDeskImportBook2.xls;Extended" is not valid. The command line parameters are invalid.
Now if I look at my source connection string in the job it looks like the following:
Provider=Microsoft.Jet.OLEDB.4.0;Data Source=D:HelpDeskImportBook2.xls;Extended Properties=HDR=YES;EXCEL 8.0;HDR=YES";
Does anyone know why it appears that my connection string looks like it is being cut off and does anyone know how I can correct the problem?
Thanks,
Scott
<connectionStrings>
<add name="AppConnectionString1" connectionString="Data Source=".SQLEXPRESS";AttachDbFilename="C:Program FilesMicrosoft SQL ServerMSSQLDataAdventureWorks2000_Data.mdf";Integrated Security=True"
providerName="System.Data.SqlClient" />
</connectionStrings>
I'm running Microsoft SQL server 2005. what is the error in the above code.
Hi,
I have just uninstalled SQLEXPRESS and installed the 180 day trial SQL server 2005 enterprise edition.
I have since started to have problems with my ASP.Net Configuration Tool., can not connect to the database.
I think that the connection string in my machine.config file is incorrect, before installing I had,..:
datasource=./SQLEXPRESS,....
So i decided to change that part to the following. Would anybody know what I have put in the datasource part for the SQL server 2005 enterprise edition? At the moment I tried SQLSERVER2005 but that is incorrect,..
<add name="LocalSqlServer" connectionString="data source=./SQLSERVER2005;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|aspnetdb.mdf;User Instance=true" providerName="System.Data.SqlClient" />
does anyone kbnow the connection string used to connect to the database in sql server 2005 express?
can someone one give me sample codes for it? thanks.
thanks
What is the impact of the differences in the following 2 connection strings:
Initial Catalog=xxx;Data Source=xxxxxx;Trusted_Connection=True;
Driver={SQL Server};Server=xxxxx;database=xxx;Trusted_Connection=yes;
To outline the differences I'm concerned with are
Missing Driver on first string
Difference in Trusted_Connection parameter (true vs. yes)
Initial Catalog vs. database parameter
Hi, all. I am using VS.NET 2005 and SQL Server 2005 Express. I tried to use the following code to connect to a database named "AMSPROD" that I attached to SQL Server 2005 Express:
dbConn = new OleDbConnection(Data Source=.SQLEXPRESS;AttachDbFilename="C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDataAMSPROD_Data.MDF";Integrated Security=True;Connect Timeout=30;User Instance=True);
dbConn.Open();
I got an error asking for provider with the above connection string, then I changed the conncection string to be like follows:
Data Source=.SQLEXPRESS;AttachDbFilename="C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDataAMSPROD_Data.MDF";Provider=SQLNCLI;Integrated Security=True;Connect Timeout=30;User Instance=True
I got error: No error message available, result code: DB_E_ERRORSOCCURRED(0x80040E21)
Then I changed the Provider to be like: Provider=SQLOLEDB, now I am getting the following error:
Message: "Invalid authorization specification
Invalid connection string attribute"
Source: "Microsoft SQL Native Client"
StackTrace: " at System.Data.OleDb.OleDbConnectionInternal..ctor(OleDbConnectionString constr, OleDbConnection connection)
at System.Data.OleDb.OleDbConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.OleDb.OleDbConnection.Open()
at ISESAMSData.DbConnections.MakeConnection() in C:\ISES\ISESCommon\ISESAMSData\DbConnections.cs:line 74"
TargetSite: {Void .ctor(System.Data.OleDb.OleDbConnectionString, System.Data.OleDb.OleDbConnection)}
Strange thing is, when I use the Connect To Database under Tool menu of VS.NET 2005, I could make the connection to this database. Then I copied this connection string to the code, the connection couln't be made. I feel very confused.
I am wondering if I need to add ASP.NET user to SQLExpress. But I don't know how to do it?
Can anyone please help me out! Many thanks!
Junifer writes "Hello guys,
Can you give me a simple example of a dns-less connection to SQL Server 2005 Express Edition?
Thanks."
I migrated my SQL Server 7 database to the new SQL Server 2005 that I installed on my PC. I have classic ASP programs on my PC that used to access the SQL Server 7 database. However, global.asa and these ASP programs can no longer connect to the new SS 2005 database.
View 9 Replies View RelatedI'm a student at Boise State university and we're using SQL Express as part of one of our projects for ASP.NET programming. I liked it and I'm trying to use it to power a wiki that I'll be hosting from my home internet connection. The wiki is compatible with MSSQL server, but it won't connect to SQL Express.
I suspect that the problem is in the connection string, mainly because the apps we're developing for class use a connection string like:
<add name="AspNetForumConnectionString" connectionString="Data Source=localhostsqlexpress;Initial Catalog=gaming.forum.nxnw;User ID=*********;Password=*********;" providerName="System.Data.SqlClient"/>
and note the Data Source. The wiki I'm using is PHP based and uses ADObd to connect databases and has a driver for MSSQL, but not SQL Express (no surprise, really). I know just enough php to be dangerous to code and I've tried modifying the adodb-mssql.inc.php, but I can't seem to make the right change.
So, all that said, my question is: Is there a way to change what SQL Express 2005 will accept as a connection string? I've been looking, but I'm not even sure what the setting would be called.
Thanks,
Les
Hi everyone!
I am new to visual studio 2005 and sql server 2005.
Up to now i was using visual studio 2003 and ms access.
When i wanted to create a web application that communicates with
an access database, i just had to take the *.mdb file and put it
into a specific folder inside my application's folder and then use
Server.MapPath on the connection string (so it can run on any pc).
Now, i want to do the same with sql server 2005 and visual studio 2005.
I use the connection string: "Server=MYSERVER;Initial
Catalog=test_db;Integrated Security=SSPI".
My problems are:
1) Can i just take the *.mdf file put it inside the App_Data folder like i did on access?
2) What should be the connection string so that my application can run on any pc (with sql server 2005)?
Thanx in advance guys!
Do I need to change connection string if I upgrage SQL server from 2000 to 2005 in ASP.NET 2.0?
View 1 Replies View Related
I'M HAVING AN ISSUE, UNDERSTANDING, THE CONNECTION STRING.
I WANT TO CONNECT TO AN INSTANCE OF SQLEXPRESS ON A REMOTE SERVER WITH A FIXED IP ADDRESS
THE TCP PORT IS OPEN TO 1433
I OPENED THE PORT ON THE ROUTER AND THE WINDOWS 2003 FIREWALL
MY CODE IS AS FOLLOWS:
S = "Provider=SQLNCLI;"
S = S & "DATA SOURCE=44.66.777.888,1433SQLEXPRESS;"
S = S & "INITIAL CATALOG=TESTDB;"
S = S & "Persist Security Info=false;"
S = S & "UID=TEST999;"
S = S & "Pwd="TEST999888;"
CnMgt.ConnectionString = S
CnMgt.Open S
I'VE FOLLOWED THE STEPS OUTLINED IN ARTICLE 914277
CAN SOMEONE HELP?
THANK YOU
PS. IF THE CLIENT IS LOCAL, I HAVE NO ISSUE OPENING THE DATABASE.
I DO NEED TO OPEN THE DB FROM FROM CLIENTS.
Hi,
I need to run a package wich is located on the file system of a PC. The problem is that the PC from where I'm running a bat file to call the package from the other PC where the package is, doesn't have SSIS.
So I was wondering if this will work. I believe that I will have to copy the DTExec.exe file to the PC where my bat file calls to the dtsx in the other PC. I am right?
My run.bat will have this line: \PCshared_folderpackage.dtsx.
Will this work?
Thanks
Does anyone know if DTEXEC runs in its own command shell area? The reason I am asking this question is that we have hundreds of old DTS packages that fetch data from Source Progress double-byte and standard databases. When we fetch from a double-byte Progress database, the first thing we do is to set System Environment variables and within the same command prompt session invoke DTS packages via DTSRUN utility. THis method works like a charm using the old DTS packages. We are trying to accomplish the same thing using SSIS and are unable to do so. The SSIS package works fine while fetching data from a non Double Byte Progress database but fails miserably while using a Double Byte Progress database. Has anyone experienced something like this? Any solution for this problem?
Thanks
Jagannathan Santhanam
Hi
It is possible to use switch statement in stored procedure.
if yes then please tell me a sample example.
We have a project already developed iusing VS 2003 Enterprise architect edition using sql server 2000(have lots of table and stored procs etc.)
Now planning to switch to Sql server 2005 are there any issues associated with the switch.
I mean front end programming wise asp.net and vb.net front end codes do they work straight away or need to make any changes to all the front end codes, we are using datasets, data readers calling stored procs and also using lot of hash tables and XML object to make bulk loads to sql server via sqlxml3.0 sp3.
Please help thank you very much for the information.
We have schedule process server, calling SSIS package via command line (see below) to physical SSIS server. Get message "insufficient for component" and package call bombs.
Facts:
1. schedule process server has Workstation tools / Clients / Connectivity for SSIS loaded
2. SSIS is 2005, SP1
What are we missing?
c:>dtexec /DTS "File SystemSalesDWgyp_dm_carrier" /SERVER BPATLQDDW /CONFIGFILE "\bpatlqddwd$SSISSalesDWgypdm.dtsconfig" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING V
Error: 2006-11-09 10:43:34.94
Code: 0xC00470FE
Source: DTF - Xfer DW to DM DIM_CARRIER DTS.Pipeline
Description: The product level is insufficient for component "Slowly Changing Dimension" (289).
End Error
Error: 2006-11-09 10:43:34.94
Code: 0xC00470FE
Source: DTF - Xfer DW to DM DIM_CARRIER DTS.Pipeline
Description: The product level is insufficient for component "OLE DB Command" (775).
End Error
Warning: 2006-11-09 10:43:34.94
Code: 0x80019002
Source: gyp_dm_carrier
Description: The Execution method succeeded, but the number of errors raised (2) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
End Warning
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 10:43:32 AM
Finished: 10:43:34 AM
Elapsed: 2.383 seconds
Hi All,
In one of my SSIS package (which connect to DB2) i save the DB2 username and password in SSIS packge itself by using option "EncryptAllWithPassword".
When I try to run the packge using dtexecui.exe it works perfectly fine. It prompts me for package password and then run fine.
Now I am trying to run it using command line dtxece.exe and i get fooolwoing error. Please suggest and help!!!
DTExec.exe /FILE C:pkgDB2Load.dtsx /CONFIGFILE C:ConfigpkgConfigMaster.dtsConfig /Decrypt mypassword /CHECKPOINTING OFF /REPORTING EWCDI
Error Message:
----------------------
Description: An OLE DB error has occurred. Error code: 0x80040E21.
An OLE DB record is available. Source: "IBM OLE DB Provider for DB2 Servers" Hresult: 0x80040E21 Description: " SQL30082N Attempt to establish connection fa
iled with security reason "17" ("UNSUPPORTED FUNCTION"). SQLSTATE=08001
"
Thanks
Sid
The box I am trying to connect to is running two instances of SQL Server.
There is a SQL Server 2005 instance which is the default. There is a SQL Server 2000 instance which is named 'SQLSERVER'.
I can connect to the SQL Server 2000 instance no problem:<add key="ConnectionString" value="server=MYPCSQLSERVER;database=mydatabase;user id=****;password=****" />
However, I am having trouble connecting to the Default SQL Server 2005 instance. I have tried:
<add key="ConnectionString" value="server=MYPC;database=mydatabase;user id=****;password=****" />
but it doesn't work. I have tried explicitly setting SQL Server 2005 to use port 1434 (as SQL Server 2000 is running on port 1433), and then used:
<add key="ConnectionString" value="server=MYPC,1434;database=mydatabase;user id=****;password=****" />
but this doesn't work either.
Am I mssing something here? Any help much appreciated
Thanks...
1) We are migrating data from SQL Server 2000 to 2005 DB.
2) We are developing SSIS packages in client, build, deploy and install and copying to SQL Server 2005 server to execute for migration.
3) For this we encrypt all packages with password, then decrypt all while executing in a batch file using dtexec. This works fine.
4) What does not work is executing a master execute task in which are individual execute tasks. This is so since the other packages are still encrypted.
5) We decrypted them separately first using dtutil using Decrypt and Copy/Move option but while executing error is thrown that these other packages are still protected by password.
6) Do we need to decrypt, then encrypt using default package protection level and then decrypt again.
7) How exactly to just execute a master package when packages are developed on client.
I believe I have made a complete install of Sql Server 2005 on my dev. machine, including all client tools, and can run SSIS packages from the dev. environment.
However DtExec refuses to run any package and always throws the "insufficient version" error (as does the "RunPackage" component, probably for the same reason).
I have repeatedly attempted to find something more to install from the Sql Server 2005 eval release that will allow DTExec to run without the "insufficient version" error, but can find nothing else to install from the eval. The install wizard (and the "change" wizard) indicates everything is installed and will not build a list of any additional components to install.
Are we sure that DtExec will install and run from a sql server 2005 eval distribution?
Licenses are in the pipeline (not that pipleine) but we need to start testing our SSIS solution in the meantime.
p.s. Kudos to the dev. team, it really is an excellent tool!
Thanks,
Ken
Dear,
I am trying to connect from a vb.net application (VS 2005) to a sql server 2005 database located remotely,what is the connection string that I should use?I used the same one that I was using for connecting to sql 2000 but it is not working.Thanks.
anybody here who can tell me of what is the syntax or sample connection string to SQL 2005 server from MSAccess 2000,
Thanks
Ben
I have a windows forms application that runs on my PC that populates a SQL Server Compact 2005 database and then transfers that .sdf file to my mobile device. The communication between the mobile device and PC is done using the Desktop RAPI class from OpenNetCF (http://www.opennetcf.com/FreeSoftware/DesktopCommunication/tabid/90/Default.aspx)
Anyway, I was previously using SQL Server Mobile 2005 and my populated .sdf was around 1.7 MB and I could transfer it to my mobile device in a minute. Once I switched to SQL Server Compact 2005, the transfer process began taking 3 minutes with a 1.5 MB .sdf file. The SSCE also got bloated more easily so I added in the Compact operation each time after I fully populate the SDF to keep the file size at 1.5 MB, but even then it still takes 3 minutes.
I've done a few tests where I simply switch between the two database versions and that simple switch of the version changes the transfer time. I am dumbfounded trying to figure out what the cause might be. Since it is just a file transfer, why would the version even matter unless somehow SSCE is really not compacting and lying about its actual size.
Has anyone run into anything similar to this or may have any ideas what might be going on?
Thanks.
I have SQL 2005 and I wanted to write a little program in Visual Basic 2005 Express Edition (VBEE) to carry out some processes. While away I built my user form, but when I got back I found that VBEE refuses to connect to SQL Server 2005 and is only configured to link to SQL Express.
The data source is set to .SQLEXPRESS in the advanced properties of the Add Connection form in the Data Source Configuration Wizard and you can not change it.
I read in MSDN ID 329721 that you can create a data layer that will allow you to use the wizards, but that is as far as it went and is above my programming skills.
So my only options are use VB.Net 2003 Standard edition, use connected mode or give up and it was only supposed to be a quick fix. Had anyone else had this same issue and developed a work around?
Hiya,
I'm a SQL n000b, and have just joined the forum 5 minutes ago seeking an answer to this problem that I've encountered. It seems that the way connection strings are handled in SQL 2005 have changed. This connection string used to work, but is now borked:
<add key="DBNAME.ConnectionString" value="packet size=4096;integrated security=SSPI;data source='sqlvirdev0035dev35';persist security info=False;initial catalog=DBNAME;connection timeout=60" />
Has something explicitly changed in SQL 2005 that would break this <add key>? Does something need to be set server side in order to handle these connection strings now? I have no idea why this won't work anymore, I just know that it doesn't work.
Ty for any help,
~Chipley
i am trying to connect to ssas 2005 -- i can get to it through management studio no problem. i cant seem to get my program to connect
can anyone see anything wrong with this connection string
Provider=MSOLAP;User ID=myid;Password=mypass;Data Source=mysrvr;Initial Catalog=mycat;Client Cache Size=25;Auto Synch Period=10000;
I try to use this conn string but it is not working I think the problem is with the provider
DataBaseSource = "Provider=SQLOLEDB; Password=sa2006; User ID=sa;Initial Catalog=coupon; Data Source=YAELSQLEXPRESS;"
I get error message
Microsoft OLE DB Provider for SQL Server (0x80004005)
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
do you know which provider can I use?
or maybe it is a sacurity problem
Yael
I have a child package where the ConnectionString property of a Connection Manager is set by a Parent Package Variable Configuration. I set up a script task that brings up a message box with the value of the ConnectionString property right before the dataflow task.
MessageBox.Show(Dts.Connections["CPU_*"].ConnectionString.ToString());When I run the parent package, the message box shows that the connection string is changing with every iteration, but in the dataflow it always draws the data from the same source.
The connection manager is an ADO.Net type, RetainSameConnection is set to False, and I've been researching this for days.
(Update 2/23/2015): To make this stranger, when I look at the diagnostic logs, they tell me that when the new connections are being opened they are using the new connection strings.