February 14, 2007 at 12:58 pm
What's the purpose of Visual Studio. Is it needed for SQL Server 2005? Why is this installed by default.
February 15, 2007 at 6:54 am
It's so you can write CLR functions - which are considerably faster, more powerful than UDF's. BOL has a load of info on it - search for CLR.
February 15, 2007 at 7:24 am
VS is also the only way we have found (there may be others but we are still searching) to save a SSIS package from the import wizard, and later execute it . (The package would complain about the wrong level of software on my client machine if I tried to run it under the SS Mgt Studio, and be unable to access the source data (on my local disk) if I tried to run it from the server.
But I could run it once I defined a solution and SSIS project in VS after connecting to the server.
Sure seems convoluted to me!
February 15, 2007 at 8:16 am
Visual Studio is now the programming interface for SQL Server, and SSMS is the administrative interface (of course, you can run queries in SSMS, and use that as the development window, as well).
As Brian said, you use VS to create CLR functions. You will also use VS BIDS (Business Intelligence Design Studio) to create and edit SSIS packages, to create and edit SSAS cubes and to create and edit SSRS reports. Basically all SQL Server development that is not purely T-SQL has to be done using VS.
You shouldn't have to execute SSIS packages in VS, they should be able to be run from a SQL Server job, you just have to get the permissions right.
February 15, 2007 at 8:19 am
Re: "You shouldn't have to execute SSIS packages in VS, they should be able to be run from a SQL Server job, you just have to get the permissions right."
I thought the only permission I was missing was a share to my local hard disk source file. (Which we are not allowed to do.) Could you define what permissions I would need?
Thanks!
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply