Viewing 15 posts - 376 through 390 (of 2,488 total)
Be aware that if you use UDL files to store the username and password they will be in plain text and available for anyone that has read access to the...
--------------------
Colt 45 - the original point and click interface ![]()
April 26, 2006 at 9:01 pm
I do recall reading in one of the upgrade doco's (sorry can't recall which one at the moment) that specified that all target servers should be upgraded before the master....
--------------------
Colt 45 - the original point and click interface ![]()
April 26, 2006 at 4:52 am
From a DBA's perspective, first and foremost you need to guarantee the databases are successfully being backed up. Once you have a successful disk backup the file can be shunted...
--------------------
Colt 45 - the original point and click interface ![]()
April 26, 2006 at 4:49 am
I'd just use something like GZip and call it via WScript.Shell in the ActiveXScript task.
Much, much easier.
--------------------
Colt 45 - the original point and click interface ![]()
April 26, 2006 at 3:29 am
Also, we have a MSX/TSX setup so for some of our older DTS packages that don't read their config dynamically, we alter the job on the MSX server and then...
--------------------
Colt 45 - the original point and click interface ![]()
April 26, 2006 at 3:28 am
We run DTS packages on multiple servers and they each read their config info from a local table.
For administration, each of these tables are edited via a central ASP.Net...
--------------------
Colt 45 - the original point and click interface ![]()
April 26, 2006 at 3:25 am
If you're using Active Directory, you could setup a linked server to run LDAP queries.
--------------------
Colt 45 - the original point and click interface ![]()
April 25, 2006 at 10:42 pm
You can use the stock standard DIR command executed via xp_cmdshell. Just insert the result into a temp table.
EG:
CREATE TABLE #dir ( [ID] int IDENTITY(1,1) , [Dir] varchar(255) ) INSERT INTO #Dir([Dir]) EXEC...
--------------------
Colt 45 - the original point and click interface ![]()
April 25, 2006 at 10:37 pm
Just because you can do something doesn't mean it's a good idea ![]()
It would probably be better to backup to seperate files. That way...
--------------------
Colt 45 - the original point and click interface ![]()
April 25, 2006 at 10:26 pm
We use a database table to store this info. If the server is up and running then the table is available.
In fact we store all Global Variables for each package...
--------------------
Colt 45 - the original point and click interface ![]()
April 25, 2006 at 10:21 pm
Not to sure about 2005, but in SQL 2000 RS it was by design. We had to include an extra device info parameter to output ANSI characters.
--------------------
Colt 45 - the original point and click interface ![]()
April 21, 2006 at 11:29 pm
It's probably creating the CSV file in unicode format. SQL 2000 Reporting Services has the same issue.
--------------------
Colt 45 - the original point and click interface ![]()
April 20, 2006 at 4:46 pm
As noted on the home page the guys are aware of this issue and are trying to fix it ASAP.
I'm sure they're pulling many a late night to fix the...
--------------------
Colt 45 - the original point and click interface ![]()
April 20, 2006 at 4:44 pm
What I would do is have a short VBScript as the first step of the SQL Agent Job that checks for the file. Then just set the appropriate amount of...
--------------------
Colt 45 - the original point and click interface ![]()
April 13, 2006 at 8:47 am
That's easily done with a few global variables and a Dynamic Properties task.
--------------------
Colt 45 - the original point and click interface ![]()
April 10, 2006 at 7:23 am
Viewing 15 posts - 376 through 390 (of 2,488 total)