I have question,why sql servers which are same version. But one doesn't have problem as below, another one has problem.

I just do T-SQL dbcc shrinkdatabase and error display

File ID 1 of database ID 7 cannot be shrunk as it is either being shrunk by another process or is empty.


I checked problem on internet, there is a report to be bug. Does it apply for all builds which are same service pack?

Why there are many builds?

When building a large and complex piece of software like SQL Server, the odds of including every feature that will ever be needed and not including any bugs or security issues is very small. Human beings aren't perfect. Customers rarely specify every feature that they will ever want or need on the first try. Such is the nature of humanity.

ITIL works on the assumption that these kinds of projects will be "built" or compiled many, many times. In order to bring some sanity to the build process, each important part gets a "build number" that changes at least each time the program is edited, and more often each time the final product is "built" (compiled/linked/etc). These build numbers describe (by a sequence number or date) when the code was built.

Throughout the code/test/release cycle, some builds finally make it all the way through the process to consumers. These are either product releases, service packs, hot fixes, etc.

Tracking the build numbers is a small step to maintaining sanity when dealing with large projects.

Going back to your original problem, you can't start a second shrink while one is still working. Doing so would corrupt your database. Apparently one of the servers that you are using can rebuild much faster than the other. Odds are good that the database on the server that seems faster is much smaller than the database on the other server, so the rebuild takes very little time on the small database compared to how long it takes on the larger database.

-PatP

what is ITIL?

Sorry, I guess that I should have provided a link for ITIL.

-PatP

thanks, i could have searched for it, i guess, but that isn't always fruitful, as many TLAs and FLAs have multiple meanings

i had honestly never heard of ITIL before -- is that, like, a fifty-cent term for documentation?

ITIL is definitely at least a seventy eight cent term!

The concept is huge, it spans everything from code creation all the way through decomissioning. ITIL focuses more on process than on mechanics, so it doesn't really care how you do version control or manage application security, but it enumerates all of the processes that you ought to have and if you go deep enough into the ITIL process it also gives you ways to quantify compliance.

I'm not big on the "digitial jihad" concepts where everything has to be done using specific tools or methodologies because I have to deal with so many different platforms. ITIL is the only process that I've found that applies to FORTH based handhelds, zOS Mainframes, Windows Servers, *nix boxes, etc.

-PatP

I thought the use of the acronym FLA was deprecated in favor of ETLA (Extended TLA)...