smo

How do you make SMO release it's connections? I have this code: public static class SqlServerConnectionFactory { public static Server GetSmoServer() { using (var c = new SqlConnection(ConfigurationManager.ConnectionStrings["MyConnectionString"].ConnectionString)) { var s = new ServerConnection(c); c.Close(); return new Server(s); } } public static Database GetSmoDatabase(Server server) { var db = server.Databases[ConfigurationManager.AppSettings["Database"]]; db.AutoClose = true; return db; } } Called like this from an ASP.Net MVC app run in IIS...: public ActionResult Index() { server =

What's the best method to check if SQL server exists or not? I'm trying Microsoft.SqlServer.Management.Smo.Server.PingSqlServerVersion() and it works fine if server exists and available. But it kinda pretty slow, if there is no such a server. Is there any fast enough method to check without even defining user credentials (only the server name), if a server exists? What do you recommend to use? You could just use TcpClient class to query the server and check if a specific port is open, could be something like this: using System.Net; using System.Net.Sockets; public bool CheckServerAvailablity

I have some code that uses SMO to populate a list of available SQL Servers and databases. While we no longer support SQL Server 2000, it's possible that the code could get run on a machine that SQL Server 2000 and not have the SMO library installed. I would perfer to check for SMO first and degrade the functionality gracefully instead of blowing up in the user's face. What is best way to detect whether or not SMO is available on a machine? Every example that I have seen through a quick Google scan was a variation of "look for C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies\Microsoft

My database has tables, views and all. And I need a way to generate SQL script for all the DDL in an automated manner. No need for data. There are FK constraints so table creation scripts should be ordered properly. Some views use another view, so view creation scripts also have to be ordered properly. Starting from a script presented on MSDN Blog , I got the following: function Generate-SqlScript { param( [string]$srvname, [string]$database, [string]$ScriptOutputFileName ) [System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SqlServer.SMO") | out-null $srv = New-Object ("Microsoft