|
<pre lang="sql">SELECT *
INTO OPENDATASOURCE('SQLNCLI',
'Data Source=.\sqlexpress;User ID=sa;Password=sa')
.[fuzzyTest].dbo.tblGroup
FROM [CMS].[Common].[File];</pre>
This is not working and giving error !
I dont wanna to use
<pre lang="sql">INSERT INTO [CMS].[Common].[File]
(Name,IdParent,[Desc])
SELECT [Name],[IdOstan]+30,''
FROM OPENDATASOURCE(
'SQLOLEDB',
'Data Source=.\sqlexpress;User ID=sa;Password=sa'
).[fuzzyTest].dbo.tblGroup</pre>
modified 27-Nov-13 1:02am.
|
|
|
|
|
jojoba2011 wrote: This is not working and giving error !
What error? Syntax error?
jojoba2011 wrote: I dont wanna to use
Why? What's wrong with that?
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
I am using an ODBC to transfer the data from a view I made in postgresql into excell.
in my query I have 2 parameters that define the the date range but I was wondering if there is a way to set it up so that the ODBC can get these date parameters and look for the info pertaining to the dates I demand?
By which I mean, say my query got the data for 2013 because I have
and account_invoice.date_invoice >=
and account_invoice.date_invoice <=
as conditions, but I would like to be able to give the ODBC a range from january 1st to January 30th and get the data in that range.
|
|
|
|
|
Member 10427697 wrote: but I would like to be able to give the ODBC a range
ODBC is merely the driver; you'd need to change the query that's executed (SELECT * FROM VIEW?) to include a WHERE clause.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
my 2 conditions are part of the where clause
I have it like
where bla bla
and
and
and...
but if I do it for a month I will ahve to change the query everytime I want to get the data for the next month, I want to know if its possible to make it work automatically.
|
|
|
|
|
Member 10427697 wrote: I want to know if its possible to make it work automatically
Of course it is, think about it, you want the dates of the previous month calculated based on the current date. I'm absolutely certain PostGres has datetime functions similar to SQL Server.
Alternatively you can pass in the 2 date parameters from the calling method.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Definitely not sure if I understood your question correctly, but have a look at the prepare[^] command.
Just remember to add UseServerSidePrepare=1 to the odbc.ini if you want to use the added performance.
Politicians are always realistically manoeuvering for the next election. They are obsolete as fundamental problem-solvers.
Buckminster Fuller
|
|
|
|
|
i have two tables (employee,attendance)
employee feilds:-
empno(pk),idno,,empname,compname,deptname all data type varchar(50)
attendance feilds:-
idno(pk),empno,intime,outtime,remarks all data type varchar(50)
my task is enter the value in textbox then check the data baseofter then display the remaining text box filling by using idno how to get the values in two tables
thank's
|
|
|
|
|
What do you enter in your textbox? You just need a sql statement to draw data from database?
|
|
|
|
|
Member 10263519 wrote: thank's
for what, you have stated your school work but not asked a question unless you do something and ask a question when you need help we can't do anything to help you.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Member 10263519 wrote: all data type varchar(50)
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Hi Everyone!
All of a sudden we are seeing the above error message, in one of our automated jobs. This job runs at 3am everyday.
This error occurs on random days, not on a regular basis.
There is not much out on this particular error.
The temp table is defined in a stored procedure.
Thanks!!!
|
|
|
|
|
Not enough information to diagnose.
|
|
|
|
|
vkEE wrote: All of a sudden we are seeing the above error message, in one of our automated jobs.
I've never encountered a PC that "suddenly" interprets code in a different way.
vkEE wrote: This error occurs on random days, not on a regular basis.
..nor does it pick random days to crash. Find out what those days have in common; check if there's exceptional heavy traffic on the network during those days. Check your firewall-log. Check the schedule of your backups, automatic updates and virusscans; are they similarly "random"?
Are you sure you got the correct type of temporary table? There's subtle differences between #tmpTable, ##tmpTable and @tmpTable.
vkEE wrote: The temp table is defined in a stored procedure.
Post the code of the stored procedure and you'll get more and better replies.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Thank you for your response.
The job runs at 3am just for that reason, so we don't have resource issues. It has crashed 3 times the past few months, but our seniors want this matter researched since it is a new bug in their test environment. They don't want this bug to migrate to production environment.
I got this error message of the log file, and it is defined with single hash, #.
|
|
|
|
|
vkEE wrote: <layer>our seniors want this matter researched since it is a new bug in their test environment. They don't want this bug to migrate to production environment.
Unless you are in full control of your environment and able to debug every device-driver, some bugs will remain unsolved.
vkEE wrote: It has crashed 3 times the past few months
Do you know at what time? Anything in the event-log at that specific time? Does it run under .NET 4? If yes, you could consider making a minidump.
vkEE wrote: and it is defined with single hash, #.
I was hinting at researching the three. Whether it's the correct one will depend on the context of it's use in the stored procedure. You will have to verify the things mentioned, and again, you'd get a more usefull answer if you provide the code for the stored procedure.
There are two types of temporary tables: local and global. They differ from each other in their names, their visibility, and their availability. Local temporary tables have a single number sign (#) as the first character of their names; they are visible only to the current connection for the user, and they are deleted when the user disconnects from the instance of SQL Server. Global temporary tables have two number signs (##) as the first characters of their names; they are visible to any user after they are created, and they are deleted when all users referencing the table disconnect from the instance of SQL Server. ..and it becomes more confusing[^] if you are EXECUTEing dynamic SQL.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
vkEE wrote: The temp table is defined in a stored procedure.
You have an execution path that is skipping the creation of the table but then attempting to use it.
|
|
|
|
|
Hi all,
I have a little confusion about creating index on Oracle, which is the difference between creating index online and creating them in not an online way (offline).
I looked it on internet and I did not find sth straight about it but I guess that :
Online : The RDBMS will create the Index without using table locks (for DML statements when creating the index).
Offline : create with the use of tables lock.
Am I correct ?
Thank you.
"The Ultimate Limit Is Only Your Imagination."
|
|
|
|
|
Yes.
Politicians are always realistically manoeuvering for the next election. They are obsolete as fundamental problem-solvers.
Buckminster Fuller
|
|
|
|
|
when i wanna to get script from my DB in sql server management 2008 i get this error :
There is already an open DataReader associated with this Command which must be closed first.....what is meann of this error
note :
1.even i stop start the instance.
2.copy the DB to other system also but same error !
thanks in advnaced !
|
|
|
|
|
This is not a sql error, it is in your code. You are opening a second connection before closing the first connection either using async calls or creating a new instance of your DAL class.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Mycroft Holmes wrote: You are opening a second connection before closing the first connection
A second connection wouldn't cause a problem. It's opening a second DataReader on the same connection which causes this error.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
You are trying to open two DataReader instances (by calling ExecuteReader) on the same connection at the same time. You need to make sure that every DataReader is closed properly by wrapping it in a using block, and that you close one before trying to open another.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
You can if you're using multiple Active Result Sets[^] on an SQLServer, and on Oracle you can anyway[^].
Politicians are always realistically manoeuvering for the next election. They are obsolete as fundamental problem-solvers.
Buckminster Fuller
|
|
|
|
|
One of my Stored Procedures was using ۀ in its name and when i am getting script it was giving error!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
