Showing posts with label files. Show all posts
Showing posts with label files. Show all posts

Thursday, March 22, 2012

Deployment problem

Hi. I created an app on my laptop and wish to deploy it to a server. I followed the steps to release the project and I copied the files over to the server. I'm getting an access denied or server does not exist error message. I went into the code behind pages to change the connection string but it still doesn't work. I think it has something to do with the SQL Server name. It's just local. The person that installed it did not change the name. In enterprise manager, it looks like this. (local) (Windows NT) Should the connection string be SERVER/(local) ? Is there a default name I'm not aware of? Any help would be greatly appreciated. Thanks!

Here is the error message:


Server Error in '/' Application.
------------------------

SQL Server does not exist or access denied.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: SQL Server does not exist or access denied.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[SqlException: SQL Server does not exist or access denied.]
System.Data.SqlClient.ConnectionPool.GetConnection(Boolean& isInTransaction) +474
System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString options, Boolean& isInTransaction) +372
System.Data.SqlClient.SqlConnection.Open() +384
System.Data.Common.DbDataAdapter.QuietOpen(IDbConnection connection, ConnectionState& originalState) +44
System.Data.Common.DbDataAdapter.FillFromCommand(Object data, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +304
System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +77
System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable) +36
ICCSalesTracker.WebForm1.GetRGU() +433
ICCSalesTracker.WebForm1.Page_Load(Object sender, EventArgs e) +7
System.Web.UI.Control.OnLoad(EventArgs e) +67
System.Web.UI.Control.LoadRecursive() +35
System.Web.UI.Page.ProcessRequestMain() +750

Another question, would local host work for server id?

Also, I took a look at PDB file and it still has my other file paths. Does that matter? Should they be changed?

And lastly, The web server admin does not want to use the inetpub folder so he created a different folder that houses all of the files. What will that effect? What do I have to change?

Please let me know. Thanks!!!!|||Hi,
It sounds like the app worked well on your laptop, but wont work when moved to a server. You need to understand the authentication and authorization scheme the app will use to access the DB. That situation may be different from the one you had on your laptop. You can use Windows Integrated security, if IIS and the SQL Server are on the same computer and the user is in the same domain. For an internet app, the client may not have credentials to pass, or passing them posses a risk, so ASP.NET uses a default user for it's worker process called ASPNET (it's called NETWORK SERVICE by Windows 2003 Server). SQL Server sees this default user and checks to see if it has permission to use that DB. In order to gain access to the DB, the ASPNET (or NETWORK SERVICE), user needs to be registered on the SQL Server and given the appropriate (just enough), permissions to use that DB. There are other factors and schemes, but you might just look to see that the SQL Server DB has the right user set up correctly.
Good luck.|||I added ASPNET & NT AUTHORITY and even my domain user is set to owner. It still will not pull it up.|||Hi,
Was the user in the form "NT_AUTHORITY\NETWORK SERVICE"? I know that worked for me one time on a local setup that didn't accept "thecomputername\NETWORK SERVICE". Also, are you sure that these default users have the correct read/write permissions set?

Some more that know more than I do will probably get you the right answer. If I had to figure it out myself, I might try using a different type of Authentication (Forms), just to see if I could get it working - then figure out how to get the authentication scheme I want working too. You might try writting a very simple data access app (using the Data Web Form wizard), just to test the connection. That way you don't have to messup your project.

Good luck.|||Thank you for your help Brian!

Well I figured out the server name. Apparently, if the server say local when you look at it in Enterprise Manager, you leave the sql servername blank in the connection string. "SERVER/"

Now I"m getting a login failed for user 'NT AUTHORITY\NETWORK SERVICE error even though IIS is set to windows integrated authentication. Is there another place I have to change a setting to ensure it only uses windows authentication?|||Hi,
Glad to hear that you are making some progress - even if my info wasn't much help.

Is the login error message from SQL Server?

In your message it says ...for user 'NT AUTHORITY\NETW...', but I think it should have an underscore between NT and AUTHORITY -- 'NT_AUTHORITY\NETWORK SERVICE'

It seemed odd to me that they connect the first two part name, and leave a blank in the second, but that's the way I saw it on my system. Double check.

Good luck.|||You are correct. I typed it in wrong. I had to add that user to the SQL users directory and now it loads. But now I have yet another problem. The initial page loads. It has an onload function that calls a stored procedure to return the number of units sold for the day. That works just fine. The second part of the page is the order entry function that passes parameters to an insert procedure. When I click on submit, I get an access denied or server not found error. It's wierd because it's using the same connection string as the on load procedure. Do you have any idea what that might be? Thanks for the help!|||Hi,
Looks like you are making progress.

I'm not sure about why the second part of the page wont function. My first guess is that the first part is only reading data, and it sounds like the second part is reading and writing. Are you sure that the user permissions include insert and update allowed?

