I'd recently upgraded SQL Server2000 to SQL server2005. I've been using Tibco DX to connect to the database. While working with SQL Server2000 things were going fine. I could access the databases from the repository through TibcoDX and could deploy my tasks which involved migrating data from source to target databases. But when I had installed SQL server 2005 an error cropped up while deploying tasks
Exception occurred while initializing the JDBCTransformer: The TCP/IP connection to the host has failed. java.net.UnknownHostException:
I'd checked the port numbers and they were matching, the TCP protocols were also enabled. But I'm not able to fix this problem. Any help would be highly appreciated. Thank You.
I attempt to back up a database on one server and restore it on my local machine.This is what the query text looks like:restore database model fromDisk='c:JQJmydumpmodel.bak'with replaceI get this error:The backup of the system database on device c:JQJmydumpmodel.bak cannot be restored because it was created by adifferent version of the server(134217922) than this server (134218488).The other server product version is: 8.00.194(RTM)The server on my machine is 8.00.760(SP3)1.How can I make this restore work? Seems to me I have the later version, so I should be able to handle it. Mine is a10-user, and the other is enterprise.2.Also I need to be able to force a different path and even database name: The source server where I create the backup filemay have a different location than I have on my machine, so what parameters can I give the command so that it will use thelocation I specifiy? The backup file will have the location information relative to the source server, which I can notalways use. This means I will need to programatically extract that location information on my machine. (I can't hard codeit, since other people with different installation setups will use my program on their machines).3.The database name on the source server may be ABC, but I may want to restore over XYZ. How can I force that? Perhaps itwould be the same parameter I need for 2.Thanks,Jon
I added a connection (ADO.NET) object by name testCon in the connection manager - I wanted to programmatically supply the connection string. So I used the "Expressions" property of the connection object and set the connectionstring to one DTS variable. The idea is to supply the connection string value to the variable - so that the connection object uses my connection string.
Then I added a "Backup Database Task" to my package with the name BkpTask. Now whenever I try to set the connection property of BkpTask to the testCon connection object, by typing testCon, it automatically gets cleared. I am not able to set the connection value.
Then after spending several hours I found that this is because I have customized the connection string in testCon. If I don't customize the connection string, I am able to enter the "testCon" value in the connection property of the BkpTask.
I have a DTS setup that copies a couple of databases from one server to another in order to have a hot backup server. When I execute the DTS package from the DTS portion of the Enterprise Manager tree it runs fine. When I schedule it, it fails with the following error:
Much of the data in the Comments field already has carriage return in it. When I use bcp out -c, it uses as a new record to figure out when the new row stats. However, the data in that column has carriage returns! Hence, when it detects the carriage return in the user data(comments) itself, it is pushing the remainder of that text to the 2nd line. Then, when I try to BCP IN, it is trying to push it into ID column!
The text file looks something like this:
ID COMMENTS -- --------- 1 This is a very long comment with a line return now. User hits return here. This should be part of the previous record but gets detected as a new row 2 Some Text 3 Some Text
So, in the BCP IN, it is trying to put 'This should be part of..' into the ID column and I am getting an error.
Is there any way I can get BCP to NOT recognize in user data as end of a record??
We've had RS running on an internal network for a while now and initially installed it with no SSL certificate. We recently decided that we would like to make some reports available through the web, and that we should secure the data with SSL. So, we registered and set up the subdomain, bought and installed the certificate, closed off all but port 443 on the box in question, and opened it up to the world. We tweaked a few options in the RS config files (after reading around):
RSReportServer.config: - SecureConnectionLevel changed from 0 to 2 (recommended) - this changed all but the help file links to https://. - UrlRoot changed from HTTP to HTTPS, and also changed from internal to external name (to match the SSL certificate)
RSWebApplication.config: - ReportServerUrl changed from HTTP to HTTPS and changed from internal to external name.
After this was changed, along with some IIS tweaks, we were able to get to the report manager through the web, and force SSL only. The problem right now is that we are intermittently getting "Underlying connection closed" errors (described here: http://support.microsoft.com/kb/915599). ; The odd thing is that we first get the Windows login prompt, wait about a minute then get the error (which is encapsulated by the Report Manager page style). After a quick browser refresh, the Report Manager appears almost instantly, with no 2nd request for a windows login.
My question: Are there any IIS or RS config settings I can look at, or any log file entries I should look for in order to determine the cause of this problem? My guess at this point is the error has to do with some sort of timeout, but to be honest, I have no clue.
I want to be able to intersect many tables. I am building my query from vb code in asp .net based on key fields entered in a search engine box.my query should look like this, which will return the rows that will have the values var, var_2, var_3 in any columns. All three must be in a row for it to be a hit. I cant get this to work in ms sql. I don't know if it supports this feature.select * from t where column1 Like '%var%' or column2 like '%var%' or column3 like '%var%'intersect select * from t where column1 Like '%var_2%' or column2 like '%var_2%' or column3 like '%var_2%'intersectselect * from t where column1 Like '%var_3%' or column2 like '%var_3%' or column3 like '%var_3%' I also googled around and found a where exists... But cant seem to figure out how to do multiple tables:select * from t where exists (select * from t where column1 Like '%var_3%' or column2 like '%var_3%' or column3 like '%var_3%') i would like to add multiple conditions to the where exists table. Could anyone please tell me what I am doing wrong.
Taking the advise from one of the postings I removed the setting for checkpoint log on checkpoint. I have set up a batch job that does a dbcc checktable (syslogs) and a dump transaction with no_log every 15 minutes. We are a development shop and do not need the transaction log, I would have liked to use the truncate log on checkpoint. I found that the transaction log seems to grow indefinitely by viewing DBCC sqlPerf and sp_spaceused if I do not first issue the checktable command. Why is this needed? This is the same problem I had with the truncate log on checkpoint option. Has anyone else encountered a similar problem? We have an application that does single row inserts multithreaded at a rate of 2500 rows a second. Without performing the dbcc checktable the log filled to over 80% in a 45 minute period. Running the stored procedure with the two commands the logs stays under 40%.
Trying to get my jobs to send mail when job fails. Should be easy but it's giving me headache
Had a whole slew of issues. Outlook is installed with a n outlook mail profile set up that can send mail in outlook. I can create a SendMail DTS and execute it to send mail
Email works in these scenarios 1. I create a DTS package in SQL Server with just SendMail with the same Profile "ABC" and click Execute and it sends 2. I can send using Outlook with the same profile "ABC" 3. I can run DTSRun with command prompt calliing the DTS package and it sends fine
However it wont send in these 3 scenarios (where I need it!):
1. I go to Operator, and put my Profile "ABC" in the Email Name, click Test and I get this error "Error 22022: SQLServerAgent Error: The SQLSErverAgent mails ession is not running; check the mail profile and/or the SQLServerAgent service startup account in the SQLSErverAGent Properties sQLServer Agent is running
2. If I add the DTS Package "EmailTest" to one of my jobs as a step to go to if the 1st step fails, nothing gets sent
3. In JObs -- Notificatioin, If I set the E-maill operator to my operator, nothing gets sent
I set the Mail Profile to the Mail Profile (in SQL Server AGent' properties) However when I click Test, I get this error: Error 0: Cannot load the DLL sqlmap70.dll, or one of the DLLs it references
I am using SQLServer Version 8.00.194, OS Windows 2003
I don't know if anyone can help me but I have two issues with SQL Server 2000 SP4 (version 8.00.2039 - Desktop Engine) running on W2K and W2K3. I'm also running SQLXML 3.0 (msxml2.dll version is 8.30.9530.0).
Is it me or is sp_xml_preparedocument a crippled fat dog that is blind?...not that I have anything against crippled fat dogs that are blind :)
In all the stored procs I have developed, I pass a text var as an input parameter and return an IStream to ADO (using an sqlxml provider) in COM+. All has been very well and fine...until the passed text parameter resembles a data object of any decent size.
The first error I was noticing was a "XML Parsing Error: not enough storage is available to complete this operation". Well, I thought I would debug logically in a step fashion and just prepare the doc first and then do a return and then do a return on the next segment of code to find out where the issue is. I was amazed to find that sp_xml_preparedocument is taking 7 seconds to load a simple 1MByte text input var and around three minutes to load a 7 MByte file.
I believe these long load times are causing issues with transaction timouts etc so I thought I would try to solve the speed issue with sp_xml_preparedocument and then see if the "XML Parsing Error" continues.
So, my first question is:
Should sp_xml_preparedocument take 7 seconds to load a 1MByte text variable and nearly three odd minutes to load a 7 MByte file? Surely there is something wrong somewhere?
I'm also running these tests on two machines - one is 2 GHz and the other is 2.4 GHz P4's.
SELECT T1.* FROM Cust_Table T1 INNER JOIN ( SELECT Family_Name FROM Cust_Table WHERE Cust_Name IN ('Billy', 'John') AND RowNum < 100 GROUP BY Family_Name HAVING COUNT(*) > 1 ) T2 ON T1.Family_Name= T2.Family_Name WHERE RowNum < 100
( This code above finds all the familys that contain either multiple billys and/or multiple Johns and displays all the duplicates ordered by the family_name. )
The problem is that what I want it to do is search through the whole table and find within each Family (Family_ID) who has both a sibling called Billy AND John (Cust_Name) wether they have multiple johns and multiple billys I don't mind as long as they have a minimum of 1 of each. I then want to just output all those examples only not anything else. An example of the table is bellow, I hope this helps. Thanks for your advice.
BEFORE Family_Name CUST_Name Bruce Billy Bruce John Bruce Mike Bruce Oli Smith Billy Smith Billy Harold John
AFTER Family_Name CUST_Name Bruce Billy Bruce John
Trying to get my jobs to send mail when job fails. Should be easy butit's giving me headacheHad a whole slew of issues. Outlook is installed with a n outlookmail profile set up that can send mail in outlook. I can create aSendMail DTS and execute it to send mailEmail works in these scenarios1. I create a DTS package in SQL Server with just SendMail with thesame Profile "ABC" and click Execute and it sends2. I can send using Outlook with the same profile "ABC"3. I can run DTSRun with command prompt calliing the DTS package andit sends fineHowever it wont send in these 3 scenarios (where I need it!):1. I go to Operator, and put my Profile "ABC" in the Email Name,click Test and I get this error "Error 22022: SQLServerAgent Error:The SQLSErverAgent mails ession is not running; check the mail profileand/or the SQLServerAgent service startup account in theSQLSErverAGent PropertiessQLServer Agent is running2. If I add the DTS Package "EmailTest" to one of my jobs as a stepto go to if the 1st step fails, nothing gets sent3. In JObs -- Notificatioin, If I set the E-maill operator to myoperator, nothing gets sentI set the Mail Profile to the Mail Profile (in SQL Server AGent'properties)However when I click Test, I get this error:Error 0: Cannot load the DLL sqlmap70.dll, or one of the DLLs itreferencesI am usingSQLServer Version 8.00.194,OS Windows 2003Help!
I'm baffled by this error but I'm guessing once someone points it out, it will a oh duh! moment. I have a proc. I want to get the results of the proc into a temp table. I've tried both SELECT INTO and INSERT INTO. Both give me the error "Invalid object name #HACK" which is the tmp table name I've used.
I'm experiencing a problem using transactions within a package, and would be grateful if anyone can help out. A search on the forum has turned up a number of similar posts but I don't think any of them deal specifically with my problem (and I didn't find an existing solution), but apologies if this is considered a duplicate!
I have two Sequence Containers in a package, each of which contains a number of Data Flow Tasks responsible for copying data from one SS2k5 database to another (on the same server). There is a precedence constraint between the two Sequence Containers (within each container the Data Flow Tasks run in parallel, although I don't think this is relevant).
I need each Sequence Container to execute transactionally i.e. within each Container the Data Flows must either all succeed or all fail. However I don't want the package as a whole to execute transactionally i.e. I don't want the two Sequence Containers within a single transaction, but rather to each start a transaction of their own. So, accordingly I have set the TransactionOption property of the package to Supported, and the TransactionOption property of each of the Sequence Containers set to Required. Each Data Flow Task has TransactionOption of Supported.
All is well when I run the package by itself, but unfortunately within my ETL this package is invoked as the child of another package, and when this happens the first sequence container fails with error message:
"The SSIS Runtime has failed to enlist the OLE DB connection in a distributed transaction with error 0x8004D00A "Unable to enlist in the transaction.""
Some quick Googling turned up the following MS Support article that seems to pretty much describe my situation and acknowledge it as a SSIS bug:
http://support.microsoft.com/?kbid=914375
However there is a bit of a problem: the article claims this problem is fixed in Service Pack 1 ... but I'm already running Service Pack 1 (Build 2047). Additionally, the alternative workaround given doesn't help me (unless I'm misunderstanding) since I don't want the two Sequence Containers running in the same transaction and so can't set their TransactionOption to Supported and rely on them joining an existing transaction.
I am aware of the post-SP1 SS hotfix but had some problems with my AS installation when I upgraded to this a while back, so I'm keen to stay with my fresh SP1 unless someone can assure me that the hotfix addresses this issue (and I can't see any mention of an issue such as this in the hotfix notes).
I guess an alternative workaround would be to use native SQL Server transactions instead of MSDTC by including explicit T-SQL transaction commands within my Sequence Containers (and RetainSameConnection on the Connection Manager), but I'm reluctant to modify my packages to do this unless necessary, since I believe the intrinsic transaction support should be able to cover what I'm trying to achieve?
Has anybody else experienced this problem even on SP1, or am I perhaps misunderstanding how to use transactions in SSIS (this is the first time I've used them)?
I've run into a problem trying to install SP2 for SQL2005 on a Server 2003 system. I tried to troubleshoot this myself but the logs are just not verbose enough. The box was just rebuilt with Server 2003, then SP2 for 2003 was immediately applied. SQL2005 was then installed. In my attempt to install SP2 for SQL2005, the following errors occured:
Summary.txt
---------------------------------------------------------------------------------- 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 : 29528 Error Description : MSP Error: 29528 The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation.
---------------------------------------------------------------------------------- Product : Analysis Services (MSSQLSERVER) Product Version (Previous): 1399 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixOLAP9_Hotfix_KB921896_sqlrun_as.msp.log Error Number : 29528 Error Description : MSP Error: 29528 The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation.
The following issue is happening a lot these days. For all the world it looks like a bug in BIDS:
I set a breakpoint in a Script Task (not a Script Component!) and the code dutifully stops on the breakpoint over and over again, as expected. (Please don't tell me about not being able to debug Script Components!)
At some point, when I run the package and hit the Script Task, the VSA editor opens as if it's going to take me to the breakpoint, but then it displays an error dialog box containing the following message:
Microsoft Visual Studio has lost its link to . You work will be exported to C:Documents and SettingsmgrohMy Documents when you quit the application
(Notice the space between "its link to" and the period in the first statement. It goes without saying that nothing is exported to My Documents.)
When I dismiss the dialog, execution resumes and the break point is ignored. In fact, breakpoints in all script tasks in the project are ignored.
Clearly, something is broken in the DTSX file, and is preventing VSA from finding the breakpoint. That's the only interpretation I can come up with for the "lost its link to" part of the message.
I have tried everything I can think of: - Deleting all breakpoints and re-establishing the breakpoint - Making a small change to the code to force VSA to re-evaluate the module - Shutting down and re-opening the project - Rebooting the computer (!!!!)
And NOTHING works. The module is just broken, and breakpoints it other Script Tasks don't work, either.
This really looks like a bug in SSIS, but I can't find anyone else who's complained of the same thing.
The following comes from SQL9_Hotfix_KB913090.log:
04/28/2006 15:13:27.843 ================================================================================ 04/28/2006 15:13:27.843 Hotfix package launched 04/28/2006 15:13:28.718 Product discovery successfully completed during the install process for MSSQLSERVER 04/28/2006 15:13:28.718 SP Level check successfully completed during the install process for MSSQLSERVER 04/28/2006 15:13:28.718 Product language check successfully completed during the install process for MSSQLSERVER 04/28/2006 15:13:28.718 Product version check successfully completed during the install process for MSSQLSERVER 04/28/2006 15:13:28.718 Command-line instance name check completed during the install process 04/28/2006 15:13:28.718 Baseline build check completed during the install process 04/28/2006 15:14:16.375 Attempting to install instance: MSSQLSERVER 04/28/2006 15:14:16.375 Attempting to install target: DEAN 04/28/2006 15:14:16.390 Attempting to check for locked files: sqlrun_sql.msp 04/28/2006 15:14:16.421 Attempting to check for locked files: \DEANd$4c016e0f5dfb4a37300a7ce503HotFixSQLFilessqlrun_sql.msp 04/28/2006 15:14:16.421 Creating MSP locked file check log at: C:WINNTHotfixSQL9LogsSQL9_Hotfix_KB913090_sqlrun_sql.msp.out 04/28/2006 15:14:27.171 MSP returned 1602: The user cancels installation. 04/28/2006 15:14:27.187 Successfully checked file: \DEANd$4c016e0f5dfb4a37300a7ce503HotFixSQLFilessqlrun_sql.msp 04/28/2006 15:14:27.187 Successfully opened registry key: SystemCurrentControlSetControlSession Manager 04/28/2006 15:14:27.187 Failed to read registry key: PendingFileRenameOperations 04/28/2006 15:14:27.187 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxmlfilt.dll 04/28/2006 15:14:27.187 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnThaWBrkr.dll 04/28/2006 15:14:27.187 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnquery.dll 04/28/2006 15:14:27.203 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnls400.dll 04/28/2006 15:14:27.203 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnlhtml.dll 04/28/2006 15:14:27.203 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsir5jp.dll 04/28/2006 15:14:27.203 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftesql.exe 04/28/2006 15:14:27.203 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftepxy.dll 04/28/2006 15:14:27.218 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftefd.exe 04/28/2006 15:14:27.218 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsfte.dll 04/28/2006 15:14:27.218 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnLangWrbk.dll 04/28/2006 15:14:27.218 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnkorwbrkr.dll 04/28/2006 15:14:27.218 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinninfosoft.dll 04/28/2006 15:14:27.218 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnFTERefFTERef.dll 04/28/2006 15:14:27.234 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnCHTBRKR.DLL 04/28/2006 15:14:27.234 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnChsBrkr.dll 04/28/2006 15:14:27.234 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COMResources1033REPLRES.rll 04/28/2006 15:14:27.234 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COM eplrec.dll 04/28/2006 15:14:27.234 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COM plisapi.dll 04/28/2006 15:14:27.234 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:WINNTassemblyGAC_32Microsoft.SqlServer.Replication9.0.242.0__89845dcd8080cc91Repl.dll 04/28/2006 15:14:27.234 Failed to read associated hotfix build information for the following file: C:WINNTassemblyGAC_MSILMicrosoft.SqlServer.DataStorage9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.DataStorage.dll 04/28/2006 15:14:27.234 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 04/28/2006 15:14:27.234 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall C:Program FilesMicrosoft SQL Server90COMqrdrsvc.exe 04/28/2006 15:14:27.234 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COMsnapshot.exe 04/28/2006 15:14:27.234 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COM eplmerg.exe 04/28/2006 15:14:27.234 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90COM ablediff.exe 04/28/2006 15:14:27.250 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COMDISTRIB.exe 04/28/2006 15:14:27.250 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnDatabaseMail90.exe 04/28/2006 15:14:27.250 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 04/28/2006 15:14:27.250 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 04/28/2006 15:14:27.250 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 04/28/2006 15:14:27.250 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 04/28/2006 15:14:27.250 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 04/28/2006 15:14:27.250 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll 04/28/2006 15:14:27.250 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll 04/28/2006 15:14:27.250 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll 04/28/2006 15:14:27.250 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn6.6.3.5 C:Program FilesMicrosoft SQL Server90Sharedmsxmlsql.dll 04/28/2006 15:14:27.265 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 04/28/2006 15:14:27.265 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll 04/28/2006 15:14:27.265 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll 04/28/2006 15:14:27.265 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll 04/28/2006 15:14:27.265 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 04/28/2006 15:14:27.265 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 04/28/2006 15:14:27.265 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 04/28/2006 15:14:27.265 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll 04/28/2006 15:14:27.265 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll 04/28/2006 15:14:27.265 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll 04/28/2006 15:14:27.281 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL 04/28/2006 15:14:27.281 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL 04/28/2006 15:14:27.281 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL 04/28/2006 15:14:27.281 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll 04/28/2006 15:14:27.281 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll 04/28/2006 15:14:27.281 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll 04/28/2006 15:14:27.281 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE 04/28/2006 15:14:27.281 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE 04/28/2006 15:14:27.296 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE 04/28/2006 15:14:27.296 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90SharedResources10339.0.2047.0 C:Program FilesMicrosoft SQL Server90Sharedmsmdrdir.dll 04/28/2006 15:14:27.296 Failed to read version information for the following file: C:Program FilesCommon FilesSystemole db2.0.3609.0 C:Program FilesCommon FilesSystemole dbxmlrw.dll 04/28/2006 15:14:27.296 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll 04/28/2006 15:14:27.312 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll 04/28/2006 15:14:27.312 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll 04/28/2006 15:14:27.312 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe 04/28/2006 15:14:27.312 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe 04/28/2006 15:14:27.312 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe 04/28/2006 15:14:27.312 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll 04/28/2006 15:14:27.328 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll 04/28/2006 15:14:27.328 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll 04/28/2006 15:14:27.328 Failed to read version information for the following file: C:Program FilesMicrosoft.NETADOMD.NET90enMicrosoft.AnalysisServices.AdomdClient.xml 04/28/2006 15:14:27.328 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft.NETADOMD.NET90Microsoft.AnalysisServices.AdomdClient.dll 04/28/2006 15:14:27.328 Failed to read associated hotfix build information for the following file: C:WINNTassemblyGAC_MSILMicrosoft.AnalysisServices.AdomdClient9.0.242.0__89845dcd8080cc91Microsoft.AnalysisServices.AdomdClient.dll 04/28/2006 15:14:27.328 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033 C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033sqlcm.xml 04/28/2006 15:14:27.328 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll 04/28/2006 15:14:27.328 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll 04/28/2006 15:14:27.343 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll 04/28/2006 15:14:27.343 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll 04/28/2006 15:14:27.343 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll 04/28/2006 15:14:27.343 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll 04/28/2006 15:14:27.343 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll 04/28/2006 15:14:27.343 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll 04/28/2006 15:14:27.343 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll 04/28/2006 15:14:27.343 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources10332005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstallsysdbupg.sql 04/28/2006 15:14:27.359 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSQLSVC90.DLL 04/28/2006 15:14:27.359 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSQLSVC90.DLL 04/28/2006 15:14:27.359 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSQLSVC90.DLL 04/28/2006 15:14:27.359 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinn2.0.3609.0 C:Program FilesMicrosoft SQL Server90ToolsBinnSQLdiag.exe 04/28/2006 15:14:27.359 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinn2005.90.2047.0 C:Program FilesMicrosoft SQL Server90Sharedsqlsvc~1.dll 04/28/2006 15:14:27.359 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll 04/28/2006 15:14:27.359 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll 04/28/2006 15:14:27.359 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll 04/28/2006 15:14:27.375 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll 04/28/2006 15:14:27.375 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll 04/28/2006 15:14:27.375 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll 04/28/2006 15:14:27.375 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll 04/28/2006 15:14:27.375 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll 04/28/2006 15:14:27.375 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll 04/28/2006 15:14:27.375 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll 04/28/2006 15:14:27.375 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll 04/28/2006 15:14:27.390 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll 04/28/2006 15:14:27.390 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90Shared2005.90.2047.0 C:Program FilesMicrosoft SQL Server90Sharedsqlsqm.exe 04/28/2006 15:14:27.390 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90Shared9.0.2047.0 C:Program FilesMicrosoft SQL Server90Shareddbghelp.dll 04/28/2006 15:14:27.390 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe 04/28/2006 15:14:27.390 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe 04/28/2006 15:14:27.390 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe 04/28/2006 15:14:27.390 Failed to read associated hotfix build information for the following file: C:WINNTassemblyGAC_MSILMicrosoft.SqlServer.Rmo9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.Rmo.dll 04/28/2006 15:14:27.390 Failed to read associated hotfix build information for the following file: C:WINNTassemblyGAC_MSILMicrosoft.AnalysisServices9.0.242.0__89845dcd8080cc91Microsoft.AnalysisServices.DLL 04/28/2006 15:14:27.390 Failed to read associated hotfix build information for the following file: C:WINNTassemblyGAC_MSILMicrosoft.DataWarehouse.Interfaces9.0.242.0__89845dcd8080cc91Microsoft.DataWarehouse.Interfaces.DLL 04/28/2006 15:14:27.406 Failed to read associated hotfix build information for the following file: C:WINNTassemblyGAC_MSILMicrosoft.SqlServer.RegSvrEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.RegSvrEnum.dll 04/28/2006 15:14:27.406 Failed to read associated hotfix build information for the following file: C:WINNTassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll 04/28/2006 15:14:27.406 Failed to read associated hotfix build information for the following file: C:WINNTassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll 04/28/2006 15:14:27.406 Failed to read associated hotfix build information for the following file: C:WINNTassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll 04/28/2006 15:14:27.406 Failed to read associated hotfix build information for the following file: C:WINNTassemblyGAC_MSILMicrosoft.SqlServer.ServiceBrokerEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.ServiceBrokerEnum.dll 04/28/2006 15:14:27.406 Failed to read associated hotfix build information for the following file: C:WINNTassemblyGAC_MSILMicrosoft.SqlServer.WmiEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.WmiEnum.dll 04/28/2006 15:14:27.406 Failed to read associated hotfix build information for the following file: C:WINNTassemblyGAC_MSILMicrosoft.SqlServer.SqlEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.SqlEnum.dll 04/28/2006 15:14:27.406 Failed to read associated hotfix build information for the following file: C:WINNTassemblyGAC_MSILMicrosoft.SqlServer.SmoEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.SmoEnum.dll 04/28/2006 15:14:27.421 Failed to read associated hotfix build information for the following file: C:WINNTassemblyGAC_MSILMicrosoft.SqlServer.Smo9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.Smo.dll 04/28/2006 15:14:27.421 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlSAC.exe 04/28/2006 15:14:27.421 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedMicrosoft.SqlSac.Public.dll 04/28/2006 15:14:27.484 Attempting to install file: sqlrun_sql.msp 04/28/2006 15:14:27.531 Attempting to install file: \DEANd$4c016e0f5dfb4a37300a7ce503HotFixSQLFilessqlrun_sql.msp 04/28/2006 15:14:27.531 Creating MSP install log file at: C:WINNTHotfixSQL9LogsSQL9_Hotfix_KB913090_sqlrun_sql.msp.log 04/28/2006 15:14:27.531 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller 04/28/2006 15:14:27.531 Failed to read registry key: Debug 04/28/2006 15:17:17.312 MSP returned 1603: A fatal error occurred during installation. 04/28/2006 15:17:17.359 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller 04/28/2006 15:17:17.359 Failed to read registry key: Debug 04/28/2006 15:17:17.359 Unable to install MSP file: \DEANd$4c016e0f5dfb4a37300a7ce503HotFixSQLFilessqlrun_sql.msp 04/28/2006 15:17:17.359 The following exception occurred: Unable to install Windows Installer MSP file Date: 04/28/2006 15:17:17.359 File: depotsqlvaultsetupmainsetupsqlsesqlsedllcopyengine.cpp Line: 856 04/28/2006 15:17:17.406 04/28/2006 15:17:17.406 Product Status Summary: 04/28/2006 15:17:17.406 Product: SQL Server Native Client 04/28/2006 15:17:17.406 SQL Server Native Client (RTM ) - Success 04/28/2006 15:17:17.421 04/28/2006 15:17:17.421 Product: Setup Support Files 04/28/2006 15:17:17.421 Setup Support Files (RTM ) - Success 04/28/2006 15:17:17.421 04/28/2006 15:17:17.421 Product: Database Services 04/28/2006 15:17:17.421 Database Services (SP1 2047 ENU) - Failure 04/28/2006 15:17:17.421 Details: Unable to install Windows Installer MSP file 04/28/2006 15:17:17.421 Analysis Services (SP1 2047 ENU) - Not Applied 04/28/2006 15:17:17.421 04/28/2006 15:17:17.421 Product: Integration Services 04/28/2006 15:17:17.437 Integration Services (SP1 2047 ENU) - Not Applied 04/28/2006 15:17:17.437 04/28/2006 15:17:17.437 Product: Client Components 04/28/2006 15:17:17.437 Client Components (SP1 2047 ENU) - Not Applied 04/28/2006 15:17:17.437 04/28/2006 15:17:17.437 Product: MSXML 6.0 Parser 04/28/2006 15:17:17.437 MSXML 6.0 Parser (RTM ) - Not Applied 04/28/2006 15:17:17.437 04/28/2006 15:17:17.437 Product: Backward Compatibility 04/28/2006 15:17:17.437 Backward Compatibility (RTM ) - Not Applied 04/28/2006 15:17:17.437 04/28/2006 15:17:17.453 Product: Microsoft SQL Server VSS Writer 04/28/2006 15:17:17.453 Microsoft SQL Server VSS Writer (RTM ) - Not Applied 04/28/2006 15:17:17.453
We have releases a shrink wrapped winforms application that uses SQL Express as its backend. The product has a fairly large take up, and consequently it is being installed on a large numbre of different machines and configurations. We seem to be having quite a common problem with the installation of SQL Express, we launch the installation from our own installation package with the following command line
We are seeing time after time that the install fails with the message "The SQL Server service failed to start."
Summary.txt points to
SQLSetupNNNN_COMPUTERNAME_SQL.log
and this in turn looks like this
<snipped>
PerfTime Start: Do_sqlScript : Mon Apr 10 14:06:07 2006 Service MSSQL$OURINSTANCENAME with parameters '-m SqlSetup -Q -qLatin1_General_BIN -T4022 -T3659 -T3610 -T4010' is being started at Mon Apr 10 14:06:07 2006 Service failed unexpectedly (1067) Error Code: 0x8007042b (1067) Windows Error Text: The process terminated unexpectedly. Source File Name: sqlsetuplibservice.cpp Compiler Timestamp: Fri Sep 16 13:20:12 2005 Function Name: sqls::Service::Start Source Line Number: 301
</snipped>
The ERRORLOG looks something like this
2006-04-10 13:55:47.07 Server Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86) Oct 14 2005 00:33:37 Copyright (c) 1988-2005 Microsoft Corporation Express Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
2006-04-10 13:55:47.07 Server (c) 2005 Microsoft Corporation. 2006-04-10 13:55:47.07 Server All rights reserved. 2006-04-10 13:55:47.07 Server Server process ID is 1732. 2006-04-10 13:55:47.07 Server Logging SQL Server messages in file 'C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG'. 2006-04-10 13:55:47.07 Server Registry startup parameters: 2006-04-10 13:55:47.07 Server -d C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmaster.mdf 2006-04-10 13:55:47.07 Server -e C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG 2006-04-10 13:55:47.07 Server -l C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmastlog.ldf 2006-04-10 13:55:47.07 Server Command Line Startup Parameters: 2006-04-10 13:55:47.07 Server -m SqlSetup 2006-04-10 13:55:47.07 Server SqlSetup 2006-04-10 13:55:47.07 Server -Q 2006-04-10 13:55:47.07 Server -q Latin1_General_BIN 2006-04-10 13:55:47.07 Server -T 4022 2006-04-10 13:55:47.07 Server -T 3659 2006-04-10 13:55:47.07 Server -T 3610 2006-04-10 13:55:47.07 Server -T 4010 2006-04-10 13:55:47.08 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required. 2006-04-10 13:55:47.08 Server Detected 2 CPUs. This is an informational message; no user action is required. 2006-04-10 13:55:47.24 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required. 2006-04-10 13:55:47.26 Server Database Mirroring Transport is disabled in the endpoint configuration. 2006-04-10 13:55:47.27 spid5s Warning ****************** 2006-04-10 13:55:47.27 spid5s SQL Server started in single-user mode. This an informational message only. No user action is required. 2006-04-10 13:55:47.27 spid5s Starting up database 'master'. 2006-04-10 13:55:47.36 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required. 2006-04-10 13:55:47.49 spid5s SQL Trace ID 1 was started by login "sa". 2006-04-10 13:55:47.54 spid5s Starting up database 'mssqlsystemresource'. 2006-04-10 13:55:47.76 spid5s Error: 15209, Severity: 16, State: 1. 2006-04-10 13:55:47.76 spid5s An error occurred during encryption. 2006-04-10 13:55:47.76 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
I can't quite understand what the problem is, has anybody got an idea?
I created an SSIS package using BIDS which refreshes one database with another, which works relatively smooth. I realized after running my package today that I need to drop all of the tables in the destination database and rebuild them with the source database tables. You would think that this would be an easy task, but as usual SSIS falls somewhat short of what DTS is capable of accomplishing. I am using the SQL transfer objects task to accomplish the data transfer, but the source database tables contain columns that are not in the destination database. So when I try to refresh the destination database I receive an error that says the columns do not exist in the source database. Is this a bug or am I missing something? Microsoft really needs to fix the bugs in SSIS. I was hoping that the bugs would've been fixed with sp2, however I am once again denied.
Does anyone have a quick sec to run down this and break it down for me what it is doing? I have some clue, but not the whole picture.... I commented where I have the most trouble.
CREATE PROCEDURE dbo.GetReviewerApptsInRange ( @sUserID char(50), @start as datetime, @end as datetime ) AS SET NOCOUNT ON; Select a.ApptKey, ' ' as TempApptKey, isnull(a.Addrkey,0) Addrkey, '' not sure what this does a.StartTime, isnull(a.EndTime,a.starttime) as EndTime, '' not sure what this does isnull(a.Subject,'') as Subject, '' not sure what this does isnull(a.Notes,'') as [Description], '' not sure what this does a.StudyType, isnull(a.ScheduleSource,'original') schedulesource, '' not sure what this does isnull(a.reviewerid,'') reviewer, a.ChangeID, isnull(a.Location,'') Location -- a.ChangeDate, -- (select count(cs.medrecactkey) '' not sure what this does -- from OdisChartScheduleStatus cs -- join OdisAppointments oa -- on cs.apptkey = oa.apptkey -- where cs.apptkey = a.apptkey) as chartcount--placeholder for assignments
FROM OdisAppointments a WHERE a.reviewerid = @sUserID and a.starttime >= @start and a.endtime <= @end
I have developed a db on a local machine (98) and would like to move it to another machine running nt 4 where it will function as a production db. I am mapped to see the other server (called "labnt"). The drive on "labnt" is partitioned, with the c drive holding programs, and the e drive designed to hold the data.
I would like to move the db (called SNB01) to the MSSQLData subdirectory on the e-drive. I have tried the following sproc to detach:
EXEC sp_detach_db 'SNB01', 'true'
And the following to reattach: EXEC sp_attach_db @dbname = 'SNB01', @filename1 = 'labntewmssqldataSNB01_Data.mdf', @filename2 = 'labntewmssqldataSNB01_log.ldf'
The above path was given me by our network admin guy.
QA gives the following error: Server: Msg 5105, Level 16, State 4, Line 1 Device activation error. The physical file name 'labntewmssqldataSNB01_Data.mdf' may be incorrect.
Overview: I am trying to automate remote admin on a db. I have a dev db where tables are added/altered etc. I need to sync the structures. So I create a text file with the templated structure and load that to a table. I then want to run a sql query to load another table with the current stucture, compare them and generate the appropriate sql (ceate table, alter table) to duplicate the structure...
I am to write a stored procedure where I load a file via Bulk Insert(ok there), then I am trying to run a query that returns a bunch of records and I am not sure how to handle the resultset. I need some pointers on how to move thru the resultset...
If someone knows of a good tutorial with this type of functionality, could you point me to it?
I am very new to SQL Server, and inherited the database administration for my company. It was setup by a very competent admin and has been fairly self-sufficient so far. I am having a problem with my main maintenance plan on my primary SQL server. The plan starts the backup of all of our databases on that server at 8pm. To complete all of the tasks in the maintenance plan is taking about 12 hours lately, spilling into the work day. The maintenance plan first makes a backup of all databases to a local RAID. Then it does the same thing to a network server, which is then copied to tape using our backup software. The maintenance plan then deletes all backup files older than 5 days. Then it Reorgs the all User DB Indexes, and Updates all User DB Stats. There are about 40 DBs total, and one of them I know for a fact is very large (> 200GB) What is best practice in this situation to make it so that all maintenance plans finish before the work day starts??
I am creating a report which consists of data in two columns. I've set the Body section to have 2 columns in it. This works fine until I start working with the report header. I do not want a page header that shows up on every page, I only want a header on the first page, a report header.
I first tried to hide the header by placing it in the Page Header section, then putting in the "page > 1" expression in the visibility property. This does what I want, except a large blank space is present at the top of my report (the header is about 1.2 "). This is unacceptable.
So my next test was to put the header into the Body section so that it only shows up in the beginning of the report. Because of this, I will need to remove the columns from the Body and make it only 1 column now. I decided to put the multi-column section into a subreport that has 2 columns and add this to the body of my report. But, this failed; the data appears in one column only. I can change the width the ensure it fits and set all other sorts of properties, nothing works.
I've researched both issues and found that these are both "bugs" in reporting services, although I cannot find thedocumented bugs.
Is there any workaround to putting a header onto only the first page of a multi-column report? Other reporting engines are able to handle this with ease, I'm suprised by Reporting Services lack of a "Report Header" section. I am an experienced .NET developer, so if there is a programmatic way through this, I am game.
OK gang here I am again. I've gotten the Packed decimals and standard 4-byte unsigned integers to work. NOW I'm stuck on 2-byte integers.
1. My file connection defines a 2 byte column of type DT_BYTES (2 bytes in and 2 bytes out) 2. My Data Conversion task is set to convert the 2 byte ByteStream to a 4 byte unsigned integer (if I try to convert to a 2 byte unsigned integer SSIS gives me a datatype conversion (not allowed) error at design-time 3. Data Conversion task throws error at run-time stating "The value could not be converted because of a potential loss of data." 4. How could I lose data going from 2 bytes TO 4 bytes ? 5. HOW do I get this value into my SQL Server int column ? 6. The HEX representation of this data looks exactly as the 4 byte column that works looks (0x00 0x01, 0x00 0x02, etc) only 2 bytes instead of 4
HELP ANYONE. I'm at my wits end with this. I've read in this newsgroup that "Microsoft won't be building data conversion utilities for every single data source know to man" (almost like we're asking for a converter for "Johns Personal DBMS"). Mainframe, COBOL, and DB2 are entrenched in many large industries with legacy systems some of us want to interface with (to make it easier for our users to get at that legacy data). Hard to do though when MS won't take the time to bridge the communications with MAJOR systems like Oracle, DB2, and COBOL. Bridging those 3 languages alone would take care of MOST of legacy interactions. This seems a bit shortsighted and unsupportive to those of us forced to deal with ancient systems.
PLEASE help me someone get past this last issue with 2 byte unsigned binary integers
I have tried to do a new SQL 2005 install via an unattended install script. I have tried both a modified version of the template.ini and just from the command line.
The installation starts and successfully installs some of the components I have selected through the ADDLOCAL option. Unfortunately it then reports an execution error and exits.
The errors I find in the install log files are as follows...
SQLSetup..._Core.log:
Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run: "C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe" finished and returned: 1603 Aborting queue processing as nested installer has completed Message pump returning: 1603
SQLSetup..._Core(Local).log
Running: InstallToolsAction.10 at: 2006/1/14 14:58:11 Error: Action "InstallToolsAction.10" threw an exception during execution. Error information reported during run: Target collection includes the local machine. Fatal Exception caught while installing package: "10" Error Code: 0x80070002 (2) Windows Error Text: The system cannot find the file specified.
Source File Name: sqlchainingsqlprereqpackagemutator.cpp Compiler Timestamp: Tue Aug 9 01:14:20 2005 Function Name: sqls::SqlPreReqPackageMutator::modifyRequest Source Line Number: 196
The files reported as failing to be added to the .cab file do not exist, although .Net 2.0 was successfully installed. All other log files do not seem to contain errors.
When calling the install from the command line I am running the following
hi all, I'm trying to run queries on relatively small tables (a few hundred thousand rows) with subqueries of counts per primary key columns as such:
(ColA in tableA is the primary key)
select * from tableA p where exists (select 1 from ( select ColA, count(1) cnt from TableA group by ColA having count(1)>1 ) t where t.ColA= p.ColA) order by some_col
my problem is that sqlserver 2005 sp5 does not materialize the internal subquery properly, or execute it beforehand and it gets confused as heck and pegs the CPUs at 100% forever.
What hints can I use to solve this issue? I've tried to use ..... "with ...." to prepare/materialize the table upfront, no luck, one version of statement pegged one cpu at 100%, while the other statement pegged ALL cpu's at 100% -- don't remember which.
My only solution right now was to create these subqueries as PHYSICAL tables -- and this would solve the problem but that would entail creating a lot of un-necessary objects.
I'm not familiar with SQL Server and am just starting things up. I have VB Express and SQL Server Express (I think - at this point, I wouldn't be surprised if I didn't), and am trying to create a database.
So how do I do that?
All I see that relates to the SQL Server 2005 is under All Programs -> Microsoft SQL Server 2005 -> Configuration Tools; I have a configuration manager, Error and Usage Reporting, and Surface Area Configuration. I assumed that in there would be a database engine in here somewhere, but I have rumaged through every command in these and found nothing on creating a new database. Nada.
Am I looking in the wrong places, did something go wrong with my install, or am I just a complete leptic?
I have a package for which I have set ProtectionLevel to DontSaveSenstive.
I connect to a SQL Database which supports mixed authentication.
To connect to this server in a flexible way, I have enabled SSIS package configuration.
I have edited my dtsconfig file with notepad and put the right password there (I am able to use management studio to connect to that database using same password).
Now when I come back to BIDS and double click on my connection manager, it doesn't read the configuration from the config file. (it just has a blank password). So it seems that BIDS doesn't read the config file.
What can I do to make BIDS read the config file.
Also, is there a way to encrypt the password (without keys) in the configuration file?
