Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m working on a project that leverages database metadata. To date I’ve just queried the database catalog views (e.g. sys.tables) but I know this will be “easier” with SMO if I’m willing to add the dependency.
What are the advantages to SMO over metadata queries? Any “gotchas” (e.g. needing to have additional SQL libraries on my local machine just for the luxury of SMO).
sys.tables and others are not guaranteed to stay unchanged between different versions of SQL Server so next version might break your code. SMO will be updated with next version of SQL Server and the interfaces should not change so SMO is the more robust solution.