How to schedule a SQL Server 2014 job without the Agent or T-SQL ? Is it possible using stored procedures? I need to schedule a weekly job on SQL Server 2014. I know how to do it using a batch file in Windows, if there are any other ways please let me know. Thanks in advance !
This is old, but I'm looking for something similar, and recently came across a solution that discusses using the SQL Server Service Broker to accomplish this.
These two posts from SQLTeam -- Scheduling Jobs in SQL Server Express and Scheduling Jobs in SQL Server Express - Part 2 -- are written with SQL Server 2005 Express in mind, and they discuss how to use BEGIN CONVERSATION TIMER to set up scheduled tasks without using a SQL Server Agent.
That all being said, in this particular case, another couple of options come to mind:
If you know how to do it using batch files in windows, then you could consider just using the Windows Task Scheduler with SQLCMD.
Based on your comment that they have SQL [...] Enterprise Edition (64-bit), I believe that they do have SQL Server Agent, and they just need to add your account to the SQLAgentUserRole.
Related
I just begin programming applications, and I need to install a demo of my software. But I read on internet that if I install a software using MySQL, I have obligation to give my source code except if I pay annual licence.(contacted Oracle support 3 months ago, but never got answer).
That's why I decided to transfer database on SQL Server, but now I meet that problem to install it on client's server, any advise about it also would be welcome. Thanks
I have a database in MySQL, and I would like to copy it on Microsoft Server 2017 through MS Server Migration.
On my local computer it works perfectly, but when I try to do it on the server, I have the following warning : SQL Server is not running. You must start SQL Server Agent to use Server-side data migration engine.
When I check services, I see in fact that no agent is running.
Looking on internet, I read that on SQL Express there is no Agent service, and I need to buy SQL Server Entreprise?
you can use data migration Free BI tools like pentaho PDI
By using this you can easily migrate data from MSSQL to MYsql
Hey anyone know how to take automatic backup of a SQL Server database once a day (or it may be daily or periodic bases)?
If you know any configuration of SQL Server then please tell me.
Or you may have solution by using a C# / .NET Windows application, then please also tell me.
Created a scheduled job, and look at the following to create the backup http://www.sqlexamples.info/SQL/tsql_backup_database.htm.
It makes use of BACKUP DATABASE #db_name TO DISK = #fileName;
Sure, it's quite easy!
Use SQL Server Agent. From SSMS go to "SQL Server Agent". Expand "Jobs", right click and select "New job". Go to "Steps" and add "New" step. Write your T-SQL code for SQL backup.
Go to "Schedules" and create new job "Schedule".
Finally, check if your agent has been started.
EDIT: You can also use "Maintenance Plan Wizard" from "Management" group, it's even easier because Wizard should generate (almost) all of the code for you and set up the Agent job.
You could use a third-party products though. Check this opensource backup windows service MFSQLBackupService, it did a great job for me.
I'm looking for some advice over the best way to transfer data from a local MSSQL DB to a remote MYSQL database every 5 mins?
At the moment I am using a tool called SQLYOG which allows me to create a connection to my local MSSQL database and to my remote MYSQL server and set up some queries and mapping.
It also allows me to create a windows scheduled task which runs every 5 minutes.
This solution has been working ok but is only about 95% reliable and seems to struggle sometimes.
This software runs in GUI mode and via cmd prompt so is reasonably light weight when running a scheduled task.
Does anyone know of any other light weight tools or methods I can use to get the same outcome?
You can use SymmetricDS. its a good & efficient open source tool for this purpose.
you can use SSIS packages to do that.
SQL Server Integration Services (SSIS) is a component of the Microsoft SQL Server database software that can be used to perform a broad range of data migration tasks.
Couple of options:
1. create linked server to mysql then copy rows via linked server in sp, set sql job to execute.
2. build ssis package and run it in sql job.
What I feel is the best soultion for this is to design an ETL job using either SSIS or Talen Open Studio.
I am coming from a SQL server 2008 background. I have a mysql local server running, and I wanted to set up some scheduled jobs via the sql agent. I have found some sketchy third party sql agents for mysql but none built in. Is there a sql agent or a recommended one for mysql? Thank you.
Usual approach is to set up a cron job to run a script. I used to use Perl for the scripts, but bash etc will do it as well.
Our company is getting ready to move next week and we currently use SQL Server 2000 for all our databases, hosted in our own building. They've decided to move the data to a local company for several reasons, but they are running SQL Server 2008.
I'd like advice on a few things:
We are trying to setup a test for just a few of our databases to see what breaks with our apps (connection strings, etc.). What is the best way to get a database from our SQL Server 2000 box to the new box without losing data or having to recreate the table, etc. I tried the DB Copy Wizard but restrictions within our network don't allow it. If I create a DB on SQL Server 2008 and perform a RESTORE from the SQL Server 2000 .bak file, I will lose all the transactions, correct? What if I replace the transaction files later? I'm thinking that won't work though.
How to properly upgrade a SQL Server 2000 database to SQL Server 2008? I've run the wizard against most of our databases and it came up clean with the exception of a few minor issues that I can resolve.
Our SQL Server 2000 is our production server so it can't go down at any point to copy files.... not until the move. Our customers have been notified that there will be a short outage period between certain dates so that's ok, but I guess what I'm saying is I can't stop the SQL Server Agent right now just to copy log files and such for testing purposes.
Any help/advice is greatly appreciated!
Create a database backup of the SQL Server 2000 and restore it to the SQL Server 2008.
Setup replication making the SQL Server 2000 as the Publisher and the SQL Server 2008 as the Subscriber.
Not sure which would be the best approach. I think a DB backup and restore would be a good idea. You will loose some data in the mean time, though.
If you were migrating between 2 versions of 2005 or 2008 I would advise a log backup to reduce the data lost but I don't think that this option is available on 2000
One piece of advice I can give you is to take a look at the discontinued features from 2000 and 2005 and from 2005 and 2008 on these links:
2005
2008
Just back up 2000, and then restore it. You won't lose transactions, no difefrent to doing a full backup on your current server.
You'll need to add any SQl logins and set the permissions etc.
You'll need to to do fix users for them as well.
If you only use integrated access then you don't need to.
e.g.
Use MyDataBase
EXEC sp_change_users_login Auto_Fix, 'MyUser'
And you'll need to set the compatibility level
Use
exec sp_bcp_dbcmptlevel 'model'
to get it
and then
EXEC sp_dbcmptlevel 'MyDatabase', ??
to set it.
Another option, would be to install 2000 on your new machine restore a back from the old one and then do an inplace upgrade through the 2008 installation wizard. That sort of thing tends to give my sphincters palpitations though.