SQL Programmability & API Development Team Blog - All Comments

re: Using time zone data in SQL Server 2008

RohitGarg — Wed, 25 Jul 2012 22:11:02 GMT

It helps in dealing with diffrent zone datetime requirment but universal standard in very much needed.

re: SQL Server 2005 / 2008 table partitioning : Important things to consider when switching-out partitions.

Nenea Nelu — Wed, 01 Feb 2012 16:39:49 GMT

I believe dp_list_partitions above is not accurate because of the the cursor definition where the "join" between

"sprv.boundary_id = sp.partition_number" is innacurate as per SQL 2008 BOL where

sys.partitions and sys.partition_range_values definitions for the the two columns are not matching.

re: Interesting issue with Filtered indexes.

Jacky_shen — Thu, 29 Dec 2011 15:42:38 GMT

Hi ,It seems has not updated for a long time:-(

re: Avoid using JDK Date APIs to handle timezone sensitive date and time

Limited Atonement — Fri, 29 Oct 2010 01:25:34 GMT

This sounds like a sqljdbc problem, right? The driver converts SQL values from the database to java.util.Date (etc) types, right? Rather than do it incorrectly, sqljdbc could just as easily throw an exception ("not castable to java.util.Date. Do not use a deprecated API, silly").

Another solution would be to have the driver handle java.util.Date correctly (putting it in as a UTC or whatever is necessary to get the desired/expected behavior).

I'm interested in hearing what others think.

re: Avoid using JDK Date APIs to handle timezone sensitive date and time

Limited Atonement — Fri, 29 Oct 2010 01:25:21 GMT

Another solution would be to have the driver handle java.util.Date correctly (putting it in as a UTC or whatever is necessary to get the desired/expected behavior).

I'm interested in hearing what others think.

re: Infinite recompile message in the errorlog

adbirka — Mon, 03 May 2010 19:24:41 GMT

Hi,

Recompile Reason 1 is Schema Change, which indicates that one of the tables, views, functions etc. referenced by the query has been modified by DDL. If you're hitting this and your app is not doing DDL, it may be indicative of a bug.

Recompile reasons are documented in Books Online documentation for SP:Recompile trace event, in the EventSubClass column.

re: Infinite recompile message in the errorlog

G Ravichandran — Thu, 08 Apr 2010 19:31:19 GMT

I'm getting the below log.

...starting offset 3594, ending offset 5780. The last recompile reason was 1.

could you please explain what does reason 1 means and provide the complete list of the recompile reasons?

Thanks in advance.

re: XML Data Type Limitations

ed_ward_graham — Mon, 29 Mar 2010 12:25:44 GMT

ID/IDREF Validation

In order to prevent denial of service attacks, we capped the amount of memory available for this purpose at one megabyte. If you try to validate a document which exceeds this limit, validation will fail with error 6969:

ID/IDREF validation consumed too much memory. Try reducing the number of ID and IDREF attributes. Rearranging the file so that elements with IDREF attributes appear after the elements which they reference may also be helpful.

----

Surely there is an option to override this, though? In my academic work I have plenty of XML files large enough to produce this error; you can't possibly be saying that SQL XML simply won't work in these cases, can you? If there is a simple override, please publish it here -- I've had a look but am so far unable to find anything that does the job.

Best regards,

Ed Graham

re: Detecting Overlapping Indexes in SQL Server 2005

Moham.mawla — Wed, 27 Jan 2010 20:44:15 GMT

oh , saw the part about included columns

THX

re: Detecting Overlapping Indexes in SQL Server 2005

Moham.mawla — Wed, 27 Jan 2010 20:39:30 GMT

What about included columns ?

If index has col1,col2

and another has col1 and (col2,col3,col4) as included

They shouldn't be the same here