Greg Larsen's Blog - All Comments

re: Save Disk Space with SQL Server 2008 DATETIME2 Data Type

Greg Larsen — Thu, 10 Jul 2008 06:02:41 GMT

Sorry it took so long to get back to you. Percision is the number of digits to the right of the decimal point, and represent fractions of seconds.

re: SQL Server 2008 Certifications

Greg Larsen — Thu, 10 Jul 2008 05:59:03 GMT

I understand the beta is an invite only. Thought I would hear more about it because I was involved in the Alpha Review but have yet to hear anything.

Greg

re: GIS Data Types in SQL Server 2008

Greg Larsen — Thu, 10 Jul 2008 05:57:06 GMT

Wish I could say I've used the GIS features in SQL Server 2008, but I haven't. At some point I will be evaluating these features, or have our GIS guy evaluate them. At that time I might have some more information for you.

Greg

re: GIS Data Types in SQL Server 2008

Sandesh — Sat, 21 Jun 2008 07:21:36 GMT

Hi Greg,

Actually i am looking for developing GIS system. But I was totally unaware about how to proceed... I just googling GIS and found your blog can you help me or can you show me the path that How to proceed???

or Can you give me some URLs where I can get related information..???

You help is appreciated.....

Thank you in advance.

From your blog I got one thing that I can use SQL Server 2008 to store my map data...

re: SQL Server 2008 Certifications

pcsql — Fri, 13 Jun 2008 01:24:57 GMT

How can I take the beta exam? Does this link www.microsoft.com/.../default.mspx apply to beta exam?

Thanks.

re: Save Disk Space with SQL Server 2008 DATETIME2 Data Type

BrianH123 — Sun, 25 May 2008 13:30:49 GMT

What is "percision"? I've never seen that word before. I know it's not a typo, since you spelled it like that seven times. Also, what does "substainal" mean. What does "now multiple that" mean?

In the event you're a smart person who just can't spell, have you considered using spell-check?

re: SQL Server Patch Management Methodology

alzdba — Mon, 19 May 2008 06:43:47 GMT

on our DBA-test instance(s) we follow CUs.

Only with instances that are being installed fresh, we apply up to our latest tested and approved CU. (currently CU5).

This implies that, for the moment, we have sql2005 instances being at different CU levels, but it also means that if an instance suffers issues, we can "rather safely" apply the latest approved CU, because we know it works on other instances. Only if that is not the case we'll go for the actual latest CU, but up till now there hasn't been a need for this.

We welcome SP3 and will test it and plan its rollout as soon as it will be available.

Johan

re: SQL Server Patch Management Methodology

zzzbla — Thu, 24 Apr 2008 14:12:45 GMT

Hi Greg,

As a rule of thumb, I upgrade SQL Servers to 9.0.3054 (SP2 + the hotfix here: www.microsoft.com/.../details.aspx)

I don't apply the cumulative updates because of the paragraph you quoted (not enough testing), but I do read about the fixes in them and I consider applying a CU that fixes an SSRS right-to-left issue - not before I try it in a test environment.

re: Is T-SQL Dead?

Greg Larsen — Sun, 06 Apr 2008 13:14:41 GMT

I agree with you regarding the security access requirements for LINQ. I like to encourage developers to only use stored procedures so we only have to give EXECUTE permissions on production tables. Having to give users CRUD permissions opens the door to adhoc updates to our data, outside of applications. What do other DBA's think about having to provide additional right beyond EXECUTE permission, just so developers can use these new features of Visual Studio that provide T-SQL code generators?

re: Is T-SQL Dead?

unclebiguns — Fri, 04 Apr 2008 20:44:06 GMT

I have spent quite a bit of time recently learning about Linq to SQL and discussing it with other SQL Server DBAs and Developers. It does replace T-SQL in .NET code with basically a T-SQL code generator. The nice thing is that is created parameterized queries. The downsides are that it discourages use of stored procedures and puts all query code in a compiled application. From a data security perspective I don't like having to grant rights directly to a table and from a tuning perspective I like to be able to tune the queries which I can't do with Linq To SQL.