Hi again,
could anyone tell me what to do about this...I'm not a dba but I do need direct access to the sql server such as scheduling new jobs (I can execute them immediately as pkgs or even run them as jobs on my machine, but to schedule I need to go to the server. The NT administrator does not like the idea of anyone else touching his server, so is there any way to circumvent the situation and do the scheduling from my workstation? Someone had mentioned creating an icon on my desktop but I'm not clear on the idea. Thanks a million. I get great help on this website.
I Scheduled a SSIS package on my Sql Server Agent, when i go to the Job History it says the Job succeded for the time it was scheduled to run, but im noticing the Job does nothing, i mean the Package is running but it's not doing what it is supossed to do. I know the Package works because when i go to the BI Studio and rightclick>Execute Package it works.
In my production server all the jobs are scheduled. but though sa user id sometimes the steps in the jobs are not visible but it is working, sometime it is visible in the sql server management studio. do i have to check any settings or change any settings.
By my customer, the jobs scheduler tool is Control-M.
I haven’t seen information about the SSISDB catalog but just the “old/classic” deployment for SSIS package on a SQL Server through msdb in the Control-M Documentation.
I writing a new achitecture concept for this customer with the SSISDB catalog.
How Control-M can work with a SSISDB architecture?
On my server running SQL7.0 with SP2, I try to backup my database to a file. All works well if I run the backup manually, but when I use the schedule option, when I close the Backup properties window and open the window again, the schedule is gone... Does anyone of you know how to get this working?
I'm having some problems debugging SQL Server stored procedures on a SQL Server 2005 server. I have installed Visual Studio 2005 on a workstation running Windows XP, now I'm trying to debug a ASP.Net web application that has some code that executes the stored procedures on a Windows 2003 Server running SQL Server 2005.
I opened VS2005 ... created a connection to the SQL Server 2005 instance ... open the Stored procedure ... right click the stored procedure name and selected Step into Stored Procedure and the following message is displayed:
Unable to start T-SQL debugging.Could not attach to SQL Server process on 'ServerName'.
Running MSSQL 2000 on Windows2000 in an NT domain. We have several jobs created by the web assistant wizard. They run along just fine for days or weeks, then all of a sudden SOME of them (?!) begin to fail with the message "Unable to perform a SETUSER to the requested username 'dbo' because the username is invalid for database 'xxx'" where xxx is of course the db where the proc resides. SQLAgent service is running as a domain admin and has not changed; job is owned by sa and has not changed; the domain admin in question is in sa role and has not changed. Something sure has changed, but what? Sometimes when this happens we can clear it up by deleting the web job and simply re-creating it. Today we have three culprits and none of our usual tricks are working. Why does this happen? How can we fix it? How can we PREVENT it! Thanks for any words of wisdom out there.
Im in the process of upgrading my sqlserver 2000 to 2005.I want to migrate all the jobs from sql2000 to 2005. I scripted the job (right click job--->all tasks--->generate sqlscript). I ran the same script on sql2005,i was getting an error like this
"Msg 515, Level 16, State 2, Procedure sp_add_job, Line 137
Cannot insert the value NULL into column 'owner_sid', table 'msdb.dbo.sysjobs'; column does not allow nulls. INSERT fails.
The statement has been terminated."
What does the error mean? cant i run the same script generated in sql2000 on sql2005. Wht is the approach to transfer the jobs from sql2000 to sql2005 ? I know ther is one more way i can transfer.It is through sqlserver business intelligence development studio and using transfer job task.But i dont want to use that.I want to script the job and execute it on sql2005.
Technically they should be able to view and modify jobs through Management Studio when being added only to SQLAgentOperatorRole. However they receive the following error when clicking on the Jobs folder regardless of the msdb role.
Our original two SQL 2005 servers do not produce this message, but all other instances do. All servers, but one, are SP2 so the service pack is not an issue. Any thoughts?
I recently installed VB6.0 Enterprise on my system. As a part of the installation is the option to install SQL Server 6.5 Development. I elected to install SQL. The install went without any glitches. Upon going into SQL Enterprise Manager, I was asked to register the server where SQL was running. My understanding was that SQL would allow me to register the name of my host system. (This is a stand alone system with VB6.0 and Sql development 6.5 installed - no network attached). SQL will not allow me to register my server's name as the host server. It says that if cannot connect to the named server. SQLSERVER and SQL EXEC services appear to be running without any problems. Anyone have any idea where I should start or what could be disallowing my connection/registeration of my server. Any help would be greatly appreciated..... Thanks... Tom
Developers wanting to access sql server developer edition on XP workstation in small office network (workgroup) will have problems using windows authentication (trusted connection) if the XP "server" machine has "simple file sharing" enabled.
Simple file sharing in XP can be disabled in control panel - folder options.
For this sneak mode to work accounts with the same user and password should exist on both "client" and "server".
Hi all!Is there any function in SQL that I can use to get current date fromworkstation? All functions which I tried (now(), getdate() etc.)returns current date from server but I need date from workstation.Regards,Mirnes Lemes
I would like to know if one can adminiter SQL server remotely using MMC on NT workstation? If so, how do you install the MMC and SQL Enterprise Manager Add-in on NT workstation?
How can I configure my workstation running WIN95 to used the SQL Enterprise Manager from the server end and other utilities. I have installed the client network utility.
Reason to use enterprise manager because I wanted to perform administrative tasks on my workstation and I've installed SQL SERVER 7.0(Standard version with 5 clients)on the WINNT 4.0 server.
Hi all;I am trying to replicate our database by using the merge replication.[color=blue]>From server side I tried to connect to the workstation. I have[/color]installed MSDE to the client machine. I can see the machine name on theSQL Server Group however I wasnt able to create the conncetion betweenthe machines. I have checked my network connection, there is no problemI can see the machine and I can connect it through the network. I triedto use Client Network Utility with Named Pipes and TCP/IP but not agood news. I couldnt achieve to connect to the machine. So couldsomeone please help me out with this problem. I am really in trouble Ihave to find out this end of this week.RegardsAs
I've got VS 2008 Pro installed, as well as SQL Sever 200 (which I must keep installed). When I run the install for SQL Server 2005 developer edition, it continually fails to install
I had a perfectly good working copy of SQL Server 2005 installed. However, at some point I needed the Report Services Designer so I could edit my reports in Visual Studio. I inserted the CD and selected the feature from the list and it installed. Only problem being that it has completely removed my Management Studio and practically every other tool I didnt explicitly checked when installing the RS Designer.
When I tried to run the same Setup again and check everything, it tells me that there is no change between what I have selected and what is installed, which sounds like total bs to me, since my pc doesnt have a management studio etc anymore.
Out of pure misery I decided to remove my entire SQL Server installation, inc Instance, hoping to start anew and achieve the result I wanted with the least amount of frustration. I ended up here and followed it all the way: http://support.microsoft.com/kb/909967
When I started reinstalling, I ran into something new. The installer refuses to let me install anything but the Workstation components, books online and development tools. All the other options are greyed out and not even available.
Someone please help me get my SQL Server back up and running because I'm getting hopeless.
It appears that there is no way to install SQL Server 2005 Workstation Components on an x86 operating system (XP in this case) if you have the x64 install disks (Standard Edition). Can someone verify this?
I am finding it hard to believe that workstation components for a standard Windows client environment are not distributed with the version of SQL Server that matches Windows 2003 x64.
I have the following connection string in my Windows app that works fine on the Server: workstation id=SCSXP;packet size=4096;integrated security=SSPI;data source=scsxp;persist security info=False;initial catalog=nala But when I use that string on a workstation, it times out. I do have a Network connection to the Server. How should I modify the connection string to work on the workstation? Thanks, Bill
I am running SQL 7 (SP3) on a 2000 Server. When I configure the server as part of the Workgroup I have no problems connecting from the workstation. However, if I join the server to our 2000 domain, I cannot connect and/or register the server from the workstation through EM.
Is this a security issue? If so, what are the minimum requirements or what else am I missing. Any suggestions would be appreciated.
I have installed SQL 6.5 client tool on to my workstation. Since then, we have upgraded to SQL 7.0 on our server. I installed SQL 7.0 client tool to my workstation and have been using it. I want to remove SQL 6.5 client tool from my workstation and do not know how. There is no uninstall button in the SQL 6.5 folder nor this program exists in Add/Remove Program in COntrol Panel. Can you help? Thank you.
Could someone please tell me what I have to set at the Server side so that I will be able to STOP and START the SQL Server using Enterprise Manager and `sa` login remotely, say from the workstation.
I have 3 NT Workstations that will not connect to my SMS database using NT Integrated Security. The SQL 6.5 server is set up to use mixed security. The only way to connect to the server is to use a standard sql account. Any ideas? THis happens to all users even administrators.