Detail | Green | Rookie | Regular | Veteran | Expert | Elite |
---|---|---|---|---|---|---|
Initiative | 1 | 2 | 3 | 4 | 5 | 6 |
Observation | 6 | 8 | 10 | 12 | 14 | 16 |
Primary Wpn. Skill | 1 | 2-3 | 4-5 | 6-7 | 8-9 | 9-10 |
Avg. Stat. | 3 | 4 | 5 | 6 | 7 | 8 |
Wpn. Bonus | 45% | 55% | 65% | 70% | 75% | 80% |
Armor Bonus | 40% | 50% | 55% | 60% | 65% | 75% |
Gear Bonus | 35% | 40% | 45% | 50% | 55% | 70% |
Loyalty Base | 1 | 2 | 4 | 6 | 8 | 10 |
Loyalty Bonus | -2 | -1 | 0 | 2 | 4 | 6 |
Wednesday, April 23, 2008
NPC Skill Chart
Monday, April 14, 2008
SQL 2005 would not let me drop a database
I did some digging to see if there was a 'real' reason for this. All I could find was the the database was in use.
I found this t-sql script to help me find out why the db was in use.
I ran this t-sql and saw that I had a single SPID (51) that was connected to my database. I executed 'kill [spid]' and then tried my drop db command again. Of course it didn't work. I then ran this script repeatedly by highlighting the code ind the SQL Server Management Studio code window and pressed F5 over and over until I could see that the command to drop the db was working.
Not sure why that SPID kept reappearing. But the problem is fixed.
I found this t-sql script to help me find out why the db was in use.
USE Master
DECLARE @dbid INT
DECLARE @dbname nvarchar(40)
SET @dbname = '[your_db_name_here]'
SELECT @dbid = dbid FROM sys.sysdatabases WHERE name = @dbname
IF EXISTS (SELECT spid FROM sys.sysprocesses WHERE dbid = @dbid)
BEGIN
--RAISERROR ('The restore cannot be done', 16, 1)
SELECT 'These processes are blocking the db in question' AS Note,
spid, last_batch, [status], hostname, loginame FROM sys.sysprocesses
WHERE dbid = @dbid
END
ELSE
BEGIN
SELECT 'There were no SPIDS using the database: ' + @dbname as Note
END
I ran this t-sql and saw that I had a single SPID (51) that was connected to my database. I executed 'kill [spid]' and then tried my drop db command again. Of course it didn't work. I then ran this script repeatedly by highlighting the code ind the SQL Server Management Studio code window and pressed F5 over and over until I could see that the command to drop the db was working.
Not sure why that SPID kept reappearing. But the problem is fixed.
Subscribe to:
Posts (Atom)