I have about 40 DTS packages that I want to run against three different databases on the same server. Can someone suggest an easy way to run these jobs and differentiate each time which SQL or INI file to use.
does anybody know if it is possible to use environment variables when calling dtexec utility?
I'd like to run packages stored on server's file system from directory that I've had specified in an environment variable called SSIS_PackagesPath.
Now, I'am trying to write dtexec command, where path to the actual SSIS package would be concatenation of environment variable (i. e. path to package directory) and name of package itself (written explicitly). Is this syntactically possible?
The reason behind is to be able to easily modify package storage directory for multiple scheduled jobs that run SSIS packages.
I am migrating the BE of an Access app. to SQL server 2012. I need to get the user's login name (Windows Authentication login). This can be done using xp_cmdshell, but, xp_cmdshell is considered dangerous and I wouldn't be able to run it once I deploy the app. to the company servers (currently I have SQL server on my computer and as an admin I can enable xp_cmdshell to run, but IT doesn't allow it in company servers for security reasons).
Another question, is it possible to send data from the logged in user from Access to SQL server? What I need to do is let SQL know the username of the logged in user, then, use it to filter the data on SQL. Idea is that user can only run queries for his data (he can't view other user's data unless he is a manager or an admin (currently the app. in Access logs the user in automatically if his Windows Domain username is found in the user's table, and set's his role found in the Roles table). It is this functionality that is giving me some problems to migrate to SQL.
I created a function that uses the System_User SQL built-in function, this retrieves the SQL login username, but, the app. uses 1 SQL local account to connect to the server, so in essence it doesn't work as I need the Windows Domain account username.
I noticed accidentally today on my PATH and discovered that I have several variables for different sql versions. I can understand this as I have upgraded from 2008, to 2012 then 2014. Here are the list of variables
We're just in the middle of performing our first release of SSIS packages through various environments.
The way we are set up currently is the developer will check the package(s) and related config files out of source control, develop on their own machine and check everything in again. Then we deploy the packages consecutively to the Dev, Tst and Prd servers.
We are going down the path of using one environment variable for every config file. some packages share config files (e.g. we've only one config file for each database or ftp connection etc.) and some config files are package specific (error log file connections and success/failure e-mail sources etc.).
What we want ideally is a script that we can check into source control that will create the environment variables on a server at deployment. The "set" command at the command line can be used to change the value of an environment variable, or to create a session-specific variable, but not to create environment variables.
So far the only method that we're using is manually typing in the environment variable names via control panel and copying and pasting the paths into the value fields. Given that we're deploying potentially hundreds of config files, it's obvious that this new-fangled GUI point-and-click and copy-and-paste method of deployment is absolutely foolproof and totaly not prone to any error whatsoever.
Please tell me there's a way to create and set environment variables without going through control panel. running a script or something to do it automatically will: Ensure that each environment is set up accurately and identically, eliminating human error. Ensure that when a developer checks out a package to their local drive, although they may have to change the variable values, he can at least create the relevant variables without having to type them in. Enable efficient migration to another new server (for example during Disaster Recovery).
Can anyone point me to some example scripts at all?
I have deployed a project with multiple packages to SSIS 2012 db. I am able to configure the project parameters fine. But, I am not able to replace the package variable values with the 'Environment' variables.
Any fix for the seemingly random sort order of the variables in the dropdown list when configuring parameters and connection managers in the SSISDB catalog?
I imported all of our connection strings into an environment (about 200 of them). They were inserted in alpha order and the ID values within the internal.environment_variables table shows them in order as well, by ID and by name. When I run profiler and capture the command that retrieves them and run it in ssms they are in order but in the dropdown they seem random.
There are no values within any of the tables that accounts for the order they are in.
If a package has 5 connections you need to go through the unsorted list 5 times to find them.
Sometimes you get lucky and they are in the first 20 or so.
I know I can write a script, just wondering if there is a fix for the sorting.
I have SSIS 2012 Enterprise, using catalog deployment and have more that 50 environment variables for connection to databases across my enterprise.
The problem when i go to configure the packages after deployment and pick the proper env variables, that are not sorted, so i have to browse all entries in order to find the proper entry in environment variables.
I have finished a change request from our client. I need to update clients' database with the one in developments.Here is the changes i made to database:Added/Changed some tablesAdded/Changed some stored proceduresAdded data to some dictionary tableThe data in clients' current database MUST be kept. So how can I merge the changed information to clients' database?
I am not comfortable with DTS 2000 but I need to execute a encapsulated DTS 2000 package from a SSIS package. The real problem is when I need to pass SSIS variables to DTS 2000 package. The DTS 2000 package have 3 global variables that I can identify on " Execute DTS 2000 Package Task Editor - Inner Variables ". I believe the SSIS variables must be mapped on " Execute DTS 2000 Package Task Editor - OuterVariables ". How can I associate the SSIS variables(OuterVariables ) to "Inner Variables"? How can I do it? Much Thanks.
I am a DBA and my boss recently recommended that we change our QA environment so that we don't have any databases on it unless they are actively being tested. This would be to save hardware costs.
The only issue I can think of at this point is that promotion to our QA environment would take up to 2 hours for some of our larger databases if we have to restore production databases to qa for every QA run.
Is this a good idea? How do you run your QA (full or partial copy of prod)? Any input appreciated.
I work on a company where we today have one SQL Server Standard Edition and Reporting Services (SSRS) and Analysis Services (SSAS) installed on the same server.
Now we want to install SQL Server Enterprise Edition, but still have the Standard Edition installed. We are gonna invest in one more server.
I wonder if its possible to install the database engine for both versions on one server and then install instances of SSRS and SSAS on the other server?
Can Standars Edition have SSRS and SSAS on another server than the Database Engine? And is it different versions of SSRS and SSAS between SQL SE and SQL EE, or does SSRS and SSAS get the SQL EE benefits if the database engine is SQL EE?
I have about 23 SQL servers running 6.5 SP3 or SP5a in a 24 hour environment. Most of the activity takes place between 6am and 11pm, with few transaction after 11pm. What is best to do with the main DB's transaction log, have the truncate at checkpoint option checked OR back up the transaction log a couple times a week? The Database is backed up every 6-8 hours.
Jimmy writes "We use a software that stores its database in SQL. We currently have a server box running Windows 2000 Server with SP4 and SQL Server 2005 with SP2 which holds the database. The server is wired in but we have several other stations that connect to the database wirelessly.
The problem is with our wireless stations. When a wireless client travels from one access point to a repeater, it'll drop the connection for that moment. Once it picks up the wireless connection again, it requires closing out of the software and going back into it so it reestablishes the SQL connection to the server.
Is there a solution for a seamless reconnection with SQL for our wireless clients? Is this a problem with our software or SQL? Please advise. Thank you."
Hi Guys, Im new to SQL Server 2005. In our organization, I was tasked to implement and maintain MS SQL 2005 database. We have several system developer and they are using MS SQL 2005 as a backend database.
Currenty, they are responsible for designing their own databases required by their application. My concern is that I want to restrict access to my SQL server that only the DB administrator can access the database server.
My question is that, how they can design their databases without accessing the database server. Is it possible for them to access SQL Server with some restriction? I mean, I want to impose some security measures that they can only access objects within their scope.
Our current scenario is that they have MS SQL Express version installed in their pc and from that terminal they can design and test their application and after everything is in place, Its me who will migrate their respective databases for production in MS SQL 2005 server.
Hoping you can provide me the best alterntive to this query.
Trying to figure out what development enviroment we need in order todo the following:- develop a non-native SQL server stored procedure;- call a web service or java program from the stored procedure;- return static values;- call the stored procedure from a view.How do I get a hold of the right tools and what do I need to put thepieces together?Obviously, I've not used SQL server and I'm looking for the basicstarting point.Thanks!
I'm currently using the setup below for my RDA testing. Is there any problem with this setup?
connected connected Client Apps (SQLCE 3.0) -----------------> Windows Server 2003 (Web server) ----------------> Windows XP (SQL2005)
previously was using windows XP to act as web server and have SQL server reside inside the same machine but having 10 connection limitation from windows xp where only 10 client can connect to the machine. The current setup moves the web server out to windows server 2003 and i believe it solves the 10 concurrent connection limitation but how about the SQL server? is it limited to 10 connection from windows server 2003 also? (Windows XP is my testing server, Windows Server 2003 contains important test data for the whole company) . I tried with concurrent RDA pull for 40 client concurrently with 1 pc having 10 client apps but obtain not really satisfying results. Pulling one table (20Mb) needs 1 to 2 mins through LAN networks but pulling concurrently with 40 clients takes up to 20 - 30 mins.
Now that I've installed SQL 2005 Express Advanced, shouldn't there be a DB Environment I can work with? There must be a configuration mistake because I can't see the "container?" Prior to SP1 I had SQL 2005 Express installed and I could open and use SQL; however, once I loaded SP1 that stopped. I thought if I load the "Advanced" I would be "back in business."
i am working in hospital environment. i am a novice in SQL. i have an urgent issue to answer which is around numbering the order of theatre event for the same patient based on the into theatre time. Patients can go to theatres several times in the single hospitalisation. we need to order as 1, 2, 3 and so on based on the into theatre time which is date/time format. your help is much appreciated. thanks.
Sould one has a seperated environment for production and test system? How do you do it on a same server? Install two instance? How do you seperate test DBs from the production DBs? Please advise...Thank you
I am embarking on a project to upgrade our SQL server environment. I'm curious for some opinions on the relative benefits of Log Shipping versus a Clustered environment and you have any experience that has helped form your opinion on the issue?
I'd like to allow students in a lab to use the Express Manager and T-SQL to create their own databases. I think I've figured out just about everything - but the last step. Here's my thinking on how to do this:
1. Students are power users, not local admin 2. Created a login for the builtinpower users group as follows: create login [BUILTINPower Users] from windows with default_database=[master] go exec master..sp_addsrvrolemember @loginame = N'BUILTINPower Users', @rolename = N'dbcreator' go 3. Now students can start the Express Manager and connect to: localhostsqlexpress using Windows Authentication 4. After they do, they can open and run a script creating a database and populating it with tables and records. 5. All good up to here... but when trying to access the new database using VB Express (file based, not a remote connection) access is denied.
The problem is in the NTFS file permissions being assigned to the new database mdf and ldf files. Local administrators and the builtin Network Service accounts have permissions, but the student who created the database gets nothing... So the student is denied access to the mdf and ldf files when trying to make a connection to them using VB Express.
I can go in with a different account having admin privileges are assign privileges to power users for the mdf/ldf files after they're created but this isn't what I need (students need to work whenever they want without waiting for an admin to fix the file permissions).
Maybe I'm going about this all wrong? If I have to I can insist on students always using VS 2005 instead of VB Express and use connections to a remote database (no problems doing this), but I'm still hoping for an express solution.
I'm new to this forum, so apologies if this is a dumb question (but even if it is - can anyone point me in the right direction?)
I want to offer a SQL 2005 server in back-end configuration for my hosting clients. Basically this means that they administer the DB with a webbased tool and the DB server it self is configured in the backend and has no direct connect to the internet. The DBs can only be access from the frontend web server.
- What security considerations should I take to use this server in a public hosting environment? - We only allow webbased administration, no direct connect to the server are allow and possible. - Multiple databases will exist on the same server from different customers.
I really would like to have as many information as possible. There is not much usefull information available on the web or in the books I own about SQL.
The question should actually be: what do you want to prevent from happing on your servers by authenticated users and ofcourse unwanted users. And how to do this.
I want to make some steps towards securing production database.
1. Give limited rights to Developers, i.e. db reaonly, db writedeny 2. Make strong password for local and Domain 3. Use Windows authentication 4. Enable log for 'Failed Login' attempts.