Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2008 Forums
 SQL Server Administration (2008)
 SQL tool recomendation

Author  Topic 

majd
Starting Member

1 Post

Posted - 2011-05-16 : 08:36:08
Hi all,

I am searching for a great SQL tool that runs good with SQL server 2008. We will begin working with SQL server 2008 very soon.

Can you please recommend me any good tool? I am using WinSQL today but I am not that satisfied with the scheduling and mail function. I need a good tool that can schedule and email results of a query in several file types, like xls, cvs etc.

Another thing I am looking for in a tool is the possibility to schedule a job that creates a new table from an existing and assigns a table name to the new table that is 'tablename' + the current date. So if I have a table named test and the job would run today the new table would be named test110516. Do anyone know any tool that can handle this? I know that it is possible to do this by scripting a function or something like that but the tables that we want to run this job on has many rows and I think a regular create table script will take very long time.

So can anyone recommend me a good SQL tool? It does not have to be a free of charge tool.

Thanks
/ Majd

robvolk
Most Valuable Yak

15732 Posts

Posted - 2011-05-16 : 10:50:07
What specifically don't you like about Management Studio or SQL Agent? As far as scheduling jobs, to my knowledge all the third-party tools will still use SQL Agent.

Database mail is perfectly adequate for sending query results, although it does not support Excel natively, it can send CSV files that Excel can open. It's NOT designed for high-volume email though. Reporting Services can export to Excel format and email subscriptions can be used, but it sounds like overkill for what you described.

You last request can be done as follows:
declare @sql varchar(max)
set @sql='SELECT * INTO tablename' + CONVERT(char(8),getdate(),112) + ' FROM tablename'
exec(@sql)
But be advised this is a very bad practice. Better to have a single archive table with an additional ArchiveDate column that has the date inserted.
Go to Top of Page

X002548
Not Just a Number

15586 Posts

Posted - 2011-05-16 : 10:52:47
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=56ad557c-03e6-4369-9c1d-e81b33d8026b



Brett

8-)

Hint: Want your questions answered fast? Follow the direction in this link
http://weblogs.sqlteam.com/brettk/archive/2005/05/25/5276.aspx


Want to help yourself?

http://msdn.microsoft.com/en-us/library/ms130214.aspx

http://weblogs.sqlteam.com/brettk/

http://brettkaiser.blogspot.com/


Go to Top of Page

jackv
Master Smack Fu Yak Hacker

2179 Posts

Posted - 2011-05-16 : 15:46:04
As well as agreeing with SSMS , there are other options - DIY. For example , you could use Powershell and a third party scheduler to connect and execute scripts on a SQL Server instance.This has it's advantages\disadvantages - but it does allow flexibility. If you are looking to execute DML , then some sort of t-sql will be necessary. As to how you manage the workflow - this will depend on your (or organisations) skillset

Jack Vamvas
--------------------
http://www.sqlserver-dba.com
Go to Top of Page
   

- Advertisement -