2nd - Restore from a backup (if you happened to have one available).You could also check the names of the tables on AdventureWorks when you finish installing it properly to be sure that you only drop the correspondent ones from master database. SELECT name, type_desc, create_date, is_ms_shipped If you connect to the master database and query sys.objects, you should be able to list all the tables you created: USE master But don't drop objects from the subfolders. If you didn't install any kind of third party software or scripts on your SQL Server 2017 Dev, you can drop all those user tables from the Tables folder with no worry of breaking something. You only added some user tables to the master database, therefore no harm would come if you just dropped them. It's probably the case that one of your attempts ended up with you executing the create table commands when connected to the master database (which is probably the default database for the user you're logging in with - I've been there myself, not a good practice though).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |