Viewing 15 posts - 1,111 through 1,125 (of 2,487 total)
I think a change is needed.
With the release of SQL Server 2005, I think the forums should be organised as per the product toolset.
eg:
Management Studio
-- General Administration
-- Security
-- Replication
-- Notification...
--------------------
Colt 45 - the original point and click interface ![]()
June 16, 2005 at 4:43 pm
![]()
![]()
![]()
![]()
Drag 'N' Drop is your...
--------------------
Colt 45 - the original point and click interface ![]()
June 15, 2005 at 7:02 pm
Unfortunately you can't set it to auto-fit. Best you can do is to layout the columns in the report to accomodate the data as best you can.
Also, if you haven't...
--------------------
Colt 45 - the original point and click interface ![]()
June 15, 2005 at 1:14 am
I thought that's what stored procedures were for ![]()
--------------------
Colt 45 - the original point and click interface ![]()
June 14, 2005 at 11:39 pm
Why do you use a custom logging table instead of the sysdtspackagelog table ?? ![]()
![]()
--------------------
Colt 45 - the original point and click interface ![]()
June 14, 2005 at 4:54 pm
Yes this works well for multiple tables where the structure is the same. If you try the same approach with tables that have a different column structure without modifying the column...
--------------------
Colt 45 - the original point and click interface ![]()
June 14, 2005 at 4:52 pm
Create a DTS package that copies one table. Then save this package as a VB file. Take a lokk at how the transformation and column mapping are done. You'll need...
--------------------
Colt 45 - the original point and click interface ![]()
June 14, 2005 at 2:16 am
Check the FAQ on setting connections over at http://www.sqldts.com
--------------------
Colt 45 - the original point and click interface ![]()
June 14, 2005 at 2:03 am
Or for something completely different, you could turn on the inbuilt SQL Server Package Logging. This logs package/step/task execution to tables in the msdb database. From there it's a simple...
--------------------
Colt 45 - the original point and click interface ![]()
June 14, 2005 at 1:57 am
You obviously aren't following the installation instructions ![]()
--------------------
Colt 45 - the original point and click interface ![]()
June 10, 2005 at 12:06 am
That was it. Ta muchly.
--------------------
Colt 45 - the original point and click interface ![]()
June 8, 2005 at 8:37 pm
Isn't parsing and validating something that's done on the client, or business layer? What is the client application developed in? Does it understand native date and time datatypes?
--------------------
Colt 45 - the original point and click interface ![]()
June 2, 2005 at 7:46 pm
You are aware that using the Data Driven Query task makes the Datapump work in row-by-row mode?
It would be much more efficient to bulk-load the data straight into a staging...
--------------------
Colt 45 - the original point and click interface ![]()
June 2, 2005 at 4:51 pm
Use DTS to import into a staging table. The run appropriate insert/update/delete T-SQL statements to update the production table.
For inserts, you would left join from staging to production and insert...
--------------------
Colt 45 - the original point and click interface ![]()
June 1, 2005 at 9:24 pm
Ok, then before you come to a SQL Server forum to get help about an error, how about you visit a VB.Net forum to get help about how to use...
--------------------
Colt 45 - the original point and click interface ![]()
June 1, 2005 at 6:47 pm
Viewing 15 posts - 1,111 through 1,125 (of 2,487 total)