You need to be very careful with any database access granted to internet users. That's even more the case when you grant write or execute permissions. Keep in mind that it's one thing to get it working, but you'll want to make sure you have the security issues understood and accounted for before you deploy the application. I'm still working my way through this myself. Using stored procedures for the functions that your users will perform is generally a good idea, but they're not a security panacea. You'll have to do some research to find the best safegaurds. I know that MSDN has some series on security best practices, webcasts, etc...

One other thing occurs to me, if you don't have a compelling reason to have both the functions you mentioned on the same aspx page, consider moving the second to another page, with a link from the first. My thought is that it compartmentalizes the functions, and it could make it easier to track down problems, and keep the first function available, even if the other is broken. You'll know if it makes sense to do this in your project.

Let me know how it goes for you.|||All of the required users have permissions to all of the objects in the database. This is an intranet and the security is set to windows integrated. The reason the page has both the on load and on submit function is to track entered units in real time. As they enter in sales, the datagrid tied to the getunit stored procedure runs every time the page loads. So when the sales agent enters in 2 revenue units, datagrid reflects those units when the page reloads. That portion works just fine. However when I click submit, I get the following error


Server Error in '/' Application.
------------------------

SQL Server does not exist or access denied.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: SQL Server does not exist or access denied.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[SqlException: SQL Server does not exist or access denied.]
System.Data.SqlClient.ConnectionPool.GetConnection(Boolean& isInTransaction) +474
System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString options, Boolean& isInTransaction) +372
System.Data.SqlClient.SqlConnection.Open() +384
ICCSalesTracker.WebForm1.btnSubmit_Click(Object sender, EventArgs e) +7239
System.Web.UI.WebControls.Button.OnClick(EventArgs e) +108
System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +57
System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +18
System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +33
System.Web.UI.Page.ProcessRequestMain() +1292

I'm pretty sure it's not the connection string as that is specified in the web.config file. I'm thinking it has something to do with IIS or something. Thanks for the help! I'll let you know if I figure it out...

Deployment Of SSIS With Config Files


I went through other threads and links on this subject. Still one thing which concerns me is the config files.

My current folder path is C:\Karunakaran\folder1\folder2\

Under folder2 I have the following files

4 dtsx files
1 .database file
1 .dtproj file
1 .dtproj.user file
1 .sln file
1 .suo file

Config folder ( C:\Karunakaran\folder1\folder2\Config\)
common.dtsConfig
oracle.dtsConfig

Based on some of the threads, when I enabled package configuration, I changed the path from
C:\Karunakaran\folder1\folder2\Config\common.dtsconfig -> common.dtsconfig

Once I did this, when I open the project I get a dozen of warning similar to the one below

Warning loading <package1>.dtsx: Failed to load at least one of the configuration entries for the package. Check configurations entries and previous warnings to see descriptions of which configuration failed.

What am I doing wrong here? If I have to deploy this to another box, what should I do to ensure that nothing breaks once its copied / installed?

Thanks

wouldn't you need \config\common.dtsconfig ? (since it isn't in the root folder?)|||You should always use absolute paths. Always. With that said, the best way to make the path portable is to use environment variables to store the base path. Then you can use the environment variable in the package configurations dialog to specify where to store the file.|||

EWisdahl wrote:

wouldn't you need \config\common.dtsconfig ? (since it isn't in the root folder?)

I did tried that earlier, when I give \Config\Common.dtsConfig i was getting the following error.

ADDITIONAL INFORMATION:
Could not find a part of the path 'C:\Config\Common.dtsConfig'. (mscorlib)

Thanks

|||

Phil Brammer wrote:

the best way to make the path portable is to use environment variables to store the base path. Then you can use the environment variable in the package configurations dialog to specify where to store the file.

I dont think Sys Admin will allow the usage of environment variables, looks like absolute path is the only way for me.
Looks like Microsoft should do something about the config files issues.

Thanks|||I'm not sure there are any issues. Besides, you can always use SQL Server based configs.

Using relative paths has a whole host of problems, when considering, depending on where dtexec is executed from, the root path could be different that what you are expecting.|||


But this also does not give me flexibility of where I want to store my config file.
The other problem I have noticed is that I cannot use one single config file for all my packages, causing a maintanence issue.

I have not tried Sql Server based config, let me try it and see.

Thanks

|||You can use one config file for numerous packages. No problem.|||I prefer SQL Server configs, for exactly the reasons you are describing. The only catch I have found with them is setting the initial connection to the database that stores the configurations. I like using a single environment variable to store that connect string, but you can also use the connection switch of DTEXEC to set it.|||

Phil Brammer wrote:

You can use one config file for numerous packages. No problem.

I'm not able to.

I can do that, ONLY if all my packages have all the variables, connection managers defined in the config file, else it throws errors / warnings whenever I open up the package.

