web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Mistakenly ran a SQL s...
Microsoft Dynamics GP (Archived)

Mistakenly ran a SQL script against MASTER database - problem?

(0) ShareShare
ReportReport
Posted on by bugman 72

While attempting to resolve an issue in Dynamics GP I mistakenly ran the "smCleanupFilesBeforeLogin" script against the MASTER database in SQL 2005 Management Studio.

Yes, I got errors. (Guess I shoulda saved the results to a file, but didn't).

I then got on the right track, ran the scripts against the correct databases, & moved on, & solved my original problem.

Dynamics GP still seems to be operating fine now..... but I have backups from yesterday - I could restore the master database from them, but would that cause other issues?  Are there changes to the master database everyday by normal Dynamics operation?

Should I be worried?  Should I do anything?

Advice?......

*This post is locked for comments

I have the same question (0)
  • Victoria Yudin Profile Picture
    Victoria Yudin 22,769 on at

    To give you an answer with 100% certainty it would be helpful to know exactly what the script was that you ran and what errors you received. 

    However, in general, smCleanupFilesBeforeLogin is a stored procedure that does not exist in the master database.  So most likely, no harm done, no restore needed.

  • bugman Profile Picture
    bugman 72 on at

    The procedure I ran was one downloaded from CustomerSource - it was to recreate the CleanupFilesBeforeLogin procedure.  I did get errors, but didn't save them.  (I know..).  :-)

    Someone else advised me just as you did - that a restore was probably not necessary.  I did peek into the master database, & the CleanupFilesBeforeLogin procedure DID get created there.  I deleted it, and all seems to be fine today - Dynamics is chugging along.

    If you think there's anything else I need to do please speak up!

    Thanks!

  • Tariq Aziz. Profile Picture
    Tariq Aziz. on at

     Nothing to worry about dear.

    every master your script did not have any effect on master database. the error was generated because there was no stored procedure with the name you were trying to modify, hence no execution occured.

     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans