I cannot use the watch window while debugging. I want to use it to look at the runtime variable values. The watch window is blank when I click on it, could someone please tell me where and how to configure it?
I need an example of a WQL query to use in the WMI Event Watcher task to watch for the presence of a file. The task has to succeed for either:
1) The file already exists when the task is run
2) The file shows up while the task is running (waiting)
Also the query has to reference a UNC path and file name. The file I'm looking for is just a flag file telling me a table is refreshed in our Data Warehouse.
I also need pointers on how to set the WMI connection manager. For the server, do I use the \servername of the fileserver? Do I need to include the folder the files are in (eg. \servernameflags)?
I have a folder that gets 2 to 3 files dropped everyday. I want to create a package that loads only the new files into the database. The old files (Processed files) remain in the same folder and cannot be moved. How do i accomplish this in ssis?
I found something about the file watcher task with the for loop, but just can't put it all together.
between my wrox book, google and looking everywhere in BIDS, I couldn't figure out how to watch the variables being set in an Exec SQL Task control flow item. My wrox book said something about right clicking the var in the script (I wasnt in a script), or using the debug menu or pressing ctrl-alt-q. None of this worked. Is it possible that at installation a certain choice wasnt made, or maybe watch windows only work in the context of something other than the control flow?
I've got an order generation query that will _sometimes_ run long. By that I mean every few days a query used to estimate the required stock quantities for an order will time-out because it has taken an extended time to run. This only occurs at one particular site. This site shares a common schema with others who do not experience this issue, although site is a particularly busy one.
This query (a stored proc call) needs to aggregate sales data from ~200k rows and usually takes 10-15 seconds. On the days when it 'runs long' it will hit the 5 minute time-out period and be failed by the application.
The problem I have with this process is that if I have the application dump out the query it's using to generate the order (this query will vary as the stored proc is passed the name of a temp table to use for this order) so I can run it in Query Analyzer to get an execution plan and maybe some clue as to why it takes so long; the issue will vanish. After I've tried to investigate in this way an order generated from either Query Analyzer or the application will work in the normal time. When the query is running long any processes which attempts to write to the sales data tables will get blocked until the order generation has finished.
The application is accessing the database via ADO 2.6. The database itself is running on SQL Server 2000 sp3 under Win2k.
I believe that the SQL Profiler is the tool best suited to investigate this but I'm hoping for some advice on which of the myriad of watchable metrics I should be checking here.
Any profiler advice or estimates as to what the issue may be here would be great!
Not sure if this is a "user training" issue or a bug, I seem to have difficulty dragging and dropping variable(s) to the watch window. Is there a specific sequence I need to follow to enable this feature in BIDS? Appreciate any feedback.
When i debug a trigger is it possible to add a WATCHon the INSERTED or DELETED?I think not, at least I couldn't figure out a way to do so.Does someone have a suggestion on how I can see the values?I did try to do something likeINSERT INTO TABLE1(NAME)SELECT NAME FROM INSERTEDbut this didn't work. When the trigger completed and Iwent to see the TABLE1, there were no records in it.Are there any documents, web links that describe waysof debugging the trigger's INSERTED and DELETED?Thank you
Can't an SSIS package run "in the background", so to speak, without having either the cmd.exe or dtexecui windows open while executing? I'd obviously rather not have to have a window open when the thing is running right?
I am attempting to write a Windows service that watches a database for uploaded files to import. When a new file is found, the corresponding SSIS package is run from the file system with variables passed through. I started development as a Windows app and copied the functionality to a service.
The app runs fine. The service does not. I get a "Failure" each time a package is executed. Everything is identical behind the scenes with the obvious exceptions that OnStart and OnStop handlers are buttons in the app. I added a script task at the beginning of one of the SSIS packages to notify me that it is even running at all. It doesn't even hit that initial task.
Again, the app will run all packages just fine. The data is imported and the results return as "Success."
The following is the code executing the package. Any help is appreciated. I've been banging my head on this one for a few days now. (Is there a tag to format a code sample?)
Dim pkgLocation As String Dim pkg As New Package Dim app As New Application Dim pkgResults As DTSExecResult
Have two C# applications - one WinForms desktop app, the other a WinForms smart device app. Both use SQL Server Compact CE 3.5 to store data locally. Both work just fine.
Now the desktop app needs to open and update the .SDF file that is stored on the Windows Mobile device. (Device will be docked via USB.)
What format would the path to the .SDF look like that the WinForms application would need to specify in order to open it?
I just upgraded from Windows XP Pro to Windows Vista Bussiness and tried to reinstall SQL Server 2005 Developers Edition. After the installation i downloaded (using microsoft windows update) and installed all the service packs for sql and vista available.
My problem is when i open sql server management studio and try to connect to my default instance using windows authentication and database engine, an 18456 error occurs.
I enabled all the protocols and all the ports I disabled windows firewall and antivirus (eset nod32) I installed all service packs available I have also installed Visual Studio 2005 without installing sqlexpress
But nothing happens!
Please i am very desperate, any information will be gratefully accepted.
This is my installation Information
Code Snippet
Microsoft SQL Server Management Studio 9.00.3042.00 Microsoft Analysis Services Client Tools 2005.090.3042.00 Microsoft Data Access Components (MDAC) 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft MSXML 3.0 5.0 6.0 Microsoft Internet Explorer 7.0.6001.18000 Microsoft .NET Framework 2.0.50727.1434 Operating System 6.0.6001
Hi all,I have a Windows 2003 server, which is also a terminal server forapplication, with sql 2000 installed. My company has developed anapplication that uses SQL 2000 as its database. The application is aclient/server one. In each client computer there's a link to theapplication on the server. There is no problem with Windows 98,Windows 2000 pro, Windows xp pro clients, but the windows 95 onescannot log in to the database. The log of the application shows thefollowing error:connection error -2147467259. Cannot open database requested in login'database name'. Login fails.Till a week ago the application was running on a Windows 2000 serverwith SQL 2000 install and the W95 clients had no problem connecting tothe database, so my guess is the error has something to do withWindows 2003 server, but what'causing the error?I tried to install a newer version of MDAC (MDAC 2.5, the last versionof MDAC you can install on W95)but with no success. By the way W95clients have no problem accessing shared folder on the Windows 2003server.Any idea?ThanksMarino
We just moved the back end of an Access db to an SQL server and upgraded to Access 2000. A strange problem has arisen. The execution of a query in a certain function seems to be causing the function to prematurely terminate (that is, the query does not complete, and the function does not execute beyond the execution of the query). This error occurs only on workstations loaded with Windows 98. Windows 2000 users are unaffected, and the function runs uninterrupted. The query in question contains date parameters. On the SQL server, dates are enclosed in single quotes (')'s, whereas in Access they are enclosed in pound signs (#)'s. When a query is sent by Access to the SQL server, it is filtered through a program that converts the Access format to SQL-friendly code. Our theory is that this process fails to occur on the machines running Windows 98. Does anyone know why this is occuring?
We have an installation of MS SQL Server (MSDE actually) runnning on a group of Windows 2k machines. Due to IT constraints at the customer site, we are using Windows authentication, but it is all done with local user accounts, not domain accounts.
We have the same user account witht he same password locally created on each machine. This works fine with all the Win2K machines (not the best solution, but under the client's insane IT department, it's all we were allowed to do).
The problem is that we tried to add an XP machine. While we can connect to a DB running on a 2K machine from the XP workstation, the XP system will not accept connections from the 2K systems. We have done a little research and think we have found out why- the 2K systems are sending usernames for authentication, but the XP is looking for the UID- which is different on every system.
We cannot go to SQL authentication, and we cannot use Domain authentication. Is there a way to change XP to authenticate from username instead of UID?
I have been trying to install MS SQL Enterprise V7 on Windows ME the first time it worked but then it stopped with a Connection error message, ever since then I have tried and tried to install it properly but it keeps giving the same connection error.I've successfully installed it on NT and 2000 adv server, so what gives I'm I barking up the wrong tree will MS SQL not install on ME?Or I'm I missing something
My SQLExpress seems to be set for windows authentication and not sql server authentication ... I am not quite sure why it is set to windows authentication - I installed this with Visual Studio 2005 and it just seemed to be set that way.Am I able to change this - if I choose sql authentication when connecting I get an errorIf someone could answer this point I would be most grateful !!Patrick
My machine is running Windows 98. I want to install window 2000 in order to enable me work with SQL Server 2000. Please what is the best way to go about it. Do I use an Upgrade or do I uninstall Windows 98 and install Windows 2000. Thanks for your help!!!!!
Does anyone know how SQL Server works with Active Directory users? Specifically, I'm wondering if I'm going to encounter problems if our Windows 2000 environment is setup with multiple forests. I'm assuming as long as there's a trust between the forests, SQL Server will be able to authenticate.
Need to install SQL 7 under windows 2000 (professional version), thought it should be. However, in the install (Standard) process, first msgbox "You could only have client utility". Hit 'OK' to ignore this message, and the whole installation finished completely.
Issue: could not register the server name of 'SQA-Test1' nor connect through the isql/w. Thus, not quite sure the relationship between SQL 7 and Win2000.