Thanks|||There have been a few posts on this recently. You can create all your connection managers in every package (if you don't use one in the package, it doesn't cause any problems) or you can set variables through the configuration, and set the connections based on expressions that use the variables.|||I going to try with both. But I think this looks more a work around.
I hope MS address this issue.

Thanks|||

Karunakaran wrote:

I going to try with both. But I think this looks more a work around.
I hope MS address this issue.

Thanks

No, I'd consider this "best practices."

If you feel, though, that this is a bug, then please post a submission on the Connect site: http://connect.microsoft.com/sqlserver/feedback

|||I'm not sure if this is a bug,but I'm sure this flexibility is required, especially if there are multiple packages, and when developer has no access to the prod env.

Thanks
|||

With regards to best practice:

I can't see how to use configuration in the case of branching using source control without manually changing the path for every branch.

And even worse if the files are checked out to different folders then the config will not work with an absolute path.

Storing configuration on the SQL server would also be difficult to use when using source control especially if you are working on local databases.

Do any of you have a good solution to using SSIS with source control and branching?

deployment of sqlserverce.dll

I registered to redistribute the runtime for SQL Server Compact edition.

I have a desktop application which uses SDF files as the database.

In VS 2008 - when I set System.Data.SqlServerCe configured to Copy Local as TRUE - sqlserverce.dll does not get inserted to my bin directory. I am assuming if I manually put the DLL file into my bin directory (and deploy it) - the DLL file will automatically be used by my app?

If you install the 3.5 redistributable/runtime with your app, you do not need any SQL Compact DLLs in your bin folder.

http://www.microsoft.com/downloads/details.aspx?FamilyID=4dd09a86-03eb-40a1-bd32-0fd8bcdf7be0&displaylang=en

|||

This defeats the purpose of packaging up the database with your deployment package. I am not the original poster of this thread but I will need a solution that does not need/want to install the Compact Edition Runtime installation with my application deployment. The installation of the runtime package requires the user to have admin rights and most of my end users will not have admin rights.

Therefore, please provide us with the steps to include the Sql Server CE provider assemblies with our application deployment package.

Thank you.

|||Maybe tutorial 1 here will be able to assist you: http://msdn2.microsoft.com/en-us/sql/bb219480.aspxsql

Deployment of Rdl files and datasource to Production Server

Hi All,
I have develoded the SRS report using vs.net , and deployed to my local
sever using vs.net all works fine.
No i need to deploy these reports to a production server where vs.net is
not present.
So can any one tell me how to automate this process of deployment to
production server insteed of mannualy uploading the rld files and creating
data source in report manager.
Can set up be made for this scenarion to my production server.
Please help me it's urgent,
Thanks in advanceYou can create a deployment script with the rss utility in RS. Please
refer to the two scripts that ship with the product and customize it to
deploy to your production server. Command line arguments can be
specified for the datasource, connection string , report server url
etc.|||You have here the code for deploy the report on any SQLRS server
http://www.rdlcomponents.com/ASPExamples/default.aspx
Jerry
"RN" wrote:
> You can create a deployment script with the rss utility in RS. Please
> refer to the two scripts that ship with the product and customize it to
> deploy to your production server. Command line arguments can be
> specified for the datasource, connection string , report server url
> etc.
>

Wednesday, March 21, 2012

Deployment files needed by sqlserver 2005 driver

Hello all

I built an application that connect to MS SqlServer2005 using Native driver (sqlncli.msi) I install that file from MS site, I need to deply my application to the end-user, and I would like to know what files do I need to deploy to make sure the application is gona run okay on the client PC's.

I search in the registry for the driver, and I found this "sqlncli.dll", is it enough or I need to include more files !!

Thanks and best regrdas

Waleed

SQLNCLI does not have specific dependencies, however your customers should have MDAC installed, which should be not a problem with the recent releases of Windows.

See also http://technet.microsoft.com/en-us/library/ms131334.aspx

Deployment and Configuration

Hi:

I have a SSIS package on my local machine, and would like to deploy it to DEV server. Which files should i be moving to the SQL DEV Server? and where? How do I modify connection managers or is there a way to do that from the Management Studio or some other way? Thanks and I would definitely appreciate some prompt advise.

Someone will provide more information, I'm sure, but have you searched this forum for "deploy"?|||

Yes, I have checked out some posts on Deployment, but havent ran into anything standard. There seems to be more than one way of deploying. I would like to follow best practices. Thanks.

|||That's the beauty of SSIS. There are many ways to accomplish one task. The "best practice" is usually best determined on your own so that it fits your way of life. We each have our own requirements/standards so what my best practices are may not be Jamie's, or Rafael's, or.....|||

I prefer to have my packages as File system files (.dtsx); then all I have to do is to move (copy the files) them into a folder in the server. I use SQL Server table based package configurations to change connection strings at run time (and any other required property). I know there is a Deployment wizard in BIDS but I have never looked into that; so you do the research. Some times I use the SET option in the execution command line to override properties in the packages while testing.

As Phil points out; the best practice sometimes depends in your preferences, IT standards, etc....

|||

Lets say I would like to use the "copy over the files" method. What files am I moving over? and where on the server? Also for changing connection strings, how do i set the properties? Where? Thanks.

|||

Only the .dtsx files are required. In case you are using package configurations based on a XML file; you need to copy and secure it as appropriate. You choose the location; just keep in mind that that location needs to be accessible to the user running the packages.

To set connection strings; you can use package configurations; I use a combination of XML file to set the connection string of my SQL server based configuration table. If you search for 'Package configurations' you will find a lot of info. Jamie Thomson's blog, http://www.sqlis.com/ and BOL have some good info.

|||

The package I have will be scheduled daily, although, the connection strings config is only meant for Deployment Process, because the DTSX has to go thru DEV, QA, BETA, and onwards to PROD. Thanks.

|||

MA2005 wrote:

The package I have will be scheduled daily, although, the connection strings config is only meant for Deployment Process, because the DTSX has to go thru DEV, QA, BETA, and onwards to PROD. Thanks.

Your scenario is a very common one. SQL Server agent will be your best bet for scheduling your packages. I too, like Rafael, prefer to store my packages in the file system, versus storing them in MSDB.|||

If the only thing that needs to be changed/configured is a single connection string, and you have only one package (no parent package calling child packages)...you may want to use the SET option of the package execution command line instead of package configurations. I don’t like that approach when I have many packages that need to be configured in the same way; as I have to maintain every command line, as opposed of maintaining an entry in a config file/table

Deployment Acritecture of SRS 2005

Hi,
I want to know how the .rdl files are deployed in the IIS Server and what is
the path where there are deplyed. Also how the UI identifes from where to
access the .rdl file attached to the perticular record.THe reports are stored in a table named Content(s?) if I remember
correctly...
--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Parimal" <Parimal@.discussions.microsoft.com> wrote in message
news:6BE09721-2DF8-4681-BFEB-FEF790CC9B5D@.microsoft.com...
> Hi,
> I want to know how the .rdl files are deployed in the IIS Server and what
is
> the path where there are deplyed. Also how the UI identifes from where to
> access the .rdl file attached to the perticular record.

Monday, March 19, 2012

Deploying web app, which SQL files do I upload?..

I'm working on a web application that uses SQL Server 2000. Once I'm ready to upload my website to a production server, I need to know how to upload my SQL Server database files to the server. Are there actual files that can be uploaded? I've only deployed a website that works with MySQL to a production server, and there were no files to upload... the database had to be created on the server, and then the data itself had to be exported to text files (on my computer), then imported/uploaded to the production server using SQL statements...

How do I do this?

Thanks~::I need to know how to upload my SQL Server database files to the server.

Ask your provider, systemadministrator or whoever manages this.

Our hosting operation does NOT allow uploads of sql database fiules - you are supposed to create a new database and use the copy database wizard out of SQL Server's enterprise manager.|||hi
i saw http://europe.webmatrixhosting.net, do you know that all hosts provide like this host utilities to work with SQL Server? utilities like http://www.aspenterprisemanager.com??

i'm developing an asp.net storefront that uses SQL Server Database, but i'm worry about after developing that, i want to do what?!! how to manage my database?
tahnk

Sunday, March 11, 2012

Deploying Reports to a different Environment

I am developing some reports and the only way I can deploy the reports to
the production server is via files on a CD.
The project manager would like to encapsulate everything into an .MSI file
for deployment.
Is there any documentation on whether this can be done? or how to go about
deploying reports when all I have is a bunch of files
Thanks
BobYou can deploy using RM from VS or through scripts. Best way for you is to
create scripts and put it in a batch file.
Amarnath,MCTS
"Bob" wrote:
> I am developing some reports and the only way I can deploy the reports to
> the production server is via files on a CD.
> The project manager would like to encapsulate everything into an .MSI file
> for deployment.
> Is there any documentation on whether this can be done? or how to go about
> deploying reports when all I have is a bunch of files
> Thanks
> Bob
>
>

Deploying Reporting Servoces Reports to the Production Server

Hi,
I am new to Reporting Services. I have installed RS and SQL Server200 on my dev machine. I have created a few .rdl files and deployed them. The TargetServerURL property of my project is set tohttp://localhost/ReportServer. and TargetFolder is "ScoreCardReports".
I have used the reports in my Asp.net app by the RS Webservice (Web Reference URL is :http://localhost/ReportServer/ReportService.asmx.). I used the Render mehtod the get the images from the reports.
Now I will deploy my Asp.net app by creating the msi installer created by the setup & deployment project.
But how to package the .rdl and .rds files so that the app works on the production server ? That will be a windows2003 server.
Please help.The way we deploy to prod is to have the change control person log ontothe prod reporting services, and use the "upload file" option,selecting the .rdl file to import.
|||

I have solved the problem by executing the rs.exe in a bat file. I have created the .rss file containing all the commands to create the reports folder and deploying the reports to the target server. The path of the file has been passed as a parameter to the RS command.

The person to setup the whole application should now only run the .bat file and all the reports will be deployed to the server at one click.

|||

Hi Boss Th Question what u asked is little bit complex.

What u need to generate an .rss file by writing code in VB.Net

use this .rss file with a small command & create a batch file

So whenever u run that batch on a particular server the Reports what u have developed will be deployted on tto the Particular Production Server

Friday, March 9, 2012

Deploying multiple files through a package

Hi

I am working on on SQL Server Integration Services and facing few problems in it.

Actually am supposed to create a package that would automatically pick excel spreadsheets with a specific format and import it onto the SQL server.
(Lets say , there is a company named AB and they have got various products named CD,EF and GH and each product has its own spreadsheet in which its monthly sales(JAN, FEB,...NOV, DEC) is given. So i have to build a generic package for each product (lets say CD) so that i don't have to import every spreadsheet seperately for each month.
To summarize i just have to build a package where i can deploy the various spreadshhets again and agian instead of building a package for each and every month spreadsheet seperately.

I have tried and used lots of combinations like Loop
conatiners etc. but still am not able to find a solution to it.

Please help me out on this.

If the metadata (i.e. Number of columns, column names, column types) of each file is different then you cannot load everything using the same data-flow. You need a seperate data-flow for each one.

You can still put everything into one package. You need to decide, at execution-time, which data-flow(s) to execute based on which file you want to process. In other words, you need conditional workflow: http://www.sqlis.com/default.aspx?306

-Jamie

|||

But the format of all the monthly spreadsheets are the same. So still i have to cosider conditional flow or it can be done through any other way also.

Cheers

|||

Oh OK, well you're all right then. You just need to set the name of the file that you want to process dynamically. You do this by putting a property expression on the Excel Connection Manager's ConnectionString property.

-Jamie

|||

Hi

I am really sorry to bother again but actually ,as i am new to these services, can you please guide me how to do it or may be direct me to some useful article.

Thanks a lot .Its been really helpful though.

Cheers

|||

Sure, this: http://blogs.conchango.com/jamiethomson/archive/2005/05/30/1489.aspx provides all that you need to know.

There's probably more in there than you need but you can pick out the bits that are important. Make sure you download the demo which will show you how all this works.

-Jamie

|||

Thanks a lot. I really appreciate it. Its working fine now.

Actually i have twisted the previous question a bit. I don't know why but i am just keen to learn whatever comes my way.

Lets say we have a database table(eg XYZ) with certain attributes (A,B,C,D,E,F) and now we want to build a package which would take excel file(eg XUV) as a source and export the data onto the table which has already been created in the database(i.e XYZ). But in the excel file we only have few attributes that match the destination column(lets say A,C,F). Now in order to get it working we have to map the columns manually. Then perform the normal procedures and it would be loaded.

This package would deploy only one source file(i.e XUV). Actually what i was curious about is that if there are hundreds of excel source files(with the same attributes like the former excel source XUV) waiting to be loaded then am i supposed to do mapping for each and every file.

Thanks in advance.

|||

Not quite sure I fully understand what you're saying but the important thing is you have to build a data-flow for each type of source file. By "type" I mean all files that have the same metadata are of the same type.

-Jamie

|||

Hi

Actually am still facing some problem with my last query.

There is no connection manager in the property listings in the expressions.

|||

Where are you looking? What object are you looking at the properties of?

You have to change the ConnectionString property of the connection manager.

-Jamie

|||Really sorry was a mistake.

Saturday, February 25, 2012

Deployed Report

Hello,

When I run Build=> Deploy , where does the report go, I check Virtual Directory of ReportServer which is C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer in my case and I do not see any file related to my report.

Thanks,

It depends on the Target URL specified under project in VS.Net

Deployed files reduced size

I am wondering why deployed packages are so much smaller than built packages. What is removed and why isn't it removed when the packages are built?

I have a package that goes from 3Mb to 1.5Mb

Any answers|||We don't remove anything from package during deployment. The things that may affect package size:
1) XML encoding. UTF-16 (usually called just "Unicode") may take twice as much as UTF-8. I think we use UTF-8 in most places, but not sure.
2) Encryption. If you encrypt the whole package (instead of just sensitive information) it may noticeably increase package size.
How you do deploy, and to what location?|||

You're spot on with the unicode, which concerns me.

The package file in the bin folder is unicode with no directive in the xml clause i.e. <?xml version="1.0"?>, the deployed file is utf-8 but with the same xml directive.

The file is deployed by double clicking on the deployment manifest and selecting "file system".

Surely this is a problem if the package contains unicode, whats more it means the file being deployed isn't the file that is built. Thats not common practice

|||Interesting. Did you do anything special with the package?

I always get utf-8 encoded DTSX files (you are right, without encoding specified in XML clause): both the project folder and bin folder contain utf-8 encoded files. I don't know a way to make designer save utf-16 files.

Deploy to SQL Server or flat files

I'm in a quandry about how to deploy my SSIS packages and was hoping someone has some experience of the same.

There are 2 approaches: 1) Deploy to SQL Server. 2) Deploy to .dtsx files.

I suppose the default approach is to deploy to SQL Server however I have a problem with that. My packages contain Execute Package Tasks which use different connection managers depending on whether the package that they are calling is on SQL Server or in a .dtsx file.
That means that my packages have to contain 2 connection managers for each Execute Package Task - one for pointing to a package deployed to SQL Server and one for a package that is still in development and hence sitting in a .dtsx file. There is also the overhead of managing the deployment to make sure my Execute Package Tasks are pointing to the same place.

For this reason I am contemplating just leaving my packages as .dtsx files even when they are deployed to a production server.

Has anyone else encountered this problem? How have you dealt with it?
Has anyone found a distinct advantage of one approach over another?

Any comments welcome.

Thanks
Jamie

On a side note, what is the performance impact on FF deployment compared to DB?

|||Here were the responses I got from project REAL team. Wish they'd throw their stuff on the web for everyone to see how they did it.


From: Gary Cabana
Sent: Tuesday, September 06, 2005 04:13
To: Grant Dickinson
Subject:

Grant, for project REAL, you have one master workflow package that calls execute package tasks with file based connections, correct? How does this work for migrating the code from a development machine to the production box? In particular, when the package starts, are you using a configuration to set the connection string for the execute packages’ file based connection, or is it implemented such that the file locations of the packages being called cannot change?

thanks



From: Grant Dickinson
Sent: Tuesday, September 06, 2005 12:33 PM
To: Gary Cabana
Subject: RE:

Hi Gary

We originally had the file locations in the config as you have mentioned, but we realised that in our case we could use a convention of always having the files in the same place, eg c:\etl - thus the configs were redundant and I removed them. If you cannot use such a convention then the config worked fine and I'd recommend that - remember to secure the folder containing the packages if need be. I cannot comment on any experiences using the SQL store for the packages since we have not used that option in REAL.

Kind Regards

Grant Dickinson


From: Gary Cabana
Sent: Tuesday, July 26, 2005 13:44
To: Grant Dickinson
Subject: RE: Project REAL questions

One more question:

Did you use multiple packages or combine all the ETL into one giant package with multiple data flows? I’d like to use multiple packages so that development can be done in parallel.

If multiple packages, did you do the execute package in sql server or execute in the file system and why?

From: Grant Dickinson
Sent: Tuesday, July 26, 2005 5:09 PM
To: Gary Cabana
Subject: RE: Project REAL questions

Multiple - as with any code project I prefer modularity. As you say, this makes team development easier too. Currently I am using the file system, no particular reason except that it was easier since the VS project is file-based, as is SourceSafe. Let me know if you find any interesting reasons to use SQL instead.


From: Gary Cabana
Sent: Tuesday, July 26, 2005 5:13 PM
To: 'Grant Dickinson'
Subject: RE: Project REAL questions

The dev group said performance was the same.

One thing I don’t like about the file approach is that you need to create a new connection for each execute package you’re executing. Although, the current CTP 15 has the same problem for creating a new connection for each package that resides in the sql server (although Kirk said it’s a bug and I submitted it).

thanks

|||Gary,
That's superb stuff, thanks very much. If its good enough for Project REAL then its good enough for me!!

-Jamie|||The performance impact should be minimum.

The location of the package only affects the load time (i.e.
load from file vs. establish SQL connection and load from SQL table),
it does not matter during execution. For typical packages that run
several minutes to hours, the time to read package from file or
from database (less than a second, unless the server is really
overloaded) should not impact anything.

I think the decision should be driven by administative habits
and convinience. E.g. many people prefer SQL deployment
since they already backup SQL database regularly, and thus
get SSIS package backup for free. But many people backup
file system as well and prefer simplicity of file deployment.|||Package Access is another consideration when deciding the deployment option. Once Package is deployed on Sql server, User Access to the package is controlled at the database level. Whereas in the oher case its filesystem level.

For a scenario where many users are executing a package, having it on a centralized SQL server is just more simple. Esp. in case SSIS package connects to multiple databases. Its more secure rather than having connections set in a package saved on file system.|||

Suresh Bansal wrote:

Package Access is another consideration when deciding the deployment option. Once Package is deployed on Sql server, User Access to the package is controlled at the database level. Whereas in the oher case its filesystem level.

For a scenario where many users are executing a package, having it on a centralized SQL server is just more simple. Esp. in case SSIS package connects to multiple databases. Its more secure rather than having connections set in a package saved on file system.

All good reasons. However the issue regarding deployment that I mentioned earlier swings it.

Thanks all.

-Jamie

deploy SSIS package to server

Ok, I created SSIS packages on my local box. All of my packages are using config files for the db connections and other configurations that'll be changed per environment. My question is how do I deploy the .dstx file and the associated config file to the servers?

Right now I'm running the packages in BIDS as I create them. I now want to run them on an actual server

One way is to map a drive (or just open a remote folder) to the server, and then copy the files there.

I suggest you create a folder on the server to hold the SSIS stuff. From there you can create subfolders if you desire.|||

would I need to create folders for each package or no? How will the SSIS package now what config file is assocaited with it?

|||

IGotyourdotnet wrote:

would I need to create folders for each package or no? How will the SSIS package now what config file is assocaited with it?

You don't need to create a folder for each package, though that decision is up to you.

In the package (control flow, right click, package configurations), you specify which configuration file to use.

Friday, February 24, 2012

deploy sql server express to ISP

To deploy sql server express to an ISP that supports Sql Server, I backed up the .mdf and .ldf files.

I can connect to the ISP database with Sql Server Mangement Studio Express. That connection requires a password.

When I try to execute 'restore', I get an error for no permission.

Any ideas why I have no permission after a password has already been entered?

I sure appreciate any help.

You will need to contact your ISP to discover what permissions you have on thier server. If you're getting a no permission error, it means that you don't have permission to perform a RESTORE on the server. SQL security is not all or nothing, you can be assigned a whole range of permissions that each imply certain rights.

Is RESTORE the way your ISP recomends putting databases on thier system? I'd actually be kind of surprised if it was, most ISP do not give this level of permissions to thier users.

Regards,

Mike Wachal
SQL Express team

-
Check out my tips for getting your answer faster and how to ask a good question: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=307712&SiteID=1

|||

Finally --

I found a solution.

The problem was the ISP. They were not helpful at all. I quit and went to discountasp.net (yea) -- they have a tool to convert sql server express over to sql server 2005 and they have answered all of my questions within just an hour or so.

Thanks for your help Mike.

|||

Glad that it worked out for you CK. I'm also glad the discountasp.net has a tool to upload your database easily.

I'll make one minor nit just so it's mentioned in the thread. I think it's important for folks to understand that SQL Express is SQL Server 2005. There is not difference between the database files, all the same data types are supported, etc. SQL Express has fewer functions, but that's all. This is pretty normal, think about all the applications that offer a "lite" or "personal" edition with reduced functionaltiy, and then when you pay, you get additional functionality, same thing here.

You don't need to convert the SQL Express database, it's already exactly the same. The confusion stems from two issues:

Some Hosters allow you to move your database to the site using the Import/Export wizard, which isn't currently in SQL Express. This makes it hard to get your database on the server and we're working with Hosters to get the whole upload story working for SQL Express users.|||

Hi Mike, very pleased to find your post. I have a website built in VWD express, where deployment to an isp fails with this:

... (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) ...

After a rather frustrating 2 days I've arrived at the same conclusion as you suggest, that isp's do not really support sql express, and they annoyingly avoid saying so in their blurb. Yet the VWD Express deployment went just fine, so I just have to fix the SQL stuff.

From your post are you saying that SQL Express is Enterprise ManagerLite, but under the hood, its still system tables like sysobjects and so on, just inaccessible. Or is SQL Express reduced in actual scope and reach, regardless of accessibilty. I cannot find a SQL express query window on its own, it seems that the only interface is from within VWD which is sufficient, although much reduced from Enterprise Manager. This must be Lite.

Reason I ask is so that I can understand better what happens when i transfer my database (at least its contents) from my local machine to my isp. Following your logic, do my SQL Express .mdf (with or without .ldf) files attach/detach seamlessly between SQL Express and SQL 2005 and back. In which case I just have to find an isp who will allow attach/detach. Then I alter the connection string in web.config to use the server/database on the isp's machine as per MSDN. Then it should work?

Hope this brightens your day, then maybe you can shed some light ...

Charlie

|||

Charlie,

I'm sorry about your 2 days of frustration. I know exactly what you are going through. The ISP that caused me 3 weeks of frustration (1) told me on the phone before I signed up that VWD/SQL Server Express would work fine (2) sent me solutions from multiple techs that required Enterprise Manager - which is NOT available from SQL Express and (3) would not admit they didn't know.

Of course I bought into the idea that VWD is for hobbyists and lite-weights, forcing me to pass my frustrations on to this forum(!), but now that is behind me and I am a happy camper.

Here's an article that helped me: http://aspnet.4guysfromrolla.com/articles/040506-1.aspx

Deploy Reports

Hi, our programmer give me periodical a lot of .rdl and other bynaries
files, used for render reports, I must deploy all the files on several
server, how can I automate the deployment? at the moment I need to upload
all single files on every machine ! THANKS for every feedbackThis news group posting describes how to do this with a script. It's for RS
2000, but I don't think the services you run the script against has changed
so much for RS 2005. At least it should give you a place to start.
"Use rs.exe to publish ALL .rdl files in a folder"
http://groups.google.no/group/microsoft.public.sqlserver.reportingsvcs/msg/7a585606cf1f6cd0
Kaisa M. Lindahl Lervik
"MV" <MV@.MV.MV> wrote in message
news:OjEgf1DcHHA.4716@.TK2MSFTNGP02.phx.gbl...
> Hi, our programmer give me periodical a lot of .rdl and other bynaries
> files, used for render reports, I must deploy all the files on several
> server, how can I automate the deployment? at the moment I need to upload
> all single files on every machine ! THANKS for every feedback
>|||If you have VS you need to just change the target URL and deploy, that will
be an easy option otherwise write scripts for deploying. sample is given in
"PublishSampleReports.rss" samples. You can refer and change accordingly.
Amarnath,MCTS
"MV" wrote:
> Hi, our programmer give me periodical a lot of .rdl and other bynaries
> files, used for render reports, I must deploy all the files on several
> server, how can I automate the deployment? at the moment I need to upload
> all single files on every machine ! THANKS for every feedback
>
>

Deploy Problem--failed with big files!

As the subject, I want to deploy my program with visual studio 2005 and pocket pc 2003, but failed when it comes with big file(bigger than 1M).
Enviroment vs2005, pocket pc 2003, activesync4.1, .net cf 2.0.
Error message here:
Deployment and/or registration failed with error: 0x8973190e. Error writing file '%CSIDL_PROGRAM_FILES%\SQLCEResultSetSampleCS\Northwind.sdf'. Error 0x8007274c:
Thanks in advance.

AS indeed is not very good with big files, but 1 MB is not big at all. It was able to deploy NETCF V2 which is 5 times that, right?

I suspect your DB is in use and can not be overwritten. May be your application is running in background with open connection or, perhaps, you forgot to close query analyzer?

deploy pacakge - what files have to go?

I'm getting ready to deploy my SSIS packages to a real server (woohoo) after testing on my local SQL box. What files have to be deployed to the SQL server? I'm creating a folder for each package (easier for these guys to maintain when my contract is up). Does only the .dtsx and .dtsConfig file go or is there any other files that have to be copied over to the SQL server?

Only the dtsx files need to go. You can deploy individually or you can set the create deployment utility as a Project Property and then just double click the manifest to deploy all of them at once. You shouldn't have to manually copy any files.

|||

Ok, even though I have a .dtsconfig file defined for them, that doesn't have to go to the servers?

As for the .dtsx file, I see one in the Bin folder of my project and one outside of the bin folder which one goes or does the deploy utility grab the correct one?

|||

In the Deploymet folder there should be a file with the extension .SSISDeploymentManifest. Double click on that. It will deploy the files from the Deployment folder.

If you don't have a Deployment folder, right click on the project and choose properties.

In the properties page, click on the Deployment Utility entry (middle one) and change create deployment utility to True.

|||

Ok, thanks, I'll look into it. This is the first for this for me, so. .

|||

If you want to include the configuration settings from the .dtsconfig file then you should deploy it. I am 99.9 % certain that you want to include it.

The deploy utility will grab the correct .dtsx file.

|||

From my experience (not very much though ), its easier to do a xcopy than going through the process of creating deployment package modifying the manifest etc., That way you wont miss copying the config files also.

Its just my thought.

Thanks

Tuesday, February 14, 2012

dependacy files of sql server for deployment setup applicaton

Respected Sir
this thing I knew 2 year later, unfortunately forget and missplace

I want to not depend on sql server 2000 clients , can I include some dll s in my vb6 setup sothat I may not depend on sql server client to install all my clients
I want to add dependancy files of sql server in my deployment setup of application written in vb6 ans sql server
plz help me
Can anybody provide liste of these filesConnectivity to SQL Server should be enabled in baseline installs of Windows XP, Windows 2000, Windows 2003 and may be part of Windows NT SP4 (can't remember and it's been a while).

In Windows XP, 2000 and 2003 you can type cliconfg at a command prompt to get the SQL Server Client Configuration utility; I don't believe that any install of SQL Client tools is required.

You should be able to test/validate connectivity by creating a simple text file, rename it to [something.UDL] and then double clicking on it to start the Universal Data Link wizard. Set the parameters (SQL Server driver, SQL Server name, user name, password and default database) and then click on the Test Connection button.

Regards,

hmscott