One way to achieve this is to either simply maintain your database tables, procedures etc as 'CREATE' scripts from day one, and devise a master script that will pull all of the individual scripts together for deployment to a database of your choosing.Ī more sophisticated solution is to use something like Visual Studio Database Edition (Probably too pricey, if your comments are anything to go by) which allows you to treat each database object as a node in a project, whilst still allowing the whole thing to be deployed with a few clicks. In addition to the above answers, I'd like to suggest that (for future projects, at least) you don't have you master database design in the database itself.
![redgate sql prompt alternative redgate sql prompt alternative](https://i.ytimg.com/vi/ZXSHlnnLjEM/maxresdefault.jpg)
SQL 2005's Management studio may handle the objects as well, but the database is in an environment where there is no way for me to connect an installation of Management Studio to it. I end up with a script that contains a CREATE DATABASE command, and creates none of the objects - the tables, the constraints, etc. When I select the option to generate a create script on a database. I'm looking for something better than this manual solutionĪdditional Update Unless I'm completely missing something, this is not a viable solution using the SQL 2000 tools. Update: The database I'm working with has 200+ tables and several foreign-key relationships and constraints, so manually scripting each table and pasting together the script is not a viable option.
Redgate sql prompt alternative .exe#
exe (no installation required) tools, tips, or T-SQL tricks would be much appreciated. I can't afford RedGate, but I really would like to have a database with identical schema on another server.Īny suggestions? Any simple. I am working in an environment that has SQL Server 2000 installed, and I am unable to install the 2005 client tools (in the event that they would help).
![redgate sql prompt alternative redgate sql prompt alternative](https://img.yumpu.com/16993749/1/500x640/sql-server-team-based-development-red-gate-software.jpg)
In essence, I want to end up with a big create script that captures the database schema.
![redgate sql prompt alternative redgate sql prompt alternative](https://silentpowerful480.weebly.com/uploads/1/2/3/9/123994415/938887974.png)
I'm in a situation where I would to generate a script for a database that I could run on another server and get a database identical to the original one, but without any of the data.