Category Archives: S.W.A.T.

We’ve all done this. You know you have. Here’s the problem: When scripting a Stored Procedure, you don’t save the script. You execute the script to create the stored procedure. Then you throw the script away, and execute the stored … Continue reading →

You often hear people say that SSMS is pretty good, but you still have to script some things. Here’s one of those things. I had a problem where I found (just laying about the place) some Data and Log files. … Continue reading →

I got our backup schedule back under control. Here’s what happened. And maybe there’s some useful info here for others. We do nightly FULL backups, with Hourly Differentials during business hours. The Gist: If you run out of space for … Continue reading →

I had to change a client password last week, and when I did I find out that they are one of those who think that using the Windows Minimum Password Complexity Requirements will help them be more secure. I already, … Continue reading →

In case any of you are running into this problem: If you go to attach a SQL Server database in SQL 2005 (and perhaps in 2000, not sure), and you browse to the folder or directory that has the .MDF … Continue reading →

In MS Access, a SQL Server 2008 view linked as a table, when opened offers: [Microsoft][SQL Server Native Client 10.0] Invalid Character Value for Cast Specification(#0) Upon exam, opened view in SSMS and found that the view had several columns … Continue reading →

Like many other sites, I’ve been hit by the recent spate of SQL Injection Attacks. My point here is not to go into great detail about how the exploit works, but rather to offer a relatively simple solution which, so … Continue reading →

Someone asked me the other day why I had done something in a particular way.  Here’s an example and an explanation: I had done something similar to the second example.  The two versions do exactly the same thing – it’s not a trick … Continue reading →

Dropping user from database results in:  “The database principal owns an assembly and cannot be dropped. (SQL error 15154).” I’ve seen this error, “Principal owns a schema in the database” before, and you simply change the owner of the schema … Continue reading →