CavyPrincess (12/10/2010)

---

My opinion - what needs to be "fixed" is the default option of FULL on model. There are a lot of non-DBAs supporting SQL Server. Databases are...

cengland0 (12/10/2010)

---

I thought I found the trick and it was that a space was missing. The lack of the space actually had nothing to do with the error but...

cengland0 (12/10/2010)

---

This should produce the same as (Notice no spacing between two commands):

Set @strSQL = 'Create table #tmp (id int)Insert into #tmp(id) values (1)'

I knew this had to cause...

I almost completely agree with Gail's comments.

Shrinking should not be removed. There are situations where a database has suffered exceptional growth, and there is no need to keep that space...

Well, I don't know about others, but for me this is one of the more...

Artur Komkov (12/9/2010)

---

What's why I always try to avoid nullable columns or make something like that:

select * from dbo.Employees where EmployeeID

not in...

:laugh:

If that number is significantly large, I'll have to consider postponing...

He did tell us...

Good question. But the explanation is not an explanation at all. I wrote a series of blog posts about NULLs, and one part covers (a.o.) this issue - you can...

steven.malone (12/7/2010)

---

Ummm... I think you missed where we discussed two commas in a row with no numbers

select isnumeric(',,')

-----------

1

(1...

I have to disagree.

Yes, you are right - all the examples are indeed valid string representations of a value...

SanDroid (12/6/2010)

---

Hugo Kornelis (12/6/2010)

---

2. The explanation does not mention how important it is to make ANSI_PADDING is enabled at the time the column is created. If it's not, the results...

Nils Gustav Stråbø (12/6/2010)

---

Good question, thanks!

Is it just me, or is there a bug in SQL Server when ANSI_PADDING is OFF (not that I've ever used it)?

(... snip ...)

I suspect...

Tough question, but also a good question. Well done, Ron!

Two minor issues:

1. The documentation link points to the description for SQL Server 2000. This behaviour has not been changed in...

You're doing nothing wrong. This is the expected and documented behaviour for sys.tables.

Note that this discussion is about the system stored procedure sp_tables, not about the catalog view sys.tables.