I want to create a package which start and stop the SQL server's services... i know i can achive this via NET COMMAND.... but i coudnt find in which task (SSIS) I can place that command?..
I also came across that I can achieve this using Execute Process task but for this I have to define executable file.... actually i dont want ne thing outside from my SSIS package
Hi All, I have some clarifications on stopping my package once cube is refreshed or processed.
Below i have given steps for the transformation in my package
Let me give you what are all the dataflow transformations that i had given in my package.
1. Data Flow Task
2. Script Task 1- I have written code for getting the last processed cube (global variable has been declared for Last processed cube date - lastProcessedCube)
3. Script Task 2 - I have written code for SS_Batch table where i can get Create_Ts date that is assigned to another global variable - create_ts.
4. Analysis Processing Task.
In between Script Task 2 and Analysis Processing Task i have given @lastProcessedCube > @create_ts for Expression and Constraint under Precedence Constraint Editor
Actually i need to run package for every 10 minutes which i can do it in Job Schedule and need to refresh or process the cube daily. Is there any way to stop the package once when my cube is processed on that day. Again start the package for the next day.... Is it possible to do this? Please let me know.
MSSQLSERVER won't restart. I can't uninstall SS7, either, because it says I have MSSEARCH running, which Task Manager can't kill (access denied, even to me the administrator). Tried changing the registry keys for MSSQL to MSSQL_old and then the install goes forward but fails at the end because some of the TEMPDB files cannot be activated. This trick worked on my Win98SE once, for the same problem. I ignorantly deleted IE4 from the server's C:drive because I needed more room to reinstall. I tried reinstalling the SS7 "components" (no apparent problem, except it detects that I have now installed IE5.5)(IE5.5 automatically installs to C:Program FilesMicrosoft or thereabouts, not C: where IE4 was, by the way). I was up to SP2 on SS7, and SP6 on NT4. The name of the server hasn't changed, but the name of the c:drive is new. Why would a new install care? I ran scandisk inbetween reboots as a caution, but the install always fails. Should I be choosing the default "allow 5 connections" rather than "5 per computer licenses"? TIA, Jeb
Help! I just took over for a new company and after logging in to one of the servers I tried to click on the Symantec Backup Exec on the desktop. It failed and said that none of the services are started, looking in my services I can not get any of the services related to sql to start. In the bottom right hand corner in the system tray I have a red dot on the sql server and it is stopped. All the event logs say that: During redoing of a logged operation in database 'master', an error occurred at log record ID (199:200:5). Typically, the specific failure is previously logged as an error in the Windows Event Log service. Restore the database from a full backup, or repair the database.
I installed a copy of SQL server 2005 on a Win 2003 machine. I connected remotely from another machine and started Sql Server Configuration manager. The MSSQLServer is stopped. So, I click to start and it failed. The error it gave me was that it time out. I am new to SQL 2005 and I thought the next step after installing was to configure. Can anyone help me please.
Straight from the sqlagent error file: (the username and login I'm providing is correct. for testing purposes only its and admin account and works on another instance)
2007-05-14 15:12:07 - ! [298] SQLServer Error: 10061, TCP Provider: No connection could be made because the target machine actively refused it. [SQLSTATE 08001] 2007-05-14 15:12:07 - ! [165] ODBC Error: 0, Login timeout expired [SQLSTATE HYT00] 2007-05-14 15:12:07 - ! [298] SQLServer Error: 10061, An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001] 2007-05-14 15:12:07 - ! [000] Unable to connect to server '(local)'; SQLServerAgent cannot start 2007-05-14 15:12:38 - ! [298] SQLServer Error: 10061, TCP Provider: No connection could be made because the target machine actively refused it. [SQLSTATE 08001] 2007-05-14 15:12:38 - ! [165] ODBC Error: 0, Login timeout expired [SQLSTATE HYT00] 2007-05-14 15:12:38 - ! [298] SQLServer Error: 10061, An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001] 2007-05-14 15:12:38 - ! [382] Logon to server '(local)' failed (DisableAgentXPs) 2007-05-14 15:12:39 - ? [098] SQLServerAgent terminated (normally)
I have a SSIS package which copies data from Excel file to the database. As soon as the file is copied to a specific location on the file system I insert an entry in the database table, which should kick off the above mentioned SSIS package.
I tried to read on WMI Event Watcher Task to do the above thing. I am not sure that I can do something like that.
I have a Stored Procedure preparing data, which then are exported (flat files) using 2 SSIS packages. What is the best way to execute those 2 SSIS packages (sp,job, other) ?
This is a repeat listing - third time - of this problem.
Here's the deal: If I turn on logging on an SSIS package in Development Studio, when the package executes it will log all the events I choose to the sysdtslog90 table in the MSDB database - INCLUDING the PACKAGESTART and PACKAGEEND events.
When I create my own custom logging, however, those two events ARE NOT being logged, even though I explicitly state in my script I want those two logged. Everything else in the script (OnWarning, OnPreExecute, OnPostExecute, etc.) is being logged.
In my reading, it states that the PACKAGESTART and PACKAGEEND events are defaults and are always logged and cannot be excluded.
If this is the case, can someone explain why they aren't getting logged?
I've seen other people have run across the same issue...
I tried to apply the SP2 on a newly installed SQL Server 2005 Developer edition. The installation failed and the MSSQLSERVER service does not start. I work on 32 bits Windows Server 2003 Standard Edition SP1 with all the patches up to date. I downloaded SQL Server 2005 SP2 on March 15, 2007.
Here are the error messages from 2 of the log files:
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 : 29534 Error Description : MSP Error: 29534 Service 'MSSQLSERVER' could not be started. Verify that you have sufficient privileges to start system services. The error code is (-2146885628) Cannot find object or property.
SQL9_Hotfix_KB921896_sqlrun_sql.msp.log:
Doing Action: ComponentUpgradeInstall PerfTime Start: ComponentUpgradeInstall : Sun Mar 18 17:37:33 2007 <Func Name='ComponentUpgradeInstall'> <Func Name='ComponentUpgrade'> Failed to add file 'C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG' to datastore in AddFileToFailureHandling Service MSSQLSERVER with parameters '-r' is being started at Sun Mar 18 17:37:33 2007 Failed to start service MSSQLSERVER. Error code 2148081668 Service failed unexpectedly (2148081668) Error Code: -2146885628 Windows Error Text: Cannot find object or property. Source File Name: sqlsetuplibservice.cpp Compiler Timestamp: Wed Jun 14 16:29:04 2006 Function Name: sqls::Service::Start Source Line Number: 301
And below you can see the content of the SQL error log:
2007-03-18 19:46:11.51 Server Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86) Feb 9 2007 22:47:07 Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
2007-03-18 19:46:11.51 Server (c) 2005 Microsoft Corporation. 2007-03-18 19:46:11.51 Server All rights reserved. 2007-03-18 19:46:11.53 Server Server process ID is 796. 2007-03-18 19:46:11.53 Server Authentication mode is WINDOWS-ONLY. 2007-03-18 19:46:11.53 Server Logging SQL Server messages in file 'C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG'. 2007-03-18 19:46:11.53 Server This instance of SQL Server last reported using a process ID of 712 at 3/18/2007 5:39:48 PM (local) 3/18/2007 3:39:48 PM (UTC). This is an informational message only; no user action is required. 2007-03-18 19:46:11.53 Server Registry startup parameters: 2007-03-18 19:46:11.53 Server -d C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmaster.mdf 2007-03-18 19:46:11.53 Server -e C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG 2007-03-18 19:46:11.53 Server -l C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmastlog.ldf 2007-03-18 19:46:11.56 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required. 2007-03-18 19:46:11.56 Server Detected 2 CPUs. This is an informational message; no user action is required. 2007-03-18 19:46:11.87 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. 2007-03-18 19:46:11.98 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required. 2007-03-18 19:46:14.06 Server Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required. 2007-03-18 19:46:14.06 Server Database mirroring has been enabled on this instance of SQL Server. 2007-03-18 19:46:14.07 spid5s Starting up database 'master'. 2007-03-18 19:46:14.15 spid5s 1 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required. 2007-03-18 19:46:14.17 spid5s 0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required. 2007-03-18 19:46:14.17 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required. 2007-03-18 19:46:14.37 spid5s SQL Trace ID 1 was started by login "sa". 2007-03-18 19:46:14.42 spid5s Starting up database 'mssqlsystemresource'. 2007-03-18 19:46:14.50 spid5s The resource database build version is 9.00.3042. This is an informational message only. No user action is required. 2007-03-18 19:46:14.89 spid5s Server name is 'YODA'. This is an informational message only. No user action is required. 2007-03-18 19:46:14.89 spid9s Starting up database 'model'. 2007-03-18 19:46:15.06 spid9s Clearing tempdb database. 2007-03-18 19:46:15.67 spid9s Starting up database 'tempdb'. 2007-03-18 19:46:15.79 spid12s The Service Broker protocol transport is disabled or not configured. 2007-03-18 19:46:15.79 spid12s The Database Mirroring protocol transport is disabled or not configured. 2007-03-18 19:46:15.82 spid12s Service Broker manager has started. 2007-03-18 19:46:21.62 Server The server could not load the certificate it needs to initiate an SSL connection. It returned the following error: 0x8009030d. Check certificates to make sure they are valid. 2007-03-18 19:46:21.62 Server Error: 17190, Severity: 16, State: 1. 2007-03-18 19:46:21.62 Server FallBack certificate initialization failed with error code: 1. 2007-03-18 19:46:21.62 Server Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate. 2007-03-18 19:46:21.64 Server Error: 17182, Severity: 16, State: 1. 2007-03-18 19:46:21.64 Server TDSSNIClient initialization failed with error 0x80092004, status code 0x80. 2007-03-18 19:46:21.64 Server Error: 17182, Severity: 16, State: 1. 2007-03-18 19:46:21.64 Server TDSSNIClient initialization failed with error 0x80092004, status code 0x1. 2007-03-18 19:46:21.64 Server Error: 17826, Severity: 18, State: 3. 2007-03-18 19:46:21.64 Server Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log. 2007-03-18 19:46:21.64 Server Error: 17120, Severity: 16, State: 1. 2007-03-18 19:46:21.64 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
I'm trying to gather information from within a SSIS package for benchmarking, reconciliation, and reporting purposes in regards to cube processing, which I'm initiating using the AS processing task.
What is the easiest way to capture this information?
The only way I've been able to come up with is to use a profiler trace. If this is really the only way, what is the easiest way to execute and read the trace from within SSIS?
Also, if a script task has to be used, does anyone have a code sample?
Can't an SSIS package run "in the background", so to speak, without having either the cmd.exe or dtexecui windows open while executing? I'd obviously rather not have to have a window open when the thing is running right?
I have installed sqlserver 2005 using the standard msdn universal installation discs on my laptop running vista business.
The mssqlserver service will not start automatically as the setup configures it and I cannot start the service manually because I get the 'Access Denied' error message
I am logged on the the computer with adminstration privileges
I have quick question. Ihave a job which consists of 9 steps. 9th step is: Exec xp_cmdshell 'c:mssql.bat'. in this batch file I am stopping and starting SQL services using net stop and net start command. This job is running perfectly but it is not giving the job history when I right click the job and view job history I can't see anything where as if I check the checkbox for Show step details it showing first 8 steps information but it is not showing 9th step information. Even I checked the Sysjobhistory system table in MSDB it shows only 8 steps information. What is the reason....
New here:) and hoping someone might be able to shed a little light on a problem I am having.
I have a job scheduled, which needs to be periodically stopped and then restarted. After looking through various places I think the start method and stop method are the best bets?:rolleyes: But not really sure to be honest.
Can anyone give me some tips/pointers/opinions on what would be the best way to do this. (have tried to setup a job with the said method in each step - but it doesn't like my syntax.
Is there any way to schedule stop and start of NT services at a particular time daily.
For eg: If i have a service by name TemServer and if i need to stop that service each night at 9:00 and restart as soon as it stops.??
And Is there any way to start and stop the services of NT from workstation. Each and every time i am going to the server room for stopping the service and restarting.
how i can do it?Under Xp/2000, i write a application that stop/start this serices, butunder Win98, how i do it?Exists a method via SqlServer or a dos command to stop/start the MSDEprogram?Thanks a lotTomas--Questa è una firma automatica di MesNews.Sito: http://mesnews.no-ip.com
What is impact, if i stop and start Synchronization, for one subscription.
When i start, will it resync all tables by dropping and recreating at subscription.
On Publisher,  from Location Publiction,   right click on subscription,       select View Synchronization Status,  From here, stop and start
Profiler was run against a database looking for "long running" queries. I used the Duration column to filter out the queries that I didn't want. When reviewing the output, I noticed that for some queries the StartTime was equal to the EndTime even though the Duration was set higher. My question is, "What can account for this discrepancy and what inferences should I draw about the difference?" Does the difference represent a resouce being locked or some other type of blocking (Duration) and once the query was allowed to run, it completed quickly? TIA
======================================= If Tyranny and Oppression come to this land, it will be in the guise of fighting a foreign enemy. -James Madison, fourth US president (1751-1836)
I want to tell to user about SQL Server Configuration Manager and wants to allow him "START / PAUSE / STOP" for SQL Server Express in system Tray. It is easy for the end user who don't know SQL Server.
A few service stop/start/restart questions on SQL Server 2005 SP2, whichI'll call SQLS.It looks as if there are *potentially* 6 ways to start/stop SQLSServices like the engine itself, integration services, reportingservice, Agent..-SQLS Configuration Manager-SQLS Surface Area Configuration (for Services and Connections)-Mgmt Studio Local (on server)-Mgmt Studio Remote (on client)-Windows Control Panel->Admin Tools->Services-Command Prompt (ala net start MSSQLSERVER)By policy, I am /not/ Administrator on the server. But I am SysAdminrole in SQLS. I have had various levels of success starting/stoppingservices in the ways listed above. In some I get Access denied, and inothers I get no msg and it simply doesn't work.Is there some special non-Admin OS group I need to be in to start/stopservices? Is this handled differently in the different interfaceslisted above?It seems like my best success for starting/stopping the engine and Agentis in /local/ Mgmt Studio, but /not/ remote Mgmt Studio - the optionsare greyed out on a remote client. Is this by design? Is it a SQLSbug?I'm sure I'm not the only SQLS DBA who does not have Admin rights on hisserver who wants to start/stop services. Generally speaking, how isthis intended to work?Any help appreciated.Allen JantzenA freshly minted DQLS DBA
Hi I have upgraded my local to sql server 2005, but still need to access the remote instance which is still at version 2008/8.0. Enterprise Manager has been removed (by the SQL server 2005 installation) Does anyone know how I can restart older version of SQL server instance (ie 2000/8.0) using SQL server Management Studio?
I don't have admin access on the server which the sql remote instance is hosted. Can get around it by asking the sys admin guy to do it for now but would prefer to continue to be able to do it myself. SQL Server Configuration Manager can only manage SQL server 2005 versions - a nice little caveat!
Is there a way to stop/start remote services using 'net stop/start'? - without having to write code.... I'll continue to search for a solution, but if someon can point me in the right direction, I'd be most greatful.
I'm getting this error message when I upgraded the SQL Server to install SSIS and other components.
===================================
The service did not respond to the start or control request in a timely fashion, you need administrator privileges to be able to start/stop this service. (SQLSAC)
------------------------------ Program Location:
at Microsoft.SqlSac.MainPanel.ServiceProgressBar.RefreshService()
For some reason the status lights in my Enterprise manager are no longer working. I am connected to the databases, but because the indicator lights are not working, I can`t get a quick visual status of my servers. Any way to get my lights back on?
I have a question about granting enough rights to allow a non admin user to start and stop a sql server service via the SQL Server Management Studio by right clicking on the server node.
I have changed the acl's of the SQL Server service security and gave the user rights to start and stop the service. This does allow them to connect remotly to the server using computer manager and they successifully start and stop the service. But, in SQL Server Management Studio the option still does not show up, unless he is a admin of the server.
Does anyone know what other security settings I need to address for the start and stop to show up when I right click on the server node?
