Viewing 15 posts - 511 through 525 (of 595 total)
You said that, initially, the import worked, but now it doesn't work. Did you create the DTS package on a client PC, then try and run it on the server? ...
August 4, 2004 at 5:41 am
Since you're using dynamic SQL, why not declare variables for each of the phrases that can be null and create them separately, like this example using @cond1 for the CycleBeg/CycleEnd...
August 3, 2004 at 6:31 am
Are you using the Visual FoxPro ODBC driver? The ".fpt" file extension is for FoxPro memo files, not dBase III. dBase III memo files are ".dbt".
August 2, 2004 at 8:01 am
Does the DTS package drop and recreate the table each time it runs?
To see if the constraint name is used by another object, run the following on server B:
July 28, 2004 at 5:49 am
How about using a UDF? Here's an example:
CREATE FUNCTION dbo.fnGMT
(
@bstDateStr varchar(22)
)
RETURNS datetime
AS
BEGIN
-- British Summer Time (BST) is the daylight saving time in effect in the United Kingdom...
July 26, 2004 at 6:49 am
The virtual pc method is a good one for learning using a single PC. It allows you to reinstall operating systems without disturbing the other virtual systems you've installed.
VMWare costs...
July 23, 2004 at 6:23 am
Kim - run this to see if you get any results:
SELECT * FROM [case] WHERE caseno LIKE '%]%'
Jeff - it works until the caseno column contains an value that can't be converted...
July 21, 2004 at 5:44 am
Indexed views should not be a problem. The difference between Standard edition and Enterprise edition is that the query optimizer considers indexed views automatically in the Enterprise edition but not in the Standard...
July 20, 2004 at 12:17 pm
Sorry if I wasn't clear. SQL Server 2000 still performs implicit conversions such as your example. However, if the varchar(12) column contains non-integer values, you may get an error when...
July 20, 2004 at 12:10 pm
If the column is of type varchar(12), you should use the quoted version of your query:
select * from [case] where causeno = '17741'
Without the quotes, SQL Server...
July 20, 2004 at 7:26 am
You mentioned that you use indexed views. To get that performance in standard edition, you'll have to modify your queries a bit.
To use indexed views in SQL Server 2000 Standard...
July 20, 2004 at 7:19 am
A couple of days ago there was a post regarding how to implemenent the Oracle function TRANSLATE in SQL Server for which I wrote a UDF.
Try the following UDF. Run...
July 9, 2004 at 7:30 am
Seems like most of the time, this error is caused by Oracle dates that exceed the date range of SQL Server, which is 1/1/1753 to 12/31/9999.
Review the following thread, maybe there...
July 7, 2004 at 5:54 am
As the others have said, nothing like Translate exists is SQL Server. You'll have to write inline code to do it, or use a UDF such as the following:
-- TRANSLATE(detail.description,'\/&*?+#;<>",','~~~~~~~~~~~~')
--...
July 6, 2004 at 6:04 am
-- If your integer date is of the form 'yyyymmdd', try this example:
DECLARE @d int
SET @d = 20040702
SELECT @d, Convert(datetime, Convert(varchar(8), @d))
-- If it's in some other format, such as...
July 2, 2004 at 7:36 am
Viewing 15 posts - 511 through 525 (of 595 total)