Showing posts with label msde. Show all posts
Showing posts with label msde. Show all posts

Friday, March 23, 2012

I want to run .sql file in MSDE

I want to run .sql file without using query analyzer in sql server
how to do thatBoth osql.exe and isql.exe are command prompt utilities from which you can run .sql files or sql-commands.

Monday, March 19, 2012

I want a default value of space

I'm using MSDE and I'd like to set a default value of a space (or spaces), and in design-view, it lets me enter a space. But it is interpreted as an empty-string "" which gets converted to Nulls when it is moved to another string field? I'm not sure why. Is there any way around this?
Are wrapping it in quotes?|||In testing, no matter what I do I cannot make SQL Server assign thedefault value of a single space or multiple spaces to a column. It always assigns an empty string. For reference, this is what Iam indicating for the default value:
(' ')
I thought it might have had to do with the varchar data type, so Ichanged it to char and had the same result. I am also stumped.
|||

It's nice to know I'm not alone. I'm doing the same - wrapping it in quotes. The problem is - it is interpreted as hex '00' when I move it to another string (which is part of a record I'm transmitting to a remote server) and this server can not handle NULL values. So unless I find a solution, I have to convert all with "empty-string" to " " before I send them. ouch.

If you find a solution, please let me know and I'll do the same.

Thanks,

John Pavelka

I upgraded from MSDE to 2005 Express, now my apps get 'login faile

All of my RDO (2.0) connections are getting this error:
Login failed for user 'my_user'
All of my apps that use ADO are working fine.
I know the userid/password are correct because I use the same ones with my
ADO apps. Does anyone have any ideas?
Thanks in advance!
apf
Nevermind! The root of my problem was - passwords are case sensitive in
2005! If anyone knows how to turn this "option" off, I would appreciate it.
|||It can't be turned off. It was part of improving password strength to
improve security of SQL logins.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"apf" <apf@.discussions.microsoft.com> wrote in message
news:2786F0F5-CBDB-4B3A-AAC4-67AADE6A4CF0@.microsoft.com...
> Nevermind! The root of my problem was - passwords are case sensitive in
> 2005! If anyone knows how to turn this "option" off, I would appreciate
> it.
>

I upgraded from MSDE to 2005 Express - now my apps get login faile

All of my RDO (2.0) connections are getting this error:
Login failed for user 'my_user'
All of my apps that use ADO are working fine.
I know the userid/password are correct because I use the same ones with my
ADO apps. Does anyone have any ideas?
Thanks in advance!
apfSorry for posting in the wrong forum!
The answer, by the way, is passwords are case sensitive in SQL Server 2005.

I upgraded from MSDE to 2005 Express - now my apps get login faile

All of my RDO (2.0) connections are getting this error:
Login failed for user 'my_user'
All of my apps that use ADO are working fine.
I know the userid/password are correct because I use the same ones with my
ADO apps. Does anyone have any ideas?
Thanks in advance!
apf
Sorry for posting in the wrong forum!
The answer, by the way, is passwords are case sensitive in SQL Server 2005.

I upgraded from MSDE to 2005 Express - now my apps get login faile

All of my RDO (2.0) connections are getting this error:
Login failed for user 'my_user'
All of my apps that use ADO are working fine.
I know the userid/password are correct because I use the same ones with my
ADO apps. Does anyone have any ideas?
Thanks in advance!
apfSorry for posting in the wrong forum!
The answer, by the way, is passwords are case sensitive in SQL Server 2005.

Monday, March 12, 2012

I think it would be nice if ...

I think it would be nice if MSDE had an interactive installation dialog.
Just launch Setup.exe and and have it ask the questions it needs and have it
check the computer for proper settings and prerequisites.
I'm not really complaining. MSDE is awesome when you consider that it's
free. It just seems that it would save alot of people time and money if
installations and uninstalls were user-friendly and a more "bullet-proof".
If Microsoft is unwilling to do this, are there any 3rd party developers out
there willing to give it a try?
hi Burton,
"Burton Roberts" <bhroberts52@.adelphia.net> ha scritto nel messaggio
news:O$KXWYoEEHA.576@.TK2MSFTNGP11.phx.gbl...
> I think it would be nice if MSDE had an interactive installation dialog.
> Just launch Setup.exe and and have it ask the questions it needs and have
it
> check the computer for proper settings and prerequisites.
> I'm not really complaining. MSDE is awesome when you consider that it's
> free. It just seems that it would save alot of people time and money if
> installations and uninstalls were user-friendly and a more "bullet-proof".
> If Microsoft is unwilling to do this, are there any 3rd party developers
out
> there willing to give it a try?
>
I was considering the same thing...
please send your feedback to sqlwish@.microsoft.com
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.6.0 - DbaMgr ver 0.52.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||"Burton Roberts" <bhroberts52@.adelphia.net> wrote in message
news:O$KXWYoEEHA.576@.TK2MSFTNGP11.phx.gbl...
> I think it would be nice if MSDE had an interactive installation dialog.
> Just launch Setup.exe and and have it ask the questions it needs and have
it
> check the computer for proper settings and prerequisites.
> I'm not really complaining. MSDE is awesome when you consider that it's
> free. It just seems that it would save alot of people time and money if
> installations and uninstalls were user-friendly and a more "bullet-proof".
> If Microsoft is unwilling to do this, are there any 3rd party developers
out
> there willing to give it a try?
Why not do what we have done and write a front end that simply allows you to
sepcify the various command params for the msde installer and then runs it
passing them on? You still get the command prompt window appear. But the
setting of the options is a whole load easier.

>
|||Hey Tim do you have a sample of that ?
Paul
"Tim Bird" <tsbdoulos@.nospambtopenworld.com> wrote in message
news:%23RTaQ1oEEHA.2076@.TK2MSFTNGP09.phx.gbl...
> "Burton Roberts" <bhroberts52@.adelphia.net> wrote in message
> news:O$KXWYoEEHA.576@.TK2MSFTNGP11.phx.gbl...
have
> it
"bullet-proof".
> out
> Why not do what we have done and write a front end that simply allows you
to
> sepcify the various command params for the msde installer and then runs it
> passing them on? You still get the command prompt window appear. But the
> setting of the options is a whole load easier.
>
>
|||"Paul McTeigue" <paul_mcteigue@.msn.com> wrote in message
news:%23LAaxfrEEHA.2076@.TK2MSFTNGP09.phx.gbl...
> Hey Tim do you have a sample of that ?
It is fairly easy. Though the app is for the company I work for so I am not
allowed to post code, etc freely available. But the principle is easy.
Design an app in your development tool of choice (not VB - get a proper
one). Create forms that will allow the parameter selection. Instance name,
sa password, all that jazz. And then pass them out when you run the setup
file using WinExec or something similar.
I may (girlfriend allowing) have some time this weekend to produce something
if you want an app that does all the stull. Simply reply here with the
options you wish to alter and I will create a sample app for you. I can do
it in Delphi or C# - whichever floats your boat. And I'll post the source.
If it is good enough and people have any ideas for it. I may put a little
more work in (facility to run an sql script/scripts, stuff like that) so
that others can use it.
Not a promise - my girlfriend hates it when I spend too much time mucking
about on the PC at weekends - but I will give it a go.
> Paul
>
> "Tim Bird" <tsbdoulos@.nospambtopenworld.com> wrote in message
> news:%23RTaQ1oEEHA.2076@.TK2MSFTNGP09.phx.gbl...
dialog.
> have
it's
if
> "bullet-proof".
developers
you
> to
it
>
|||"Tim Bird" <tsbdoulos@.nospambtopenworld.com> wrote in message
news:eBpk8pwEEHA.3576@.tk2msftngp13.phx.gbl...
> "Paul McTeigue" <paul_mcteigue@.msn.com> wrote in message
> news:%23LAaxfrEEHA.2076@.TK2MSFTNGP09.phx.gbl...
> It is fairly easy. Though the app is for the company I work for so I am
not
> allowed to post code, etc freely available. But the principle is easy.
> Design an app in your development tool of choice (not VB - get a proper
> one). Create forms that will allow the parameter selection. Instance name,
> sa password, all that jazz. And then pass them out when you run the setup
> file using WinExec or something similar.
> I may (girlfriend allowing) have some time this weekend to produce
something
> if you want an app that does all the stull. Simply reply here with the
> options you wish to alter and I will create a sample app for you. I can do
> it in Delphi or C# - whichever floats your boat. And I'll post the source.
> If it is good enough and people have any ideas for it. I may put a little
> more work in (facility to run an sql script/scripts, stuff like that) so
> that others can use it.
> Not a promise - my girlfriend hates it when I spend too much time mucking
> about on the PC at weekends - but I will give it a go.
Sorry. Didn't get to do anything. My father had a motorcycle accident at the
weekend and seeing him ate up all my time.
> dialog.
> it's
> if
> developers
> you
runs
> it
the
>

Sunday, February 19, 2012

I need help about two server configuration

Hello I have one sql server 2000 and one MSDE , I need a database replicated
in two servers, but I can't modify table structures.
I need to make data modifications in SQL Server and in MSDE, what type of
replication can I use ?
Thank you .
Guillermo
Guillermo,
there are several choices, depending on your setup:
If you are expecting conflicts then the (out of the box) choice is between
queued updating and merge replication. Queued updating won't work if you are
replicating BLOBs but it is generally much faster than merge, especially as
you only have one subscriber.
If the data is completely partitioned, you could use bidirectional
transactional replication (not out of the box though).
If there is continual connectivity (unlikely as you are using MSDE as the
subscriber) then immediate updating subscribers could be relevant.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Thank you Paul, but I can not use Merge because that type of replication
make changes in my table structures.
And transactional replication from sql server to MSDE is ok but what can I
do for MSDE to Sql Server?
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> escribi en el mensaje
news:%23ynvRF95GHA.3592@.TK2MSFTNGP05.phx.gbl...
> Guillermo,
> there are several choices, depending on your setup:
> If you are expecting conflicts then the (out of the box) choice is between
> queued updating and merge replication. Queued updating won't work if you
are
> replicating BLOBs but it is generally much faster than merge, especially
as
> you only have one subscriber.
> If the data is completely partitioned, you could use bidirectional
> transactional replication (not out of the box though).
> If there is continual connectivity (unlikely as you are using MSDE as the
> subscriber) then immediate updating subscribers could be relevant.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
|||Guillermo,
if you go down the transactional route, you'll still have schema changes for
updating subscribers. You're quite right that bidirectional transactional
replication isn't an option as you have MSDE and hence can't publish from
it. So, for merge or transactional you'll have another column added. If you
want a solution that doesn't alter the schema at all, then for your
requirements you could consider Redgate DataCompare which just uses Primary
Keys as identifiers. BTW, what is the problem with the schema being altered
to add the extra column?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||"what is the problem with the schema being altered to add the extra
column?"
I fear that it causes errors in my applications
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> escribi en el mensaje
news:uFjTFnF6GHA.1256@.TK2MSFTNGP04.phx.gbl...
> Guillermo,
> if you go down the transactional route, you'll still have schema changes
for
> updating subscribers. You're quite right that bidirectional transactional
> replication isn't an option as you have MSDE and hence can't publish from
> it. So, for merge or transactional you'll have another column added. If
you
> want a solution that doesn't alter the schema at all, then for your
> requirements you could consider Redgate DataCompare which just uses
Primary
> Keys as identifiers. BTW, what is the problem with the schema being
altered
> to add the extra column?
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
>
|||I would only think so if these applications use "select * from ...", which
is pretty unusual. In other cases you'll be OK.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .