Fatal Error 615
log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Database Administrators Questions Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top db_owner unable to drop database - Error 615, SQL Server up vote 6 down vote favorite I have a SQL Server 2012 database running on amazon EC2. I've created a user to be able to create, edit and drop databases. I gave the new user with dbcreator server role. My user can connect remotely and successfully runs the create database foo; command. But when the user attempts to drop the database again with drop database foo; the command fails with the following error: Warning: Fatal error 615 occurred at Feb 1 2014 5:15PM. Note the error and time, and contact your system administrator. ErrorCode: 21 Even though the selected database is master (so I don't think it's because it's in use). And the command succeeds when I run it again logged in as an administrative user. I checked the newly created database, and my user has been assigned the db_owner role in the database as I expected so my understanding is that this should be sufficient permissions for that user to be able to drop the database they just created. According to http://technet.microsoft.com/en-us/library/ms178613.aspx the db_owner role should be sufficient permissions. "Requires the CONTROL permission on the database, or ALTER ANY DATABASE permission, or membership in the db_owner fixed database role." I've looked up error 615 and found "Could not find database table ID %d, name '%.*ls'." which makes no sense t
our previous solution, Caylx Point, is being phased out and replaced for the bank's Mortgage Division. Complete Hotel IT infrastruture Existing hotel resort has been torn and retrofitted with all the latest available technologies. Nearly all services are now requiring IP communication as a backbone. Door, Lights, Airconditioning, TV, Phones, Walkie Talkie alternativesetc Data Requests I have been in charge of producing data for Spiceworks' internal and external use. These data requests have included pulling statistics for State of IT reports, for blog posts, and more. TECHNOLOGY IN THIS http://dba.stackexchange.com/questions/58137/db-owner-unable-to-drop-database-error-615-sql-server DISCUSSION Microsoft SQL Server 2012 Join the Community! Creating your account only takes a few minutes. Join Now I'm new to SQL, and I've been working through the fantastic 'Joes2Pros Vol 1 SQL Queries' tutorial book and finally got myself stuck in Chapter 10 (just 2 chapters to go!). With SQL Express 2012 SP2 on my Win7 laptop, I created a new SQL user "Sara", granted https://community.spiceworks.com/topic/604682-fatal-error-615-with-drop her control server access, set the server to allow SQL logins, and quit SSMS. I re-opened SSMS, logged in as Sara, and created a new database called dbSara. I then tried to drop dbSara, and got Fatal Error 615. Technet shows #615 is "Could not find database table ID %d, name '%.*ls'." Symbol Meaning%d, %ld, or %DDecimal integer%xHexadecimal number%ls or %.*lsCharacter stringThe funny thing is this is an empty db with no tables. I can drop it just fine when I'm logged in as a Windows user.Sara is the db owner. When I look under login properties, she has 'public' server role checked off only. Under Securables, there are two entries (rows) for Connect SQL and Control server. Is this normal?Sara has Connect SQL and Control Server granted, for the 2nd row of each. My login (sa) has the 2nd row of Connect SQL checked, for what that's worth
Service Pack 1, I ran against this error: Drop database [snapshotDbName] Msg 21, Level 21, State 1, Line 1 Warning: Fatal http://schoennie.blogspot.com/2015/06/error-removing-sql-snapshots.html error 615 occurred at Jun 11 2015 2:51PM. Note the error and time, and contact your system administrator. Or via the interface: I knew I had enough rights because I was using the same account that created the snapshots. After trying setting the snapshot-parent-db to single user, etc. etc. I ran into this solution: alter database [YourDBName] fatal error set emergency The result will be: Msg 5093, Level 16, State 1, Line 1 The operation cannot be performed on a database snapshot. Msg 5069, Level 16, State 1, Line 1 ALTER DATABASE statement failed. BUT, now you ARE able to delete the snapshot using the UI or: drop database [bwdba_SS] Don't know why but .. it fatal error 615 works because of the (emergency) herbs :) Posted by Jeroen Schoenmakers at 6:03 AM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Newer Post Older Post Home Subscribe to: Post Comments (Atom) Blog Archive ► 2016 (1) ► October (1) ▼ 2015 (1) ▼ June (1) Error removing SQL SnapShots ► 2014 (7) ► August (1) ► June (3) ► May (1) ► January (2) ► 2013 (15) ► October (3) ► September (4) ► July (1) ► June (1) ► May (1) ► April (3) ► January (2) ► 2012 (7) ► October (3) ► August (1) ► July (3) ► 2011 (7) ► October (3) ► May (3) ► January (1) ► 2010 (7) ► November (4) ► October (1) ► March (2) ► 2009 (2) ► June (1) ► May (1) ► 2008 (3) ► July (1) ► April (2) ► 2007 (2) ► March (1) ► February (1) ► 2006 (4) ► November (1) ► October (3) About Me Jeroen Schoenmakers In no particular order: Sou