hi all,
i posted this somewhere else but i think here is the right group.
i have a dts that shld write to a text file located at a mapped drive. i read somewhere that sql job does not recognise mapped drive, so i use UNC path in form \128.1.1.1dtsfile, which dtsfile folder is the shared folder name. i opened the folder permission to everyone.
thats abt the remote server. the sql server i am running is on windows NT, logon using Administrator to local. my sql is SQL 2000. i register the server using sa username. the server agent is start up using System account.
now the problem is when i run the dts interactively/manually, it runs succesfully. but when i run it thru SQL job it says "Access denied". Or full error is like this,
DTSRun: Loading... DTSRun: Executing... DTSRun OnStart: DTSStep_DTSDataPumpTask_1 DTSRun OnError: DTSStep_DTSDataPumpTask_1, Error = -2147467259 (80004005) Error string: Error opening datafile: Access is denied. Error source: Microsoft Data Transformation Services Flat File Rowset Provider Help file: DTSFFile.hlp Help context: 0 Error Detail Records: Error: 5 (5); Provider Error: 5 (5) Error string: Error opening datafile: Access is denied. Error source: Microsoft Data Transformation Services Flat File Rowset Provider Help file: DTSFFile.hlp Help context: 0 DTSRun OnFinish: DTSStep_DTSDataPumpTask_1 DTSRun: Package execution complete. Process Exit Code 1. The step failed.
i really hope and appreciate if someone out there can help me out. thanks!
ps: pls let me know if more clues needed from my environment settings.
We are using SQL Server 2005 (9.0.3054 on Windows 2003 RC2 SP2 with clustering two instances. We are running an instance on both boxes. I have 2 linked servers to the same server on the first box (SQL1C) that use different SQL Logins to connect to the same box but to different databases. One uses the name of the server and one uses the name of the server with a 2 at the end of it. (servername and servername2). The second linked server was added recently and is used very frequently by the new application. The other thing is there is a server with the name servername2. They are SQL boxes but I am not sure what version or what they are running on. If it turns out to be important, I will ask.
Here's what is happening: When we fail over to the second box, up until recently, we had no problems. All linked servers worked well. But since we have added this new linked server, when we fail over, the linked server no longer works and we get an error like from the Cold Fusion application:
[Macromedia][SQLServer JDBC Driver][SQLServer]TCP Provider: An existing connection was forcibly closed by the remote host.
I got a similar error in EMS, but did not copy it to save it. Since this is a production server, I can't really just try things.
We checked to make sure all IPs from box1 and box2 are allowed access to the server and they are not using IP blocking for inside the university domain.
There are no errors in the SQL Logs. I checked the application logs and found no errors for the linked server. The only error I could find and I didn't think it was related but I will include it was this:
Closed event notification conversation endpoint with handle '{4F54167A-F3D0-DC11-97FE-000E0CB2D7CA}', due to the following error: '<?xml version="1.0"?><Error xmlns="http://schemas.microsoft.com/SQL/ServiceBroker/Error"><Code>-8470</Code><Description>Remote service has been dropped.</Description></Error>'.
Any ideas? One of our pplications goes down when the cluster fails over now. Help PLEASE!
Anyone live in seattle (meet on cap hill)? I have been stuck for weeks now and can't wait any longer wasting time - i will pay someone to set me up correctly quickly. I doubt this will be resolved online, but here goes... I need a datagrid to bring up simple database info (northwind) instead of showing the error 'login failed for mycomputeraspnet'. I am using windows authentication and my string is connectionstring = datasource=(local)\netsdk;initial catalog=Northwind;integrated security=sspi; persistent security=false;, I have seen online they say alter the authorization in the app virtual directory-- is that the C/inetpub/wwwroot or the web config of my project? I did so in the web config of my project, and also I added the impersonate=true to same already. I shared all the folders and made sure they are not read-only. I am flabbergasted. Paul XP pro 2004 sp 2 vis studio 2002 w updates C# Asp web app project
Hello I am receiving the dreaded mail error listed above. I can send out a test E-mail from Enterprise Manager to operators, but I cannot run this Transact query:
I've got a popular problem so i get a message that server acces denied! ..
But that what is different in my error.... When i use same setting same database and connection string (on MSDE server) there is no problem...
On SQL server i have got windwos authentication but i added all accounts as ASPNET and SA.... and when i try to connect by
RETTO - name of my server
server=RETTO;uid=sa;pwd=password;database=db1; or by Integrated Security=SSPIserver=RETTO;uid=RETTOASPNET;database=db1;
I CAN BROWSE RECORDS THERE ARE NO PROBLEMS WITH CONNECTION!!! but when i try to update or iinsert or delete something in database there becomame this error that access denied or server does not exist!!!
PLEASE HELP I'm FIGHTING WITH THAT FOR OVER 5 DAYS!!!
I MADE FOR MY ACCOUNTS (SA, ASPNET) ALL THINGS ALLOWED AS EXECUTING stored procedures.. OR ACCESING datatables with insert delete and update query WHERE IS THE PROBLEM!!!??
I'm having a strange problem with this but I know (and admit) that the problem is on my PC and nowhere else. My firewall was causing a problem because I was unable to PING the database server, switching this off gets a successful PING immediately. The most useful utility to date is running netstat -an in the command window. This illustrates all the connections that are live and ports that are being listed to. I can establish a connection both by running
TCP 81.105.102.47:1134 217.194.210.169:1433 ESTABLISHED
TCP 81.105.102.47:1135 217.194.210.169:1433 ESTABLISHED
TCP 127.0.0.1:1031 0.0.0.0:0 LISTENING
TCP 127.0.0.1:5354 0.0.0.0:0 LISTENING
TCP 127.0.0.1:51114 0.0.0.0:0 LISTENING
TCP 127.0.0.1:51201 0.0.0.0:0 LISTENING
TCP 127.0.0.1:51202 0.0.0.0:0 LISTENING
TCP 127.0.0.1:51203 0.0.0.0:0 LISTENING
TCP 127.0.0.1:51204 0.0.0.0:0 LISTENING
TCP 127.0.0.1:51206 0.0.0.0:0 LISTENING
UDP 0.0.0.0:445 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:1025 *:*
UDP 0.0.0.0:1030 *:*
UDP 0.0.0.0:3456 *:*
UDP 0.0.0.0:4500 *:*
UDP 81.105.102.47:123 *:*
UDP 81.105.102.47:1900 *:*
UDP 81.105.102.47:5353 *:*
UDP 127.0.0.1:123 *:*
UDP 127.0.0.1:1086 *:*
UDP 127.0.0.1:1900 *:*
Both these utilities show as establishing a connection in netstat so I am able to connect the database server every time, this worked throughout yesterday and has continued this morning.
The problem is when I attempt to use SQL Server Management Studio. When I attempt to connect to tcp:sql5.hostinguk.net, 1433 nothing shows in netstat at all. There is an option to encrypt the connection in the connection properties tab in management studio, when I enable this I do get an entry in netstat -an, see below:
Amost as if it's trying the different ports but you get this time_wait thing. The error message is more meaningful and hopefull because I get:
A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.) (.Net SqlClient Data Provider)
I would expect this as the DNS has not been advised to encrypt the conection.
This is much better than the : Login failed for user 'COX10289'. (.Net SqlClient Data Provider) that I get, irrespective of whether I enter a password or not.
This is on a XP machine trying to connect to the remote webhosting company via the internet.
I can ping the server
I have enabled shared memory and tcp/ip in protocols, named pipes and via are disabled
I do not have any aliases set up
No I do not force encryption
I wonder if you have any further suggestions to this problem?
I use the code below for updating data from a AS400 Liked server. I dont understend how the WHERE NOT EXISTS( sections work however usualy they do, in this case it does not andt I can't seem to find out why.
Does anyone see the error?
Thanks
--========================================= --Create a local temporary table that hold --all the data from the source table --=========================================
SELECT * INTO #TEMP FROM dbo.LINK_LTTSTOC
--========================================= --Remove table entries that are no longer --needed or that have to be updated --=========================================
DELETE FROM LTTSTOCK
WHERE NOT EXISTS( SELECT * FROM #TEMP
WHERE LTTSTOCK.WarehouseNo = LTWHLO
AND LTTSTOCK.Location = LTWHSL
AND LTTSTOCK.ItemNo = LTITNO
AND LTTSTOCK.NumberAvail = LTAVAL
)
--=========================================
--Insert data that is missing or that
--needed to be updated and was previously
--deleted
--=========================================
INSERT INTO dbo.LTTSTOCK(WarehouseNo,Location,ItemNo,NumberAvail,rowguid)
I've built SSIS package and made a job to execute it automatically but it always returns an error. The job returns OK but when we looked at the Log File viewer, it conatins this error log :
Key not valid for use in specified state
Failed to decrypt protected XML node "DTS Password" with error
What's wrong with the package ? Thanks in advance.
I wrote an application using Visual Studio 2005 beta 2 which uses a SQL Express .mdf file, included in the project, for the database. After installing Visual Studio 2005 RC and the SQL Express that comes with it (I followed all of the uninstall instructions first) I can no longer add a SQL Express database to any of my projects, nor can I open the SQL Express database in my original project. When I try either of these tasks, I get the "Failed to generate user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed." I read the thread which dealt with this error, and changed the connection string for the database file that had worked before to User Instance = false. The moment I click Test Connection or OK, I get the error: "An attempt to attach an auto-named database for file C:<path to project>EngSQL.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share." (<path to project> is actually a full path, I didn't want to type the whole thing out. :) ). A search for this error turns up a solution of setting User Instance = false, which puts me in a catch 22 position.
I have log shipping set up between 2 SQL 2000 SP1 Servers on Win 2000. The db is small 10 meg, and when the restore job on the backup server fails I am getting "sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed." as the message, the maint paln on the primary server show no error. Anyone seen this before? The restore has worked 3 out of 5 times
Many a times see the below error in SQL Error log.
Login failed for user 'NT AUTHORITYANONYMOUS LOGON'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: ]
Is this something to do here?
Note: If I run the below statement I know that the SQL Error log entry will go off, but wanted to know the real significance of this error?
CREATE LOGIN [NT AUTHORITYANONYMOUS LOGON] FROM WINDOWS
I am administering several SQL Servers running SQL Server 2005 SP2 Build 3042. I have a common maintenance plan that runs on each of the servers. The maintenance plan runs fine on all the servers except for one. On the one server the Database Integrity check fails with the following error:
Check Database integrity on Local server connection Databases: <list of databases> Include indexes Task start: 2008-02-21T00:05:42. Task end: 2008-02-21T00:05:46. Failed0) Alter failed for Server €˜XYZ€™
I created a test maintenance plan to just do the integrity check and selected one database only and this also failed with the same error message. I ran this test maintenance plan and configured it for each of the databases in question and it failed each time. If I run the DBCC manually against the databases they all report fine.
I read some of the post that talked about the €œAllow Updates€? being set incorrectly but that does not apply to my problem since my configured and run values are set to 0.
I have a re-indexing stored procedure,yester day night it got failed "Executed as user: CONNECTSRVmyadmin. sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed." what may be the reason..
[Source - chn_employee_vew_test_txt [1]] Error: Data conversion failed. The data conversion for column "Column 42" returned status value 4 and status text "Text was truncated or one or more characters had no match in the target code page.".
[Source - chn_employee_vew_test_txt [1]] Error: The "output column "Column 42" (136)" failed because truncation occurred, and the truncation row disposition on "output column "Column 42" (136)" specifies failure on truncation. A truncation error occurred on the specified object of the specified component.
I using Locale (People's Republic of China) and code page of 936 (Simplied Chinese GBK) with header row delimiter {CR}{LF}.
I am using flat file import method.
Whenever the server process the Column 42 with value "11,Nanjing Rd.W, China" which contain 'comma' or '.' it will hit error importing with above message. When i manually change the column value to non comma or '.' (11 Nanjing Rd W China) in the flat file it is ok.
I am using SQL server 2005.
Please advise what need to be done to avoid this error ?
Thanks in advance and any idea or suggestion is very much appreciated as i have try to solve this issue for over a week but still not able to find any answer on it.
I am running the Sept CTP. I have created a SSIS package that pulls data from a text file and inserts into a database. When I run the package on the DB server it runs fine. I have moved the package the the web server (we are attempting to kick off the package from a web site) and we get connections errors. We are running the package using dtexec from the command line.
[Source - chn_employee_vew_test_txt [1]] Error: Data conversion failed. The data conversion for column "Column 42" returned status value 4 and status text "Text was truncated or one or more characters had no match in the target code page.".
[Source - chn_employee_vew_test_txt [1]] Error: The "output column "Column 42" (136)" failed because truncation occurred, and the truncation row disposition on "output column "Column 42" (136)" specifies failure on truncation. A truncation error occurred on the specified object of the specified component.
I using Locale (People's Republic of China) and code page of 936 (Simplied Chinese GBK) with header row delimiter {CR}{LF}.
I am using flat file import method.
Whenever the server process the Column 42 with value "11,Nanjing Rd.W, China" which contain 'comma' or '.' it will hit error importing with above message. When i manually change the column value to non comma or '.' (11 Nanjing Rd W China) in the flat file it is ok.
I am using SQL server 2005.
Please advise what need to be done to avoid this error ?
Thanks in advance and any idea or suggestion is very much appreciated as i have try to solve this issue for over a week but still not able to find any answer on it.
when i right click and execute the package from the Management Studio, it runs fine, everytime. When i schedule a job to execute it, it fails, everytime.
"The package execution failed. The step failed."
i have made sure that the package and job ran using credentials with more than enough access to everything. Still, with no luck. PLEASE! I am at my wits ends here, and the boss is getting antsey...
Im trying to installed SQL SP1 and I get 'cancelled' status on the Database Services product.
If I open the SQL9_Hotfix_KB913090.log I see a bunch of 'Failed to read" errors. Im not very good at debugging SQL Logs, could you please assists me or tell me where to look?
02/15/2007 15:09:58.436 ================================================================================ 02/15/2007 15:09:58.436 Hotfix package launched 02/15/2007 15:09:59.405 Product discovery successfully completed during the install process for MSSQLSERVER 02/15/2007 15:09:59.405 SP Level check successfully completed during the install process for MSSQLSERVER 02/15/2007 15:09:59.421 Product language check successfully completed during the install process for MSSQLSERVER 02/15/2007 15:09:59.421 Product version check successfully completed during the install process for MSSQLSERVER 02/15/2007 15:09:59.421 Command-line instance name check completed during the install process 02/15/2007 15:09:59.421 Baseline build check completed during the install process 02/15/2007 15:10:21.892 Attempting to install instance: MSSQLSERVER 02/15/2007 15:10:21.892 Attempting to install target: DEV08 02/15/2007 15:10:21.892 Attempting to stop service: SQLSERVERAGENT 02/15/2007 15:10:25.893 Successfully stopped service: SQLSERVERAGENT 02/15/2007 15:10:25.893 Attempting to stop service: MSSQLServer 02/15/2007 15:10:27.893 Successfully stopped service: MSSQLServer 02/15/2007 15:10:27.893 Attempting to check for locked files: sqlrun_sql.msp 02/15/2007 15:10:27.909 Attempting to check for locked files: \DEV08D$KitsSQL2005_StandardSP1HotFixSQLFilessqlrun_sql.msp 02/15/2007 15:10:27.909 Creating MSP locked file check log at: C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB913090_sqlrun_sql.msp.out 02/15/2007 15:10:39.520 MSP returned 1602: The user cancels installation. 02/15/2007 15:10:39.567 Successfully checked file: \DEV08D$KitsSQL2005_StandardSP1HotFixSQLFilessqlrun_sql.msp 02/15/2007 15:10:39.567 Successfully opened registry key: SystemCurrentControlSetControlSession Manager 02/15/2007 15:10:39.567 Failed to read registry key: PendingFileRenameOperations 02/15/2007 15:10:39.567 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxmlfilt.dll 02/15/2007 15:10:39.567 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnThaWBrkr.dll 02/15/2007 15:10:39.567 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnquery.dll 02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnls400.dll 02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnlhtml.dll 02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsir5jp.dll 02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftesql.exe 02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftepxy.dll 02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftefd.exe 02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsfte.dll 02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnLangWrbk.dll 02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnkorwbrkr.dll 02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinninfosoft.dll 02/15/2007 15:10:39.598 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnFTERefFTERef.dll 02/15/2007 15:10:39.598 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnCHTBRKR.DLL 02/15/2007 15:10:39.598 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnChsBrkr.dll 02/15/2007 15:10:39.598 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COMResources1033REPLRES.rll 02/15/2007 15:10:39.598 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COM eplrec.dll 02/15/2007 15:10:39.598 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COM plisapi.dll 02/15/2007 15:10:39.598 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:WINDOWSassemblyGAC_32Microsoft.SqlServer.Replication9.0.242.0__89845dcd8080cc91Repl.dll 02/15/2007 15:10:39.598 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.DataStorage9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.DataStorage.dll 02/15/2007 15:10:39.598 Failed to read version information for the following file: C:Program FilesCommon FilesMicrosoft SharedDatabase ReplicationResources10332005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall plhtfin.sql 02/15/2007 15:10:39.598 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall C:Program FilesMicrosoft SQL Server90COMqrdrsvc.exe 02/15/2007 15:10:39.598 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COMsnapshot.exe 02/15/2007 15:10:39.598 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COM eplmerg.exe 02/15/2007 15:10:39.598 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90COM ablediff.exe 02/15/2007 15:10:39.598 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COMDISTRIB.exe 02/15/2007 15:10:39.613 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnDatabaseMail90.exe 02/15/2007 15:10:39.613 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources30822005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources2052sqlevn70.rll 02/15/2007 15:10:39.613 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10422005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1041sqlevn70.rll 02/15/2007 15:10:39.613 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10402005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1036sqlevn70.rll 02/15/2007 15:10:39.613 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10332005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1031sqlevn70.rll 02/15/2007 15:10:39.613 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10282005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033XPStar90.RLL 02/15/2007 15:10:39.613 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll 02/15/2007 15:10:39.613 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll 02/15/2007 15:10:39.613 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll 02/15/2007 15:10:39.613 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn6.6.3.5 C:Program FilesMicrosoft SQL Server90Sharedmsxmlsql.dll 02/15/2007 15:10:39.613 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2.0.3609.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxmlrw.dll 02/15/2007 15:10:39.613 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll 02/15/2007 15:10:39.613 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll 02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll 02/15/2007 15:10:39.629 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLBOOT.dll 02/15/2007 15:10:39.629 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxplog70.dll 02/15/2007 15:10:39.629 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnatchp~1.dll 02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll 02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll 02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll 02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL 02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL 02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL 02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll 02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll 02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll 02/15/2007 15:10:39.645 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE 02/15/2007 15:10:39.645 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE 02/15/2007 15:10:39.645 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE 02/15/2007 15:10:39.645 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90SharedResources10339.0.2047.0 C:Program FilesMicrosoft SQL Server90Sharedmsmdrdir.dll 02/15/2007 15:10:39.645 Failed to read version information for the following file: C:Program FilesCommon FilesSystemole db2.0.3609.0 C:Program FilesCommon FilesSystemole dbxmlrw.dll 02/15/2007 15:10:39.645 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll 02/15/2007 15:10:39.645 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll 02/15/2007 15:10:39.660 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll 02/15/2007 15:10:39.660 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe 02/15/2007 15:10:39.660 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe 02/15/2007 15:10:39.660 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe 02/15/2007 15:10:39.660 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll 02/15/2007 15:10:39.660 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll 02/15/2007 15:10:39.660 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll 02/15/2007 15:10:39.676 Failed to read version information for the following file: C:Program FilesMicrosoft.NETADOMD.NET90enMicrosoft.AnalysisServices.AdomdClient.xml 02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft.NETADOMD.NET90Microsoft.AnalysisServices.AdomdClient.dll 02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.AnalysisServices.AdomdClient9.0.242.0__89845dcd8080cc91Microsoft.AnalysisServices.AdomdClient.dll 02/15/2007 15:10:39.676 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033 C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033sqlcm.xml 02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll 02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll 02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll 02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll 02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll 02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll 02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll 02/15/2007 15:10:39.692 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll 02/15/2007 15:10:39.692 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll 02/15/2007 15:10:39.692 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources10332005.90.2047.0 C:Program FilesMicrosoft SQL Server90ToolsinnSQLSVC90.DLL 02/15/2007 15:10:39.692 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinn2.0.3609.0 C:Program FilesMicrosoft SQL Server90ToolsBinnSQLdiag.exe 02/15/2007 15:10:39.692 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinn2005.90.2047.0 C:Program FilesMicrosoft SQL Server90Sharedsqlsvc~1.dll 02/15/2007 15:10:39.692 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll 02/15/2007 15:10:39.692 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll 02/15/2007 15:10:39.692 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll 02/15/2007 15:10:39.707 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll 02/15/2007 15:10:39.707 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll 02/15/2007 15:10:39.707 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll 02/15/2007 15:10:39.707 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll 02/15/2007 15:10:39.707 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll 02/15/2007 15:10:39.707 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll 02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll 02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll 02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll 02/15/2007 15:10:39.723 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90Shared2005.90.2047.0 C:Program FilesMicrosoft SQL Server90Sharedsqlsqm.exe 02/15/2007 15:10:39.723 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90Shared9.0.2047.0 C:Program FilesMicrosoft SQL Server90Shareddbghelp.dll 02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe 02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe 02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe 02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.Rmo9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.Rmo.dll 02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.AnalysisServices9.0.242.0__89845dcd8080cc91Microsoft.AnalysisServices.DLL 02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.DataWarehouse.Interfaces9.0.242.0__89845dcd8080cc91Microsoft.DataWarehouse.Interfaces.DLL 02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.RegSvrEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.RegSvrEnum.dll 02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll 02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll 02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll 02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.ServiceBrokerEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.ServiceBrokerEnum.dll 02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.WmiEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.WmiEnum.dll 02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.SqlEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.SqlEnum.dll 02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.SmoEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.SmoEnum.dll 02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.Smo9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.Smo.dll 02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlSAC.exe 02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedMicrosoft.SqlSac.Public.dll 02/15/2007 15:10:51.256 The following exception occurred: User canceled patch install Date: 02/15/2007 15:10:51.256 File: depotsqlvaultsetupmainsetupsqlsesqlsedllfilegroup.cpp Line: 865 02/15/2007 15:10:51.256 Restarting SQL Service MSSQLServer since it was previously running 02/15/2007 15:10:51.256 Attempting to start service: MSSQLServer 02/15/2007 15:10:54.944 Successfully started service: MSSQLServer 02/15/2007 15:10:54.944 Restarting SQL Agent Service SQLSERVERAGENT since it was previously running 02/15/2007 15:10:54.959 Attempting to start service: SQLSERVERAGENT 02/15/2007 15:10:58.350 Successfully started service: SQLSERVERAGENT 02/15/2007 15:10:58.350 02/15/2007 15:10:58.350 Product Status Summary: 02/15/2007 15:10:58.350 Product: SQL Server Native Client 02/15/2007 15:10:58.350 SQL Server Native Client (RTM ) - Success 02/15/2007 15:10:58.350 02/15/2007 15:10:58.350 Product: Setup Support Files 02/15/2007 15:10:58.350 Setup Support Files (RTM ) - Success 02/15/2007 15:10:58.350 02/15/2007 15:10:58.350 Product: Database Services 02/15/2007 15:10:58.350 Database Services (RTM 1399 ENU) - Cancelled 02/15/2007 15:10:58.350 Reporting Services (SP1 2047 ENU) - Not Applied 02/15/2007 15:10:58.350 02/15/2007 15:10:58.350 Product: Integration Services 02/15/2007 15:10:58.350 Integration Services (SP1 2047 ENU) - Not Selected 02/15/2007 15:10:58.350 02/15/2007 15:10:58.350 Product: Client Components 02/15/2007 15:10:58.366 Client Components (SP1 2047 ENU) - Not Selected 02/15/2007 15:10:58.366 02/15/2007 15:10:58.366 Product: MSXML 6.0 Parser 02/15/2007 15:10:58.366 MSXML 6.0 Parser (RTM ) - Not Selected 02/15/2007 15:10:58.366 02/15/2007 15:10:58.366 Product: SQLXML4 02/15/2007 15:10:58.366 SQLXML4 (RTM ) - Not Selected 02/15/2007 15:10:58.366 02/15/2007 15:10:58.366 Product: Backward Compatibility 02/15/2007 15:10:58.366 Backward Compatibility (RTM ) - Not Selected 02/15/2007 15:10:58.366 02/15/2007 15:10:58.366 Product: Microsoft SQL Server VSS Writer 02/15/2007 15:10:58.366 Microsoft SQL Server VSS Writer (RTM ) - Not Selected 02/15/2007 15:10:58.366
I'm running a DTS package that works correctly when I do "Execute Package" directly, by right clicking the package.
But, if I schedule the job, it fails.
It's trying to write data to another server, but I can't see why it doesn't work as a scheduled job. I tried changing all the parameters I can think of. I'm no Windows expert, so if you have any ideas, please feel free to explain as if you're talking to a "newbie" (since I am one)
I am going to tangle with our ERP system for the rest of my natural life, and in so doing, will need to create new SQL queries on an almost-daily basis. Based on the handful of queries that I have created against it so far, I recognize that I need to get better at authoring them.
Towards that end, I was wondering if anyone with a little firmer grasp on the subject could take a look at this query (which works & does exactly what I need it to do) and make suggestions as to what I might have done better/differently.
I've changed the names of everything to make it more comprehensible (I hope).
The query returns one row for each unique record in DetailTable, with data from the SummaryTable and a PartDescription from ThirdTable.
FROMtheDatabase.dbo.DetailTable LEFT JOIN theDatabase.dbo.SummaryTable ON DetailTable.RecordID=SummaryTable.RecordID LEFT JOIN theDatabase.dbo.ThirdTable on SummaryTable.PartNumber = ThirdTable.PartNumber AND SummaryTable.PartRevision = ThirdTable.PartRevision
WHERE (SummaryTable.IssueCategory='1' OR SummaryTable.IssueCategory='2' OR SummaryTable.IssueCategory='3' OR SummaryTable.IssueCategory='D' OR SummaryTable.IssueCategory='E' OR SummaryTable.IssueCategory='L' OR SummaryTable.IssueCategory='O' OR SummaryTable.IssueCategory='R' OR SummaryTable.IssueCategory='S' OR SummaryTable.IssueCategory='V' OR SummaryTable.IssueCategory='X' OR SummaryTable.IssueCategory='Z') AND SummaryTable.Facility='Default' AND SummaryTable.Status='OPEN'
I have a VB app that loads 9 text files for 8 different products, one product at a time. The user must select the product to import. For each product the application:
1. Copies the 9 text files from the source directory to a "process" directory. 2. Calls a stored procedure that sequentially calls a different SSIS package for each text file. 3. Performs some additional processing.
Here's the problem. For the 7th product in the sequence, at least 2 of the text files are not being loaded, and no error exceptions are being thrown. For the 8th product in the sequence at least one text file is not being loaded. If I comment out the call to the stored proc in VB and run the stored proc manually at that point in the program, all files are processed.
On the text file side, the files are being copied correctly and the read-only flag on the file is not being set. In addition, I can open the files in a text editor without any problem.
I'm totally stumped here, so any helpful advice would be appreciated.
I have an asp.net page that executes a DTS. When I execute that DTS from enterprise manager it takes about 5000 rows from the as400 and insert into sql serverIt works right. but when I execute it from my asp.net page I have this error.Error al procesar DTS TransferirDatos(ExistMP) en el paso DTSStep_DTSActiveScriptTask_1System.Exception: Error al procesar DTS TransferirDatos(ExistMP) en el paso DTSStep_DTSActiveScriptTask_1 at LibreraLentos.exec.ejecuta_SP_EXISTENCIASMP() in C:Documents and SettingsluisvalenMis documentosVisual Studio ProjectsInventariosLentosLibreraLentosexec.vb:line 43 at InventariosLentos.generacionprocesomateriaprima.btnenviar_Click(Object sender, EventArgs e) in C:AplicacionesWebInventariosLentosgeneracionprocesomateriaprima.aspx.vb:line 60LibreraLentos I have this on my ASP page Private Sub btnenviar_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btnenviar.Click Try objexecsp.ejecuta_SP_EXISTENCIASMP() lblmensajes.Text = "Proceso generado satisfactoriamente" Catch ex As Exception lblmensajes.Text = ex.Message + ex.GetBaseException.ToString + ex.Source.ToString End Try End Subthis on my Data Classs Public Function ejecuta_SP_EXISTENCIASMP() ' call UpdatePrice using a parameter array of SqlParameter objects Try Dim ejecutardts As New cDTS ejecutardts.EjecutarDTS("TransferirDatos(ExistMP)") Catch ex As Exception Throw ex End Try End FunctionThis is what executes the DTSImports System.Runtime.InteropServicesImports System.Configuration.ConfigurationSettingsImports DTSPublic Class cDTS Public Sub EjecutarDTS(ByVal NombreDTS As String) Dim pkg As New DTS.Package Dim oStep As DTS.Step Try pkg = New DTS.Package 'pkg.LoadFromSQLServer(AppSettings("MED20NT"), AppSettings("user"), AppSettings("pwd"), DTSSQLServerStorageFlags.DTSSQLStgFlag_Default, "", "", "", "pruebaCdr1") pkg.LoadFromSQLServer("MED20NT", "sa", "prueva", DTSSQLServerStorageFlags.DTSSQLStgFlag_Default, "", "", "", NombreDTS, "") pkg.AutoCommitTransaction = True pkg.Execute() For Each oStep In pkg.Steps If oStep.ExecutionResult = DTSStepExecResult.DTSStepExecResult_Failure Then Throw New Exception("Error al procesar DTS " & pkg.Name & " en el paso " & oStep.Name) End If Next Catch ex As System.Runtime.InteropServices.COMException Throw ex Catch ex As Exception Throw ex Finally pkg.UnInitialize() pkg = Nothing End Try End SubEnd Class
Can anyone enlighten me on sqlexpress smo? I have compiled an exe using vbc running the folloing code Imports SystemImports Microsoft.SqlServer.Management.SmoImports Microsoft.SqlServer.Management.CommonImports System.IO Module SMOtest Sub Main() Try Kill(System.Environment.GetFolderPath Environment.SpecialFolder.ProgramFiles) & " estSMO_BACKUP") Catch End Try Try System.Threading.Thread.Sleep(500) Dim bkpfileName As String = System.Environment.GetFolderPath(Environment.SpecialFolder.ProgramFiles) & " estSMO_BACKUP" Dim backDeviceItem As New BackupDeviceItem(bkpfileName, DeviceType.File) Dim db As String = "test" ' Define and set db Dim bck As New Backup() ' Instantiate a Backup object bck.Action = BackupActionType.Database ' Set Action bck.BackupSetName = db & "_BackupSet" ' Set Backup bck.Database = db ' Set Database name property bck.Devices.Add(backDeviceItem) Dim srv As New Server() ' Instantiate a Server object bck.SqlBackup(srv) ' Invoke Backup object's SqlBackup method Catch End Try End SubEnd Module This works fine on a win2k dev system though when moving to another win2k system the code will error on non system databases. If db= model,master,tempdb etc it executes fine. When I try to backup a created db (any) I get an error stating the name is not found in sysdatabases. SELECT name FROM master..sysdatabases where name not in ('master','tempdb') shows all the created databases including "test" in this case keep in mind many recompiles using different db's work fine on one system and not the other. Even restored "test" from a backup from the system with no problems only to have a 3041 error consistently on the other. System databases work fine for all attempts on the offending system. Any ideas? (the offending system is a SAT raid which has been evil from the get go) corruption seems to be the only conclusion I can reach
Help, I had my entire DB created and when i thought i was done, i upsized to SQL and now almost none of my queries work?
The below works when i remove Distinct, but then i have doubles?
Code:
SELECT DISTINCT Equip_ProductName.ProductName, Equip_ProductName.ProductInfoID, Equip_ProductName.ProductDesc, Equip_ProductName.ProductSearchTerm, Equip_ProductName.ProductMore, Equip_ProductName.Visible, Equip_Products.ProductID, Equip_Products.CategoryID FROM Equip_Products INNER JOIN Equip_ProductName ON Equip_Products.ProductInfoID = Equip_ProductName.ProductInfoID WHERE (Equip_ProductName.Visible = 1) AND (Equip_Products.CategoryID = 1) ORDER BY Equip_ProductName.ProductName
As an accomplished web devver of many years using ASP and ASP.NET in conjunction with Access and SQL Server, I am a bit pedantic on the rules of good data structures.
Specifically the two main rules of data redundancy and normalisation.
The latter dictates at the lowest level that a data table should NOT contain a field that can be gleaned from one or a combination of others.
I have a problem with this now, I am building a betting system which will take the odds given, plus the stake placed and calculate the winnings or losses accordingly.
There is an added complication in that not all profit is calculated the same way, as a horse can also be 'placed' which does the same calculation as for profit, but then quarters it, so one single select statement won't do.
I could calculate this at data entry stage on a per entry basis and simply store in a Profit/Loss field and keep the value for each bet, however I know this is not the correct thing to do!
My other alternative [and the correct method] is to do this calculation at data request time, but that would involve the use of a cursor or loop in the SP.
I am aware of the huge resources a cursor can consume and I am not sure which is worse, using a cursor or ignoring the normalisation procedures.
So the question is this, what would you do here?
Since I may not be the same SQL Server expert as I am a programmer, is there an alternative way of reading all the bets and doing these calcs on SQL server and bang them back to ASP as a self contained recordset with all the profit/losses calculated for each bet?
Each bet as a unique EntryID and there is a field called Result which stores 'Win, Place or Loss' accordingly.
I have a DTS to copy data from Oracle to SQL Server. When I logon to SQL Server box with a userID xxx, I can run the DTS from EM and it works perfectly fine but when I schedule the DTS as job, it fails.
SQL Server agent is running with same account "xxx" DTS connects to SQL Server with sa authentication Job owner is same account "xxx"
Job error log
Executed as user: DOMAINNAMExxx. ... Drop table [IFS_PROD].[dbo].[INVENTORY_PART] Step DTSRun OnStart: Drop table [IFS_PROD].[dbo].[PART_CATALOG] Step DTSRun OnStart: Drop table [IFS_PROD].[dbo].[SUPPLIER_INFO] Step DTSRun OnStart: DTSStep_DTSExecuteSQLTask_1 DTSRun OnFinish: Drop table [IFS_PROD].[dbo].[PART_CATALOG] Step DTSRun OnFinish: Drop table [IFS_PROD].[dbo].[INVENTORY_PART] Step DTSRun OnStart: Create Table [IFS_PROD].[dbo].[INVENTORY_PART] Step DTSRun OnStart: Create Table [IFS_PROD].[dbo].[PART_CATALOG] Step DTSRun OnFinish: Drop table [IFS_PROD].[dbo].[SUPPLIER_INFO] Step DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_1 DTSRun OnStart: Create Table [IFS_PROD].[dbo].[SUPPLIER_INFO] Step DTSRun OnStart: Create Table [IFS_PROD].[dbo].[SUPPLIER_INFO_ADDRESS] Step DTSRun OnFinish: Create Table [IFS_PROD].[dbo].[PART_CATALOG] Step DTSRun OnFinish: Create Table [IFS_PROD].[dbo].[INVENTORY_PART] Step DTSRun OnStart... Process Exit Code 6. The step failed.
I copied the DTS to another one and scheduled it
This time I got the error log Executed as user: DOMAINNAMExxx. ...... DTSRun OnStart: DTSStep_DTSExecuteSQLTask_1 DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_1 DTSRun OnStart: Create Table [IFS_PROD].[dbo].[SUPPLIER_INFO_ADDRESS] Step DTSRun OnFinish: Create Table [IFS_PROD].[dbo].[SUPPLIER_INFO_ADDRESS] Step DTSRun OnStart: Copy Data from SUPPLIER_INFO_ADDRESS to [IFS_PROD].[dbo].[SUPPLIER_INFO_ADDRESS] Step DTSRun OnError: Copy Data from SUPPLIER_INFO_ADDRESS to [IFS_PROD].[dbo].[SUPPLIER_INFO_ADDRESS] Step, Error = -2147467259 (80004005) Error string: Oracle client and networking components were not found. These components are supplied by Oracle Corporation and are part of the Oracle Version 7.3.3 or later client software installation. Provider is unable to function until these components are installed. Error source: Microsoft OLE DB Provider for Oracle Help file: Help context: 0 Error Detail Records: Error: -2147467259 (80004005); Provider Error: 0 (. The step failed.
set @out_dte = '2006-08-03 04:05:12.670' set @FileName = cast(DATEPART(mm,@out_dte) as char(2)) + cast(DATEPART(dd,@out_dte) as char(2)) + cast(DATEPART(HH,@out_dte) as char(2)) + cast(DATEPART(mm,@out_dte) as char(2)) + 'DX.748'
select @FileName
… but then date and time values were left justified spaced filled. Example output: 8 3 4 8 DX.748
I don't just want to get code that works. I want to learn how to write the best possible code.
I would like to use sp_start_job to execute a SSIS Package but I am not sure how it works. If there are two requests run the job two times simultaneously or sequentially?
I'm able to execute a package in VS Pro on my machine. However when I upload it to the sql server and try to execute the package directly it fails with:
Error: The product level is insuficient for component "...." (3129) Error: The product level is insuficient for component "...." (5411)
The first component is a DataReader Source which is consuming an ODBC (Noble Systems ATOMIX Driver) connection and the second component is a DataConversion object. Anyone know why this would work running it on my pc in VS but not when I execute it from SQL on the same machine?
I'm coming from Oracle world and my knowledge about SQL Server is quite limited so I apriori apologize for probably stupid questions
DB version is SQL Server 2005. The business scenario is - there is search form with many criteria. User may enter very unrestrictive criteria matching probably millions of rows. To prevent that we'd like to show him no more than N rows (N ~200). Any rows matching criteria are good enough, however these FOUND rows we'd like to sort. I do not want to find all potentially X million rows, then sort them and only then show forst N rows. So in Oracle I know how to do that. I just find N rows in subquery, and then in outer query sort them. So I avoid to find all rows and then sorting millions of rows. Here is an example:
Code Block SQL> create table t (id number, data varchar2 Table created. SQL> insert into t values (1, 'aaa'); 1 row created. SQL> insert into t values (2, 'bbb'); 1 row created. SQL> insert into t values (3, 'ccc'); 1 row created. SQL> select * from ( 2 select * from t where rownum <=2) 3 ; ID DATA ---------- -------------------- 1 aaa 2 bbb SQL> ed Wrote file afiedt.buf 1 select * from ( 2 select * from t where rownum <=2) 3* order by data desc SQL> / ID DATA ---------- -------------------- 2 bbb 1 aaa
However how can I avoid sort of potential big result in SQL Server? I've searched google but unfortunately found nothing. I've tried to use both TOP and SET rowcount without success i.e. from these examples I assume that DB will find ALL rows matching where clause then sort them keeping only first N. It seems that order by clause in outer query is pushed into inner query both for top and set rowcount.
Code Block create table t (id integer, data varchar(20)); insert into t values (1, 'aaa'); insert into t values (2, 'bbb'); insert into t values (3, 'ccc');
select * from ( select top 2 * from t) as q
1 aaa 2 bbb
select * from ( select top 2 * from t) as q order by data desc
3 ccc 2 bbb
set rowcount 2 select * from ( select * from t) as q
1 aaa 2 bbb
set rowcount 2 select * from ( select * from t) as q order by data desc
3 ccc 2 bbb
And I'd like to avoid sort because of two reasons: 1) I predict that generally finding all rows will be much more costly than finding just any no more than N 2) Sorting all found rows also probably will be slower than just N (however DB has to find only first N rows, so not ALL rows should be sorted/kept sorted)
Are my concerns reasonable? If yes what can I do to just find N rows and sort only these?
