Viewing 15 posts - 2,641 through 2,655 (of 3,700 total)
Well the APEX stuff isn't free but it is very good. If you start with a shrink wrapped ApexSQL Doc and a cup of coffee it will pay for...
December 15, 2005 at 9:33 am
Do I have to go through the all the CreateObject("ADODB.Command") stuff to execute a query to get the count back or is there a quicker way of doing this?
December 15, 2005 at 8:55 am
In the UK estate agents have their own dialect of English.
Agent: A property with a sea view.
English: Its on a crumbling cliff top that recedes at 6ft per...
December 14, 2005 at 12:59 pm
The row size limit comes into play if the DATA exceeds 8096 bytes not if the STRUCUTRE exceeds 8096 bytes.
I seem to recall that for TEXT and NTEXT only 16...
December 14, 2005 at 12:52 pm
Thanks Noggin, that fixed it
December 14, 2005 at 6:53 am
Use the TEXT or NTEXT datatype. In SQL2005 use VARCHAR(MAX) or NVARCHAR(MAX).
This gives you 2GB of text.
In SQL2000 the text itself is not stored in the row, only the...
December 14, 2005 at 6:41 am
I thought that the @@RETURN_VALUE is intrinsic to the RETURN statement. I didn't think you could set it at will.
I tend to use positive values greater than zero to...
December 14, 2005 at 6:36 am
I was revisiting the problem I posed in http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=21&messageid=229499
The child table has an identity field called SelectionId which isn't mentioned in the schema at all and yet the bulk...
December 14, 2005 at 1:44 am
"Good" and "cursor" in the same sentence.
"Old Fashioned" is OK, it implies that something has worked
December 13, 2005 at 7:22 am
You can emphasise standards as much as you like with regard to XML but this is a data entry issue.
If you have required fields on a form within an application...
December 13, 2005 at 3:10 am
This might work a bit faster
DECLARE @ProcName sysname ,
@usercredentials sysname
set @procname=''
set @usercredentials='Development'
WHILE @procname is not null
begin
SELECT @procname = min(name)
FROM sysobjects
WHERE xtype='P' and name > @procname and name not like 'dt_%'
IF...
December 13, 2005 at 1:53 am
I take your point but DATTIME fields can hold values up to 31-Dec-9999. If you use a date that ridiculously far in the future then you DATEDIFF should always...
December 12, 2005 at 1:22 pm
Have you considered using LIKE %[^0-9]% as a comparison?
In otherwords if your string contains characters in that are not digits?
December 12, 2005 at 12:43 pm
I don't know how big your database is but in a live transaction database I would put the growth at fixed growth rather than a percentage.
I have come across this...
December 12, 2005 at 12:39 pm
I don't have SQL Server available as I write this but my approach would be to do a DATEDIFF between a fixed date in the future and your time col...
December 12, 2005 at 12:36 pm
Viewing 15 posts - 2,641 through 2,655 (of 3,700 total)