Viewing 15 posts - 13,396 through 13,410 (of 13,849 total)
Sorry if this is obvious, but is Excel installed on the SQL Server server itself (if you know what I mean)?
Your error is happening at the CreateObject line, before the...
August 8, 2005 at 4:35 pm
But I've just eaten 3 pieces of fried chicken & need to remove the grease somehow - not on my screen either ![]()
August 8, 2005 at 11:13 am
A fixed-length file has ALL records the same length! Yours does not, so it is not.
If you've got less than 65,535 rows you can do it in Excel in 1...
August 8, 2005 at 11:11 am
Here's another way that might be faster as it's not doing the CONVERTs
SELECT floor(0.4799608993157 * 1000) / 1000
August 8, 2005 at 11:07 am
Following your own explanation, surely the formula is
UNION ALL = UNION + duplicates
?
August 8, 2005 at 6:30 am
Somethink like this might be what you need:
ALTER DATABASE <dbname> SET SINGLE_USER WITH ROLLBACK IMMEDIATE
go
Regards
August 8, 2005 at 4:55 am
I don't think that this is enough detail.
Can you also possibly include some sample source data and what you are seeing - highlighting the spurious rows.
Regards
August 8, 2005 at 4:51 am
OK - can you provide a small sample of the data you have and what you want to be returned. No need to include all of the existing GROUP BY...
August 8, 2005 at 3:43 am
Take a look at the INFORMATION_SCHEMA views in BOL - you'll get the constraints from there. But the actual CREATE script - not available from a system view as far...
August 8, 2005 at 3:15 am
Yes, use Query Analyser. Open the Object Browser and browse to the table you wish to script. Right click it and select 'Script object to new window as / Create'...
August 8, 2005 at 2:57 am
The error messages, in this case, are accurate and I presume that you understand why they are appearing. I have no experience of Sybase, so I cannot comment on why...
August 8, 2005 at 2:52 am
Try this for SP level:
SELECT SERVERPROPERTY ('productlevel')
August 5, 2005 at 4:39 am
One of the simplest ways is to change your data to a consistent format, eg:
1.00, 1.01, 1.02, ..., 1.10
would work.
But if that doesn't suit, you need to write some...
August 4, 2005 at 1:28 pm
You are correct ... SQL Server treats nulls as special and you will often find that comparison operators (= <> etc) do not return rows where one of the items...
August 4, 2005 at 1:23 pm
So your first query is to return a list of valid clients - and then you need to join that with 'table'.
To select valid clients:
select distinct t.client from table t...
August 4, 2005 at 11:41 am
Viewing 15 posts - 13,396 through 13,410 (of 13,849 total)