Not sure if I am posting this in the right area. I have been assigned as a project leader for a new software project that will control all aspects of our business. I am mildly familiar with databases and how they work. We are a internet based retailer with 25 million $ in annual sales with the anticipation of growing that number 4 fold within 5 years. Our website is currently run on a SQL database. The two platforms we are considering include a custom application that is built on SQL. The other option is a product that is used in fields similiar to ours but the company has limited experience in creating a application to coexist with our Web data. This product will be tailored to fit our needs. My real question is how does Universe compare to SQL. Is there anything I should be concerned with eitheir database? Thank you for your input as this issue has divided the ranks on this project.Don't know much about UniVerse.
As with most established relational databases they can cope with most requirements if designed and implemented properly. The most important feature is the experience of the team.
There is a lot to be said for sticking to a single platform as this does not dilute the expertise - and means that you don't need to hire two sets of experienced staff.
Anyone who has spent several years dedicated to implementation on a single platform is likely to be more competent than someone who claims equal expertise in several as long as they have had exposure to several systems and environments.
Showing posts with label software. Show all posts
Showing posts with label software. Show all posts
Wednesday, March 28, 2012
MS Sql Server User ID, Password and connection string
Hi;
I am making a software (.Net) which is going to connect a ms sql server but I cant conect yet :(.
1- I dont know what I have to type for user id (name)
2- What is my password, it has been long time that I hvae installed it but I dont need any password with Microsoft SQL Server Management Studio Express which has windows authentication option. My software can work via internet or network. So I need to know my user name and password. I am using oledbconnection. Do I need any password?
3- I visited www.connectionstrings.com already so I have the format of it.
Thanks very much for any help...you need to either use your windows account and use the example from connection strings dot com that uses windows auth or you need to go to SQL Server management studio to create a sql server login and password and you will need to give that account access to the specific database you are accessing.
man do the redskins suck.
I am making a software (.Net) which is going to connect a ms sql server but I cant conect yet :(.
1- I dont know what I have to type for user id (name)
2- What is my password, it has been long time that I hvae installed it but I dont need any password with Microsoft SQL Server Management Studio Express which has windows authentication option. My software can work via internet or network. So I need to know my user name and password. I am using oledbconnection. Do I need any password?
3- I visited www.connectionstrings.com already so I have the format of it.
Thanks very much for any help...you need to either use your windows account and use the example from connection strings dot com that uses windows auth or you need to go to SQL Server management studio to create a sql server login and password and you will need to give that account access to the specific database you are accessing.
man do the redskins suck.
MS SQL SERVER Software
Please can someone lend me a help, i need MS SQL SERVER personal Edition i mean the software..i will like to have it if someone can show me a place i can download it from or betters till can attached the file to me.. uchedealsreal@.gmail.com i will be greatfull.I think you want to download SQL Server 2005 Express from Microsoft. It is a free download. Be sure to get Visual Studio Express Manager as well.|||i would prefer personal editon 2000|||why bother with 2000? it's only supported for another year or so.sql
Friday, March 9, 2012
MS SQL conflicting with other DB Engines.
Hello All,
I work for a company that packages MSDE and MSSQL 8.0 because our software requires storing client information in a database. The problem is that we've found that if the our users have another DB engine installed (BDE or Paradox usually), our program has trouble using MSDE to access the database and thus making our software inaccessible. It behaves as if this other database engine locks on our database before MSDE can. I'm basically looking for help on either how to uninstall these other db engines or how to get around this problem so that both MSSQL and other db engines can co-exist in one system.I'd try to dump the data out of the other database to some type of file then import it in to sql server. Just a thought|||Thanks for the idea garrydawkins but unfortunately that's not an option we have.|||Does SQL Server have to be installed on everyone's desktop? Can it not be installed on a dedicated server, and everyone who uses your software can utilize this single instance?|||depends on the chosen environment, we have the ability to use a machine as a dedicated server, unfortunately, servers are used as servers. If they are serving our product, they are serving the conflicting product. We also have a lot of "stand-Alone" Clients. Not an option here either. Sorry for being difficult. :(|||Wow.. so the Stand-Alone clients, and the distributed clients both require the full install of SQL Server? Sounds overkill for the Stand-Alone. One idea might be to use Access for the Stand-Alone implementations, and SQL Server for the distributed clients. That might require significant recoding of the install, and the app (to execute SQL vs Access specific statements), but it would probably solve the problem.
At the same time, it would reduce the cost of your Stand-Alone version (since they won't have to purchase a commerical SQL Server license), be cheaper for your clients, giving you an edge over your competators.|||I work with Geeneus,
ok, the MSDE (MSDE 2000) is only running on the server, the workstations are not required to be running the server app(sorry about being unclear about this). This in turn, explains why a stand-alone is required to run it as well. Turning the client app to Access is a leap backwards, and not needed. The symptom we are experiencing, is that another database app is grabbing a hold of our database before MSDE can grab it. I suspect BDE (Borland), Paradox, Delphi (also Borland), etc...is just reacting faster and putting a lock on the database even though it is not using it. I know that this BDE can come from many sources, the most common being things like the "Corel" office suite. Anything from Oracle will be using Delphi. Any suggestions?
Xero|||I don't care for Access either, I understand, just trying to think of an option that wouldn't have you writing your own :). Is it possible this other app is running as a service? In which case you could simply disable the process.|||yea, thats my assumption. I am having huge troubles locating the offending app/service. BDE tends to hide. In most cases the MSDE will install. It is when we try to run the configuration scripts to attach the database is when it blows up. Something allready installed has grabbed ahold of it and locked it.|||Good News!!
Reverend managed to figure out how to work around the problem. I'll let him explain it but just wanted to give you all the good news!!|||I have discovered a conflict btween what was called MQIS (MSMQ), and is now Active Directory. This MQIS thing came with early versions of Windows, i.e. Win95, Win98, and NT4. It has an installed backbone of SQL 6.5. If, throughout its lifetime, any of these components have been removed, then this issue can arise. Identification can be made by Start -> Programs -> Startup. I have noticed that the MSDE will show as "Service Manager" and the other instance will be called simply SQL Server. Remove SQl server from startup and run your configuration scripts. viola. Be advised that the next time this client runs any exe that calls for that old SQL Server (app in the case of win9x) it will be reactivated in startup and cause this nightmare again.
Have also seen strange(same) behavior while trying to install the MSDE after the newest version of quickbooks is installed.|||stupid user tricks:Install MSDE to a win98 machine, upgrade to WIN2k or WINXP. Now the database can not be read by the MSDE.
I believe that the MSDE installes as a application, when you roll up to xp or 2k, you suddenly have services and POOF! we get blown out of the water.
anyone had any experience with this and have a workaround/fix?|||Install MDAC 2.7 then uninstall the MSDE. Then reinstall the MSDE, it will now install as a service rather than an application. (This was tested from 98 to XP, 2000 is still unknown) Then run any attach/repair scripts (ours run auto in our installer).
-Frank
I work for a company that packages MSDE and MSSQL 8.0 because our software requires storing client information in a database. The problem is that we've found that if the our users have another DB engine installed (BDE or Paradox usually), our program has trouble using MSDE to access the database and thus making our software inaccessible. It behaves as if this other database engine locks on our database before MSDE can. I'm basically looking for help on either how to uninstall these other db engines or how to get around this problem so that both MSSQL and other db engines can co-exist in one system.I'd try to dump the data out of the other database to some type of file then import it in to sql server. Just a thought|||Thanks for the idea garrydawkins but unfortunately that's not an option we have.|||Does SQL Server have to be installed on everyone's desktop? Can it not be installed on a dedicated server, and everyone who uses your software can utilize this single instance?|||depends on the chosen environment, we have the ability to use a machine as a dedicated server, unfortunately, servers are used as servers. If they are serving our product, they are serving the conflicting product. We also have a lot of "stand-Alone" Clients. Not an option here either. Sorry for being difficult. :(|||Wow.. so the Stand-Alone clients, and the distributed clients both require the full install of SQL Server? Sounds overkill for the Stand-Alone. One idea might be to use Access for the Stand-Alone implementations, and SQL Server for the distributed clients. That might require significant recoding of the install, and the app (to execute SQL vs Access specific statements), but it would probably solve the problem.
At the same time, it would reduce the cost of your Stand-Alone version (since they won't have to purchase a commerical SQL Server license), be cheaper for your clients, giving you an edge over your competators.|||I work with Geeneus,
ok, the MSDE (MSDE 2000) is only running on the server, the workstations are not required to be running the server app(sorry about being unclear about this). This in turn, explains why a stand-alone is required to run it as well. Turning the client app to Access is a leap backwards, and not needed. The symptom we are experiencing, is that another database app is grabbing a hold of our database before MSDE can grab it. I suspect BDE (Borland), Paradox, Delphi (also Borland), etc...is just reacting faster and putting a lock on the database even though it is not using it. I know that this BDE can come from many sources, the most common being things like the "Corel" office suite. Anything from Oracle will be using Delphi. Any suggestions?
Xero|||I don't care for Access either, I understand, just trying to think of an option that wouldn't have you writing your own :). Is it possible this other app is running as a service? In which case you could simply disable the process.|||yea, thats my assumption. I am having huge troubles locating the offending app/service. BDE tends to hide. In most cases the MSDE will install. It is when we try to run the configuration scripts to attach the database is when it blows up. Something allready installed has grabbed ahold of it and locked it.|||Good News!!
Reverend managed to figure out how to work around the problem. I'll let him explain it but just wanted to give you all the good news!!|||I have discovered a conflict btween what was called MQIS (MSMQ), and is now Active Directory. This MQIS thing came with early versions of Windows, i.e. Win95, Win98, and NT4. It has an installed backbone of SQL 6.5. If, throughout its lifetime, any of these components have been removed, then this issue can arise. Identification can be made by Start -> Programs -> Startup. I have noticed that the MSDE will show as "Service Manager" and the other instance will be called simply SQL Server. Remove SQl server from startup and run your configuration scripts. viola. Be advised that the next time this client runs any exe that calls for that old SQL Server (app in the case of win9x) it will be reactivated in startup and cause this nightmare again.
Have also seen strange(same) behavior while trying to install the MSDE after the newest version of quickbooks is installed.|||stupid user tricks:Install MSDE to a win98 machine, upgrade to WIN2k or WINXP. Now the database can not be read by the MSDE.
I believe that the MSDE installes as a application, when you roll up to xp or 2k, you suddenly have services and POOF! we get blown out of the water.
anyone had any experience with this and have a workaround/fix?|||Install MDAC 2.7 then uninstall the MSDE. Then reinstall the MSDE, it will now install as a service rather than an application. (This was tested from 98 to XP, 2000 is still unknown) Then run any attach/repair scripts (ours run auto in our installer).
-Frank
Monday, February 20, 2012
MS SQL - Query Analyzer by IP range
I need to run reports from our database that stores IP addresses when a software license is used. So, I need to know how to run SQL queries to retrieve certain IP addresses from specified ranges. For example:
192.168.1.0 - 192.168.2.255
192.168.3.11 - 192.168.7.128
10.10.10.8 - 10.10.12.255
What commands would help me accomplish pulling all IP addresses in a range. I know I would have to run multiple reports for each range. I tried using the "between" function and "less than/greater than" functions, but I received mixed results. For example:
SELECT * FROM testtable WHERE ip LIKE '192.168.[1-2].[0-255]'
I also tried -
SELECT * FROM testtable WHERE ip>'192.168.1.0' and ip<'192.168.2.255'
Any help would be greatly appreciated! Thanks in advance!Parse your IP addresses into four separate columns. That would make it easy to search or filter by ranges.|||blindman, thank you for the feedback... however, the original DB configured the IP address as it's own field... at this point, there is over 10million or so records, so modifying the DB would be time consuming... any other thoughts would be greatly appreciated...|||Create a function called IP2DWord or so. Its pretty straigtforward. First octet * 256^3 + second octet * 256^2 + third octet*256 + fourth octet. If you use this function on both starting and ending address you can easily select ranges.|||Define: "time consuming"? ;)
There have been a number of questions about IP addresses in a range - I suggest you search the forum www.dbforums.com/search.php and there were some very good suggestions around and about (see above ;)).|||roac, i looked into your suggestion and it seems to be the way to go... thnx all for the feedback...|||If you parse the IP address on the fly using a function, then you can toss any indexing out the window. On 10,000,000+ records don't expect a great response time.
You asked for advice, and I gave it. You are FAR better off parsing the IP Address into four separate columns in your table. You can index them, and you only need to parse each address once. If you absolutely have to have the IP Address as a single column in your table, then keep it and create four additional columns in the table that you populate automatically using insert/update triggers.
You can do this right, or you can do this wrong. You can take shortcuts now, or you can save programming, debugging, and execution time over the life of the application.
'Nuff said.|||For reporting purposes it is required for the IP address to be in 1 column. I will look into separating each IP segment into it's on column, as I agree there's more flexibility when running reports specifically for IP ranges.|||For reporting purposes it is required for the IP address to be in 1 column.Reporting purposes do not require the data to be in one column. A view, sproc, or SQL statement can easily combine the components for reporting.
192.168.1.0 - 192.168.2.255
192.168.3.11 - 192.168.7.128
10.10.10.8 - 10.10.12.255
What commands would help me accomplish pulling all IP addresses in a range. I know I would have to run multiple reports for each range. I tried using the "between" function and "less than/greater than" functions, but I received mixed results. For example:
SELECT * FROM testtable WHERE ip LIKE '192.168.[1-2].[0-255]'
I also tried -
SELECT * FROM testtable WHERE ip>'192.168.1.0' and ip<'192.168.2.255'
Any help would be greatly appreciated! Thanks in advance!Parse your IP addresses into four separate columns. That would make it easy to search or filter by ranges.|||blindman, thank you for the feedback... however, the original DB configured the IP address as it's own field... at this point, there is over 10million or so records, so modifying the DB would be time consuming... any other thoughts would be greatly appreciated...|||Create a function called IP2DWord or so. Its pretty straigtforward. First octet * 256^3 + second octet * 256^2 + third octet*256 + fourth octet. If you use this function on both starting and ending address you can easily select ranges.|||Define: "time consuming"? ;)
There have been a number of questions about IP addresses in a range - I suggest you search the forum www.dbforums.com/search.php and there were some very good suggestions around and about (see above ;)).|||roac, i looked into your suggestion and it seems to be the way to go... thnx all for the feedback...|||If you parse the IP address on the fly using a function, then you can toss any indexing out the window. On 10,000,000+ records don't expect a great response time.
You asked for advice, and I gave it. You are FAR better off parsing the IP Address into four separate columns in your table. You can index them, and you only need to parse each address once. If you absolutely have to have the IP Address as a single column in your table, then keep it and create four additional columns in the table that you populate automatically using insert/update triggers.
You can do this right, or you can do this wrong. You can take shortcuts now, or you can save programming, debugging, and execution time over the life of the application.
'Nuff said.|||For reporting purposes it is required for the IP address to be in 1 column. I will look into separating each IP segment into it's on column, as I agree there's more flexibility when running reports specifically for IP ranges.|||For reporting purposes it is required for the IP address to be in 1 column.Reporting purposes do not require the data to be in one column. A view, sproc, or SQL statement can easily combine the components for reporting.
Subscribe to:
Posts (Atom)